Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Per-Jump Encounter/Event Flags #6

Open
puppetsquid opened this issue Sep 30, 2015 · 1 comment
Open

Per-Jump Encounter/Event Flags #6

puppetsquid opened this issue Sep 30, 2015 · 1 comment

Comments

@puppetsquid
Copy link

I posted about this in the FTL forum thread under the username 'Gencool', but am now posting here for ease of use.

I know "Crew skills as difference per sector" has already been added to the roadmap, but I think 'per Jump' would also be really useful.

The main example, again, is 'Crew Size' - just having a difference per sector means a ship might display having gained 1 crew over the sector, when in reality the player gained 5 and lost 4.

I suggested a rough workaround for finding more in-depth information about crew deaths.
I admit it becomes less accurate if more than one crewmember dies between jumps, and could probably be improved upon who knows how to code properly, but it'd be nice to see the crew data visualised in more detail.

With the data available through the FTL profile Editor, it seems this could potentially also be used to show Hazard data, Ships Destroyed/Surrendered/Escaped, Flagship Battles, Clones Created, Stores Visited, Systems Purchased/Upgraded, Augments/Weapons/Drones Added to Cargo/Equipped/Unequipped and even Event/Enemy Ship Names (where available).
Having them as Per-Jump flags, rather than (or as well as) sector breakdowns could also help correlate them with dips in hull or peaks in scrap...

Some of this would probably have to be roll-over data, and all optional, though it'd be -amazing- if you could add mini weapon/ship/crew sprites later on (dug from game files, of course).

@Niels-NTG
Copy link
Owner

You're right about the difference per beacon thing. I decided to scrap the difference per sector feature entirely, since they are functionally the same idea. Only getting a difference per beacon offers a lot more valuable information, as you rightly pointed out.

As for your rough workaround... I will address it on a later date when I have more free time.

Most of the things you mentioned are already implemented in the CSV export feature. They haven't been added to the graph yet. I'm planning to add mouse-over pop-ups with qualitative data in a future version of FTLAV.

It's hard to really get a distinction between ships that have surrendered, destroyed or escaped. And getting event text is easy, but getting the choices is not. Enemy ship names are retrievable, but from experiments I can tell you it's not that interesting. They are often the same and not ment to be seen by the player.

Adding tiny sprites directly from the game files is something you should definitely expect to see in the future.

BTW: Next time you file an issue anywhere on GitHub, try to break it down in multiple separate issues so developers can tackle it more easily.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants