| 07-31-2014, 06:40 AM | #1 |
So, like every other lazy map maker, i've been working on the same map on and off for maybe 3 years. sometime within the last major version, though, it has become unplayable on battlenet for some hosts. it would really suck to lose like 20 hours of work if I have to fully revert to the last stable version here's the deets: 1. I can play the map fine in single player 2. I can use the multiplayer emulator function of WE 2.0 to play with other fake clients via LAN 3. Even though I've heard this from a few people, I only have one instance I can actually describe: player2 tries to host map, fails and his warcraft client becomes glitched (I view him as being in game, he views himself as being in channel) a. when I try to host the map after that, I get an error saying that it's an invalid map4. The map doesn't use the return bug anywhere Any thoughts or ideas for tracking down the smoking gun? I'm attaching the unprotected map file, I'm not sure if it would have been possible for him to open it My current plan for the worst case scenario is to somehow slowly merge the new version's scripts into the old versions. can't do it all at once or the same problem will stick and doing it separately sucks with cascading requirements. a better solution would be much loved |
| 07-31-2014, 11:12 PM | #2 |
actually that won't work since the map plays just fine for me 100% if anyone has time would they mind opening it / trying to see if it loads single player (you don't have to play at all) edit: to open it requires jngp with an updated jasshelper and umswe enabled |
| 08-01-2014, 04:45 AM | #3 |
I can play it in SP just fine. Can't open it in normal editor or JNGP. It says "Trigger function does not exist in database:" and a blank line. Then it crashes. |
| 08-01-2014, 09:41 AM | #4 |
thanks for checking Fledermaus, I appreciate it! i actually got that error for a while too. usually it means one of two things: either your path to wc3 is not valid (in my case this was caused by a valid path with insufficient read/write privileges) or UMSWE is not enabled. in this case it might actually mean that the map is somehow corrupted though :/ trying to open the map once was enough (thanks again!), these are just my troubleshooting findings if it keeps happening to you |
| 08-01-2014, 10:08 PM | #5 |
a) make sure your map is updated to be compatibile with patch 1.24. b) disable UMSWE and WEU The 3rd party tools listed in b) are providing illusive impression of adding something new, but the only thing they actually provide is chaos. If you want to extend we functionality use SharpCraft. Everything that you thought you need WEU/UMSWE for can be achieve with standard WE or JNPG, especially the new 2.0.X version. There is no reason to use those outdated resources. Again, I'm advicing you to carefully study your scripts, convert them into acceptable form for JNPG and then recheck the map. If problems still occur, post them here. |
