I appreciate the feedback. I'll send a note to the documentation team to suggest we add that where applicable.
There is nothing wrong with doing advanced things that require copy and pasting code into new locations. I do it all the time, for instance I sometimes will put a recordset inside a repeat region, or move an insert in between two recordsets. There is nothing fundamentally wrong with that, just sometimes when doing something advanced the order of the code becomes significant and you can't always depend on dreamweaver to realize that and put things in the "right" order because depending on what you are doing one order might be right for you and wrong for another person.
This is true for not just our server behaviors, but for Dreamweaver's as well. The weighting of server behaviors isn't something we introduced, it is core to the way Dreamweaver works. That is how I learned about it, from reading Dreamweaver's documentation. I appreciate and apologize for your frustration, but at least you learned something. Not just this server behavior, but all server behaviors when applied may have to be re-arranged if you need them to work in a particular order. This goes for ours, Dreamweaver's, or any other extension developer's that creates Server Behaviors.
What's worse is that once you move one server behavior it will effect every other one applied in the future. For instance I often will move a recordset into a repeated region. Once I do that, then that establishes that location as the "50" weight location in Dreamweaver's eyes, so any other server behavior I apply with weight greater than 50 will then appear in my HTML inside the repeat region below the recordset I moved down there manually.
The weighted system Dreamweaver uses for server behaviors is far from perfect, and it is something people will have to get used to because it isn't something we as extension developers can fix. To accurately place code, you would effectively have to know what the developer is thinking and planning, and it really isn't possible outside of a wizard that does everything for you like DataAssist. As long as you can apply server behaviors individually that are supposed to work together, then re-ordering may be necessary.