UMSWE 4.1 beta

About those missing strings:
Some of you might remember that they were already missing in the last beta (719). I just added support for 1.13 as fast as possible. As a result I haven't added anything else.

@chemo:
Can you describe that problem more precisely?
Which events (exact description)?

Please GOD (Starcraftfreak) do something. I got crazy since 1.13 patch was released. DDAY Players are killing me... they want a compatible version with 1.13... and that's not possible. I have so many triggers not compatible with 1.13... And i want to be sure the beta doesn't ruin any other things. If you want me, i'll forward you hundreds of emails begging me to find a sollution :) I think untill Blizzard will release 1.14 (and even then, i'll have to wait/stick with UMSWE)... we all are counting on you.
Thank you very much for your work. DDAY: Judgement is played by thousands of ppl waiting for you to release a final super version :))
Please be free to visit us (http://dday.4t.com homepage and forum: http://ddaysequel.proboards22.com).
P.S. UMSWE is the best editor for W3. Never give up this great piece of art :)

I'm not sure whats your problem. The "beta" works without any remarkable problems, i.e. you can use it without worrying.
Of course it is always recommended to make a backup.

"Create Dialog Button With Hotkey" makes "Set <dialog-variable> = Last Created Dialog Button" return the error : Invalid argument type (string)

I've encountered 2 strange system crashes while using UMSWE 4.1 Beta with a certain map.

Error 1:

1) While exiting UMSWE on my map, the computer instantly restarted for no appearent reason.
2) The computer said my Hard Drive was acting up (Which happens sometimes). My friend went into setup, checked the Bios, etc. and everything was ok. We exited setup and Windows XP started up normaly, and ran Scan Disk, which found no errors.
3) XP asked me to file an error report. I filed the report, and it didnt give me a reason for the crash.

Error 2:

1) While beggining to test my map (I had tested it several times b4 without incident) the computer instantly restarted again.
2) My friend checked the Bios again, and it was fine. We restarted the comp and ran scan disk. Scan Disk said that 2 windows files had been 'tuncated' and also mentioned my map, and the test map it was saved under.
3) XP Error reporting said it was possible that my GeForce4 Video card needed drivers, and that probly caused the crash. I updated my video drivers shortly after.
4) My map, and test map were erased.

I'm not sure if UMSWE is too blame (Probly not), but I have at least 4 culprits.

1) My hard-drive

2) My video card needing new drivers

3) My map

4) UMSWE 4.1 Beta

I dunno if you guys will be able to help out, but maybe this error report can be of use.
I'm kind of sad that Windows erased my map (It was the first mission for my campaign), but I guess I will have better luck making something new instead. (I also have a back-up, but I don't trust it much...)

As there is no one else encountering the same problems, we can suggest that it is some other problem. Apparently your system is not running stable.

Well my system seems to be working fine, in fact my friend stayed up to 3:00 AM in the morning playing Call of Duty.

I guess my only real question is, should I use a back up of my map that I copied to a CD, or start over? The error hasn't occured on any other maps, so I guess I could just start over on it...

I just wanted to point out that UMSWE can't produce these problems. I don't have such problems, and except you no one else who uses UMSWE has.

Some time ago I had similiar problems with a PC. Maybe you have to install another BIOS.

I can help you a little on this issue, but send a PM if you need further help, as this doesn't fit this forum.

"hidden icon: Repair Autocast" has a wrong path (it should be ReplaceableTextures\CommandButtons\BTNRepairOn.blp)

"hidden icon : Old Charm" Doesn't work (Tft and Roc Versions use the same path, so the only way to use the icon is to export it from the mpq and import it to the map with another path)

1.14 compatibility ??

To my knowledge the editor should work with 1.14 since 1.14 did nothing to the editor itself

You are right. I haven't tested it, as I don't have 1.14 yet (was quite busy the last days), but according to Blizzards changelog, it should work. Of course the balance changes are not applied (so in UMSWE you have 1.13 stats). There will be an update as soon as possible.

Thank you GOD (i was waiting for this).... Can i prepare my 1.14 installation for now ? :)

i think it would be incredibly useful is you allowed all references to type values of locals to be integrated into the GUI...
for example- i have a local real called r and i want to use it in a GUI point w/offset call. maybe you could make some action when you refer to a real, a custom script call? so all you do is in the same selection area that would have Arithmatic (Real) would also have a a Custom Script where you could enter the locals name to use?
this would be insanely awesome and im sure others would benefit from it, not just myself.

by the way, awesome job on UMSWE! keep up the good work and thanks!

There is already a workaround for this. I added Lord Vexorians custom script trigger call pack, which makes use of dummy functions, to make that work. I will write a tutorial at some time to explain how to use those.