5 replies to this topic

[Rastael]

Heyho

 

I'm half finished with my 2.5 quest and I'm considering changing over to version 2.55. Since I use many scripts in my quest, I'm wondering, if I have to expect some complications or if I can change over without any fear that one of the scripted items, enemies (or other stuff) might not work.

I'm especially worried about the X- and Y-Buttons.

 

Would you recommend to change over for the new features or stay in 2.5?

[Alucard648]

X and Y buttons are same as Ex1 and Ex2 buttons respectively.

[Rastael]

X and Y buttons are same as Ex1 and Ex2 buttons respectively.

Thanks for your reply. ^^

 

I just wonder, if I can adjust the scripted weapons to the X- and Y-Buttons without any problems.

I also used lots of the "z (+number)" items as custom items, which are now maybe a complete new item (wich maybe deletes the item I created).

 

Those are just some concerns I have. Maybe it will work without any problems. But maybe, I spend hours with working in my quest in 2.55 and then realise, that it was a big mistakes, because several things are;nt working any more. That's why I wanted to ask you guys.

[Russ]

In general, scripted items should work fine on X and Y. The exception would be if the script is written in such a way that a global script component is looking for A or B being pressed while the scripted item is assigned to that button.

[connor.clark]

I would recommend updating to 2.55 just for the VS code extension.

 

It's not 2.50 but FWIW we have an entire test case of compiling the scripts for this quest (plus actually running and ensuring it all works the same) to avoid major breakages in scripts. Besides a few minor breaking changes in the language itself (top of mind is that non-void functions missing a return statement now error), and perhaps some movement within the std library, it shouldn't be much effort to get 2.50 scripts compiling again. If you come across an issue let me know.

[Rastael]

I would recommend updating to 2.55 just for the VS code extension.

 

It's not 2.50 but FWIW we have an entire test case of compiling the scripts for this quest (plus actually running and ensuring it all works the same) to avoid major breakages in scripts. Besides a few minor breaking changes in the language itself (top of mind is that non-void functions missing a return statement now error), and perhaps some movement within the std library, it shouldn't be much effort to get 2.50 scripts compiling again. If you come across an issue let me know.

 

Thanks a lot! ^^

 

I will try it out and message you, if I get some minor errors or bugs.