In engine/misc.txt, you can set "save_onload=false" to disable saving when changing maps. You can then use "save_onexit=false" to disable auto-saving when the player exits the game. You may also want to set "save_oncutscene=false" if you plan on using cutscenes.
To then save the game manually, you can use "save_game=true" in an event.
As a matter of fact, the project I mentioned that was using Flare had a map system just like that. They were able to accomplish it by creating a "book" that had the world map as a background. Each location on the map was a button that executed the "intermap" event to send the player to the correct map.
For switching days, you would actually need "requires_not_status=tuesday,wednesday,thursday,friday,saturday,sunday". A much easier way would be to flip to logic and use "requires_status=monday".
I did some testing and was surprised to see using "requires_status" didn't work. Turns out, for whatever reason, the key you want is called "visible_requires_status" instead. "visible_requires_status=06:00" will do what you want. If there's truly no reason for this naming difference, I'll extend the engine to support both.
You can use "requires_status" for powers/upgrades in the powers tree, and events can use "set_status". So combining those two should let you control skills with events.
Looks like it might be an engine bug. I just tried something similar and I had to click the upgrade button, even though there was no power point requirement. I've opened an issue here: https://github.com/flareteam/flare-engine/issues/1766
In engine/misc.txt, you can set "save_onload=false" to disable saving when changing maps. You can then use "save_onexit=false" to disable auto-saving when the player exits the game. You may also want to set "save_oncutscene=false" if you plan on using cutscenes.
To then save the game manually, you can use "save_game=true" in an event.
First, you should check flare_log.txt in your Settings folder for any detected errors (https://github.com/flareteam/flare-engine#settings)
Second, it's worth reviewing the Animation Definitions wiki page (https://github.com/flareteam/flare-engine/wiki/Animation-Definitions) if you haven't already.
As a matter of fact, the project I mentioned that was using Flare had a map system just like that. They were able to accomplish it by creating a "book" that had the world map as a background. Each location on the map was a button that executed the "intermap" event to send the player to the correct map.
For switching days, you would actually need "requires_not_status=tuesday,wednesday,thursday,friday,saturday,sunday". A much easier way would be to flip to logic and use "requires_status=monday".
I did some testing and was surprised to see using "requires_status" didn't work. Turns out, for whatever reason, the key you want is called "visible_requires_status" instead. "visible_requires_status=06:00" will do what you want. If there's truly no reason for this naming difference, I'll extend the engine to support both.
You can use "requires_status" for powers/upgrades in the powers tree, and events can use "set_status". So combining those two should let you control skills with events.
I didn't know you were using Linux. I would recommend building it yourself if you haven't already (it's not too hard). Here's a quick guide: https://github.com/flareteam/flare-engine/blob/master/INSTALL.engine.md#...
Sorry, no way to increase stats directly with an event.
As for the bug, I just pushed a fix for it: https://github.com/flareteam/flare-engine/commit/084e645b5c23b9b3cb3f84b...
I've also made a Windows build if you need it to try: https://drive.google.com/file/d/1I_HSDIpXprYYaWCmSb0XE71xZxE--h7N/view?u...
The Powers menu was refactored for version 1.07, so I think the code was cut there. Should be fixable.
Looks like it might be an engine bug. I just tried something similar and I had to click the upgrade button, even though there was no power point requirement. I've opened an issue here: https://github.com/flareteam/flare-engine/issues/1766
No, nothing like that is possible currently.
You should set the "power_damage" property on the event. On the power, you should add something like this:
modifier_accuracy=absolute,1000
Pages