Starting a New Project Worth it?

[Leubast]

I think it's clear that Warcraft 3 will be getting quite a few updates throughout the PTR that could very well corrupt maps in the making so I wanted to ask before I really get back into map making again; Would starting a new project be worth it, either in 1.27 or current PTR 1.29?

My concerns are that if I start a new project in PTR 1.29 that an update might break it, but if I start it in 1.27 that it won't work with the newest update once it becomes the norm or that it would just feel generally out of date.

 

[Chaosy]

Blizzard seem pretty keen on backwards comparability unless it is breaking the game. @Kam might hopefully reassure this.

And even if it somehow does break, it is probably an easy fix. You wont have to remake your whole map, or anything close to it.

 

[Kam]

We are committed to helping map developers keep their projects alive.

I would not begin a project on a PTR as anything on a PTR is subject to change.

 

[Leubast]

I'll keep my project small in that case because I am loving the improvements made so far.

Thank you, Kam!

 

[TheGoldenGoblin]

Does Jass NewGen (JNPG) work with 1.29 or are we stuck with normal Jass with the new update?

 

[Chaosy]

JNGP's author is not active.
So no it wont work, seeing as it does not work on 1.28

WEX is actively developed and is the only choice for the latest patches.
Hive WE is too early too fully take over, but eventually that will probably be an option.

 

[TheGoldenGoblin]

So I have to learn normal Jass now and add loads of variables? :/

 

[Lizreu]

So I have to learn normal Jass now and add loads of variables? :/

WEX supports vJASS out of the box, and just about everything else you need for triggering.

 

[Alethos]

I would not begin a project on a PTR as anything on a PTR is subject to change.

I accidentally did a ton of map editing on the PTR without realizing... now when I test ingame via the normal editor there are some glitches (models with water texture do not show for example).

Anybody has ideas to salvage all the work I've been doing? :'(

Unfortunately I did not do a changelog- and I do have many saved versions but my previous saved version for the not-ptr is quite old. I'm a mess.

 

[Korialstrasz]

I accidentally did a ton of map editing on the PTR without realizing... now when I test ingame via the normal editor there are some glitches (models with water texture do not show for example).

Anybody has ideas to salvage all the work I've been doing? :'(

Unfortunately I did not do a changelog- and I do have many saved versions but my previous saved version for the not-ptr is quite old. I'm a mess.

Don't worry too much about it, I did the same. Kam is of course right, it wasn't the best idea, but I could not resist working with the new colors and the widescreen support.
I for my part will continue to work on the PTR and pray that it will still work on the final version.

What you can try is exporting the object & trigger data and import it with the old editor again. However you should try to eliminate any ptr features in these datas that you used.

Or you just risk it now to continue on the PTR since you already did a lot on it, that is what I will do. No risk no fun. The choice is yours.

 

[Xonok]

When 1.29 comes out for real I will update my own JNGP such that it would be able to use the new natives. There's a file somewhere that says which natives exist, so simply adding them there should prevent errors and that's all the updating I need. This means having 2 versions of WC3 installed - one that works with JNGP and one that is fully updated.