| 12-08-2003, 07:37 PM | #1 |
Here is my current version of UMSWE 4.1. It's beta, so I suggest that only experienced users use it. The RAR archive contains the standard edition only. Make suggestions here: http://www.wc3campaigns.com/forums/s...threadid=21493 Bugreports of new stuff, that wasn't in 4.0 should pe posted into this thread. Build 719: http://www.wc3campaigns.net/tools/um....1_beta719.rar Build 775 (fully 1.13 compatible): http://www.wc3campaigns.net/tools/um....1_beta775.rar Build 825: http://www.wc3campaigns.net/tools/um....1_beta825.rar Build 829: http://www.wc3campaigns.net/tools/um....1_beta829.rar Build 832 (fully 1.15 compatible): http://www.wc3campaigns.net/tools/um....1_beta832.rar Build 833: http://www.wc3campaigns.net/tools/um....1_beta833.rar Build 835 (fully 1.17 compatible, triggerfix only): http://www.wc3campaigns.net/tools/um....1_beta835.rar Build 836 (fully 1.18 compatible): http://www.wc3campaigns.net/tools/um....1_beta836.rar Build 837: http://www.wc3campaigns.net/tools/um....1_beta837.rar MAC Edition: Build 832: http://www.wc3campaigns.net/tools/um...eta832_mac.zip Build 833: http://www.wc3campaigns.net/tools/um...eta833_mac.zip Build 835 (fully 1.17 compatible, triggerfix only): http://www.wc3campaigns.net/tools/um...eta835_mac.zip Build 836 (fully 1.18 compatible): http://www.wc3campaigns.net/tools/um...eta836_mac.zip Build 837: http://www.wc3campaigns.net/tools/um...eta837_mac.zip To make the MAC edition work, just copy all files from the ZIP archive to your WC3 folder. If you start the WE afterwards it will be UMSWE. If you want to use the normal WE or if you want to play the game, you should remove those directories again. More info will be available soon. I'm working on a better solution for this. Stay tuned! Readme |
| 12-09-2003, 03:11 PM | #2 |
When I open it I get odd missing string messages for event button click, widget destroy and some other I can't remember, the weird thing is that the triggers are still usable and nothing wrong happens besides the messages. Also I reccomend you to put the Custom Script Trigger Calls at the bottom of the lists instead at the top (so newbs won't get scared) |
| 12-09-2003, 07:24 PM | #3 |
1) I am aware of the three yellow warning messages. I just forgot to add some strings. Nevermind, it's beta. 2) Ok, I also thought that they should be at the bottom. I will also write a tutorial for the custom script trigger calls. |
| 12-10-2003, 12:49 AM | #4 |
does this work with classic? |
| 12-10-2003, 08:11 AM | #5 |
Like any release of UMSWE it is also compatible with RoC. It requires RoC 1.10 or higher. |
| 12-10-2003, 11:12 AM | #6 |
The Jass Code option is not working, when i put it in a trigger, when i start the game, it didn't start after the main screen of w3, like when we make an script error ... |
| 12-10-2003, 03:06 PM | #7 |
You have to copy the functions from Lord Vexorians custom Script trigger calls plugin to your script header. Search it in the Jass Vault. As I said, this is a beta for experienced users. In the full release there will be a tutorial for that. |
| 12-10-2003, 03:15 PM | #8 |
Is there any way to add something in the header at the open of a map ? |
| 12-10-2003, 03:22 PM | #9 |
Look at that thread from Lord Vexorian: http://www.wc3campaigns.com/forums/s...threadid=34100 |
| 12-10-2003, 03:35 PM | #10 |
Yeah i already saw it, and i know now how to use it, but for UMSWE, will we need every time to add functions in the header ? I imported the blizz.j of UMSWE, its work but its a little heavy :D |
| 12-10-2003, 03:38 PM | #11 | |
Quote:
There is no way to do that (yet) , also importing blizzard.j won't work at all (will work for single player but forget about it in battle.net) so please copy the functions there everytime you want to use them |
| 12-12-2003, 08:20 PM | #12 |
I like what you did with the trackable but could you add to the gui Move trackable to a point i know you cant distroy them but can you move them in actions. |
| 12-12-2003, 08:33 PM | #13 | |
Quote:
|
| 12-12-2003, 08:40 PM | #14 |
k thanks that would help alot. |
| 12-13-2003, 11:18 AM | #15 |
Lord Vexorian, why should including the Blizzard.j not work on b.net ? Unless Blizzard changed something about it (I have not tested it for quite some time) you can include Blizzard.j in maps and it works, even on b.net . |
