Search results

That was added in 0.27.11

The flag names aren't useful (unless they are existing flags), I need their integer values. I normally can't add new functionality till it gets into a public build (and I can get the source code).

Delete this directory: %UserProfile%\AppData\Local\TiTsEd

*cough* https://forum.fenoxo.com/threads/titsed-a-save-editor.2809/ The pregnancy editing is experimental, though. Backup your saves. Also, if you do run into issues, *PLEASE* document them via an issue in GitHub :D

Right, I just can't resist being super anal when discussing technical details sometimes >>

Yes

That doesn't set it to "default".. it deletes the flag entry from the save.

From the first post in the editor thread:

Those items are in the TiTS source, but they currently cannot be obtained in-game. If it isn't in the Raw tab, then it is not in the save, or is not a 'Flag', in which case the editor doesn't support it yet.

Read the game's source code >.>

Yeah.. it would feel like a job if I took any money for it. I'd rather not.

Turns out, Paige is marked as "neverSerialize", so she is never stored in the save, her state is stored purely in flags and stats. https://github.com/OXOIndustries/TiTS-Public/blob/master/classes/Characters/Paige.as

Will be in the next release, or you can use this version of the TiTsEd.Data.xml: https://github.com/Chase-san/TiTsEd/blob/a9190b1222f2ed9f3eff108faf27a73bccbd821b/TiTsEd/TiTsEd.Data.xml

The list of characters is based on the specific save you are editing. If a particular character is not in the list, that means that save does not know about that character.

I don't actually look at the changelog, I look at the source. I run a diff from previous to new for specific changes like new/changed items/statuses/etc.

My entire point was that everyone else can use the slot for "whatever", but drone techs cannot.

The drone-specialized Tech is at a disadvantage compared to everyone else. Everyone else can use the accessory slot for such as the thermal belt. The drone tech cannot without giving up their lone advantage.

Link a process monitor output for a new attempt

Can always look at the source code to see what they do, if anything. If you do, feel free to open a pull request in TiTsEd for updates :D

I wouldn't take every flag listed in TiTsEd as useful, either, especially if they don't have comments about them. I don't normally "fact check" them. I run a diff from previous source to new, to find new stuff. I don't really go looking at each individual one to see if they're actually used...