| 04-09-2007, 10:16 PM | #2 |
I do not see any server split material. Back when i actually used Warcraft III i found a very good debugging technique. After each line in the danger zone (when the server split occurs) create 2 more lines of code (or gui) the first stating what just happened and the second being a one second wait. Then the last message you see before everyone goes bye-bye is the culprit, get the other tester to tell you what the last message said then correct the line of gui. It may be a lengthy process but will give you the soloution. On a second note, try looking at deleting the local shadow 'e' if that is the culprit make a workaround, that looks suspicious. |
| 04-09-2007, 10:23 PM | #3 |
Pan camera as necessary causes desyncs. Use pan camera instead. |
| 04-09-2007, 10:41 PM | #4 | |
Quote:
Really? Dang. I figured it might be that. Since getting the location of a players camera causes desyncs that makes sense. As luck would have it all my other Pan Cameras are the regular kind. Thanks for the advice too Mapz_Maker. |
| 04-10-2007, 09:08 AM | #5 |
I think you shall move this to the top of the trigger. Trigger: Custom script: local effect udg_e |
| 04-10-2007, 09:11 AM | #6 | |
Quote:
It is at the top. And the cause of the split is the pan camera thing, because it's well known to do so. |
