STTEVE

What is STTEVE?

STTEVE is fan-made tool for game Star Trek Timelines. It reads game data in JSON format and creates CSV files suitable to import to another tools or to your own spreadsheet for further analysis and examination of your crew, ships, items etc.
TLLTs (Tyl Lanthor Little Tools) were added to the website later to help you in some aspects of the game.

A famous tool DataCore was a great inspiration for development of STTEVE. STTEVE generates same CSV files with identical data struture as DataCore - crew.csv, ships.csv and items.csv. STTEVE has quite rich configuration options that allow you to generate CSV files “mostly compatible” with DataCore, or generate STTEVE's “extended” CSV files with new additional columns. Also, you can create absolutely new CSV files with another game related data.

Generated CSV files contain data from another community tools/projects. See the full list on the About page.

You will find STTEVE main tool on the Tool page.

Remarkable features

• Verbose information about your game in gameinfo.csv file (buffs, factions, voyage, events etc.).
• The tinygameinfo.csv file can be used by other tools to easily get player's total buffs and voyage information so that the player doesn't need to fill them manually.
• Verbose information about all ship battlestations in ships.csv file.
• Your crew retrieval inventory stored in crewretrieval.csv file (polestars and constellations, but also ISM and quantum).
• New columns “Unique ID” and “Frozen/Active character quantity” can help you to distinguish and identify duplicit crew.
• You can add crew in countdown and/or in reenlistment to crew.csv file if you wish.
• Viable Voyager Tool related data in viablevoyager.csv file are calculated for all characters and not only legendaries.
• STTEVE produces equipment data with similar data structure as DataCore but with unique item names and (IMHO) more accurate values.

Data accuracy in CSV files

STTEVE extracts many data from JSON game data but some values are taken from another tools and data sources. STTEVE collects external data and saves them in its own storage to not overload other tools and sites. Data syncing is done manually by the author at the moment.

This fact means that STTEVE can produce inaccurate output files if stored external data are outdated. As result, CSV files can contain inaccurate, zeroes or even missing information (e.g. for new crew). This temporal situation is mostly solved by performing an update of external data, which is done by the author of STTEVE.

You have the possibility to check date and time of external data at the bottom of the Tool page and estimate if STTEVE uses current data. Note that some external data files can be updated less frequently (e.g. ships), which is normal.

Differences to DataCore CSV files

Three core CSV files crew.csv, ships.csv and items.csv created by STTEVE use the same data structure as the same CSV files provided by DataCore. The order of columns and their names are identic (however, the order of rows doesn't correspond).

Be aware that STTEVE calculates values in the columns “Amount”, “Accuracy”, “Crit Bonus”, “Crit Rating” and “Evasion” differently than DataCore. DataCore fills the columns with values corresponding to FFFE character while STTEVE writes values corresponding to current level, equipment and rarity of character. In other words, we can say that DataCore describes final state of crew while STTEVE describes current state of crew.

STTEVE has a configuration parameter “Crew parsing mode” that allows you to switch between DataCore and STTEVE mode.

There is one more column that is filled by STTEVE differently - “Charge phases”. Some charge phases in DataCore crew.csv file are wrong. You can easily identify them by presence of “undefined” word (see e.g. Senator Cretak or Duelist Barclay). Charge phases in web interface of DataCore are correct, though. STTEVE uses own algorithm to create correct charge phases, which is the reason of difference to DataCore CSV file. Also note that creation of charge phases cannot be altered by the configuration parameter “Crew parsing mode”.

Content of the equipment.csv file is also different from DataCore. Structure of the columns is the same but values differ. It is because DataCore IMHO calculates wrong values. Equipment data from STTEVE should be more accurate.