1.10WE Screen Problems

Does this picture mean I am screwed?

i think it means you dont have enough space in your comp...

This means you used the UMS editor or other custom editor on your map. Downgrade from 1.10 (reinstall war3 and apply 1.06 patch) then run UMS and convert any triggers that use UMS only actions/events/conditions to custom text.

now how do you suppose i get 3.6 patch?

I doubt if version 3.6 ever comes out lol, but you can check the blizzard web site and see if they are still hosting the external install for 1.06 :)

whoops. typo. heh. Right. Well, I am trying to patch up my map. Make it as much anti UMSWE3.6 as possible. So. Erhm. Who is Player 00? And uh, is there a way to make a map not UMSWE triggers?

same problem !!!!!!!!!!!!! please help, how do we get 1.06?
I been working on my map 4 months waiting for frozen throne so i could use new editor on some of the stuff and now its screwed, please please help. thanks

lol.... i had kinda same problem, but it cvan be solved.... easy...

uninstall war3, cut all the folders which appear in ur war3 main folder to another1 like ex. "war3backup"

then install war3, and upgrade to 1.10....

then after u appplyed the patch, go cut the "old" folders in "war3backup", and apply them to the now "main" folder of warcraft.....

now.... ur modifyed WE wont work any more (UMSWE, Zepirs etc.)
but then go open the "normal" editor (the 1 blizzard make), and u will be able to open ur map.......

isnt that just a bless :D

ok i got patch 1.06 now, i still get those errors thught, what should I do?

the other method do I copy everything in the main folder? cuz theres alot, like .dll and that kinda stuff do I just copy it all?

uninsteall war3, then copy ur stuff in ur main folder, and paste it in to another....

then install war3, go dl the patch, then go copy ur "old" stuff u copyed before, and paste it into ur new war3 folder, then open worldeditor <---- blizzards version, and open ur map...

then u should get like no errors... it worked for me...

i tought it meant that he didnt have enough storage space cuz in 1 screen its wrote

Not enought storage space to perform action

heres what to do. uninstall wc3, install, apply 1.06 patch, use an advanced WE to take out ALL advanced triggers. To check, use the basic editor to open your map, and see what triggers will cause it. It usually tells you the trigger number, couting top to bottom.

There is another solution to this but I have not used UMSWE so I don't know how many special triggers Scio added.

What I do know form personal experience is that extending the World Editor is not hard to do. You have a few files to edit TriggerData and TriggerStrings.

Basically, the only reason your map won't load in a standard WE is because there are triggers in there that WE won't accept.

You can emulate the functions if you can find the internal names. They will have names like 'TriggerRegisterPlayerChatEvent' or 'CreateDestructableLoc' which will need to exist in TriggerData.txt and TriggerStrings.txt.

One way to solve this is to extract your war3map.j file and find the custom functions used by UMSWE. With luck, Scio used a common prefix or suffix for the functions he implemented. If not, and you're not sure which are real functions from Blizzard and which are UMSWE's then you can find out by starting the WE and noting the error. The error will give a clue as to the function name. and then you can find that in the JASS you extracted in the war3map.j file. From this you can see the type of the parameters and reconstruct the UI files.

Since I could be talking garbage having never tried to do this, I am willing to give it a go tonight if someone wnats to send me a map that doesn't work. I'll see if my method works and write down the process for you...

Once all of the UMSWE functions are known exist in your customised UI files, you can open them freely in WE but for them to work in the map, you have to supply implementation in Blizzard.j. That's shouldn't be a problem either since the implementation will be in your map already, but I'd recommend revieing the choice of WE now that the standard one seems to have implemented many improvements (was Scio involved in these methinks?)

Cheers