Subset Games Forum

bamalf wrote:

Gencool wrote:can we use <event load> to duplicate events in a list?

Yes, we can do it.

Thank you, I'll keep this in mind.

That software is an amazing idea ! Could really make life easier for modders.

sul wrote:That software is an amazing idea ! Could really make life easier for modders.

Thank you so much!

Version 1.3 is planned for release this weekend, which will add system rewards and possibly more enemy ship features.
Unfortunately, the internet connection won't be very good for me until next weekend.
This could cause a up to a 5-day delay at worst. In the meantime, if anyone has any suggestions for new features, feel free to let me know.

edit: version 1.3 is now released with system modification, fleet pursuit modification and map reveal functionality, along with tons of crucial bug fixes. Refresh the page if you still see the old version.

From the bottom of my heart, I thank you deeply for making this. It saves me so much time. Great job, and good luck with your future plans for this!

elijahdb wrote:From the bottom of my heart, I thank you deeply for making this. It saves me so much time. Great job, and good luck with your future plans for this!

Thank you so much! I really hope you have no trouble using it let me know if you run into any problems. Enjoy!

So, quick question, when I add a ship into the event, why does it say ship name and auto_blueprint at the bottom? I haven't run into this in FTL's events yet.

elijahdb wrote:So, quick question, when I add a ship into the event, why does it say ship name and auto_blueprint at the bottom? I haven't run into this in FTL's events yet.

When FTL loads ships into events, it doesn't just call a ship blueprint. It summons what I call a scenario ship, which is defined by a ship blueprint as well as circumstances for when the ship is destroyed/the crew is killed. These ship scenarios are automatically generated by the editor alongside your event, and go inside the same file as the event.

edit: these scenarios also have names to identify them. You want the names to be unique so the scenario isn't called by another event accidently.

Okay, thanks.