I’ll be up for Alpha/Beta testing
(Or will i be already testing because i tested in the past)
1 Like
You will be on non-public tests for versions that aren’t good for public release.
The mentioned case is for public alpha / beta versions where anyone can decide by himself if he wants to use them.
Basically there will be an option in the updater (a checkbox) where you can select “alpha” and “beta” versions, too (think about the Steam Beta feature). If chosen, you’ll be notified when a new version is available (alpha, beta or stable).
2 Likes
What’s wrong with my code??
Seems to be an error where UME doesn’t escape strings properly. You can work around this by removing the " characters in your research description.
2 Likes
Thank you! 
There will be no non-public version for the next release. I will try to release a version by tomorrow which will address bugs and introduce some new features, although I cannot guarantee that they will be completely implemented. I have a long train travel today, so let’s see how much I got done today (I will focus heavily on the import / export features, so you can collaborate and share).
2 Likes
Well, all I can say is GOOD LUCK and, I believe you can launch it tomorrow!
Thanks 
And I already have some good news 
I currently finished implementing the core routines for handling import and export (the Engine Research Export / Import is already working).
Whatever happens within the next hours, Import/Export will definitely be available!
2 Likes
Yeah! This will help a lot in TimeZonePack!
And, do you have any other minor features that are already implemented?
1 Like
Not yet… writing code at 275km/h and with a quite slow internet is not always easy and funny 
But as soon as I’m at home, I’ll have some hours to work on finetuning the next release 
1 Like
Again, good luck, because writing a code at 275km/h with a slow internet should be VERY hard (and boring)
And… (I always put this “and…”) Is there any other feature that you’re trying to implement at the moment?
“And”… most probably “Custom Code”
1 Like
Great news, guys.
The import and export of the following project items has been fully implemented and is working:
- Engine Research (Extension: .resengine.umeblock)
- Lab Research (Extension: .reslab.umeblock)
- Hardware Research (Extension: .reshardware.umeblock)
- Platform (Extension: .platform.umeblock)
- Topic (Extension: .topic.umeblock)
- Simple Event (Extension: .sevent.umeblock)
- Platform Event (Extension: .pevent.umeblock)
- Simple Notification (Extension: .snotification.umeblock)
This means: tomorrow’s release will include this new features 
Exporting and importing items is a piece of 
:
Export:
- Right-Click on an item to bring up the corresponding context menu
- Select “Export ITEMTYPE”
- Select target directory and file
- Click OK
- Done
Import:
- Right-Click on a item category to bring up the corresponding context menu
- Select “Import ITEMTYPE”
- Select target file
- Click OK
- Done
(Duplicate items will be detected, so that you can only import an exported item once).
2 Likes
Well, now there’s no reason to the TZP don’t happens!
1 Like
@alphabit The UME file for my mods latest alpha was working fine a few hours ago
But when i try opening it now i get this
This error is caused by the CanDevelopLargeGame thing, it is an error with the code creation of UME.
I had this error too and @alphabit fixed it for me, so send him a PM and he will probably fix it when he have time.
And, looks like a new update of UltraGDT is online
1 Like