scp-fs2open / scp-fs2open/fs2open.github.com

Split off "Hard stats" of ships, weapons, into a .csv for dev QoL

Open
#5,116 0 comments 0 reactions 0 assignees View on GitHub
discussion feature general modding
Dominant language
C++
Stars
487
Forks
184
Avg merge
3d 9h
Merged PRs (30d)
44

Description

This idea came up from a discussion with SerialMascot on discord over the use of the new `-weaponspew` commandline flag.

`-weaponspew` outputs "hard stats" of weapons to a .csv for data analysis and easy comparison of the various weapons such as damage hitpoints, range, energy consumption per shot, etc.

This feature request/discussion thus goes over the feasibility of possibly spitting off the hard stats from the rest of the weapon specs found within the weapons.tbl into a .csv, .json, or similar file that can be used in spreadsheets or database tools.

Thus, the envisioned workflow would be:
1. Mod maker tells FSO to output to a database file of default weapons or weapons from a source mod
2. Mod maker reviews and edits weapon stats to their liking
3. FSO then imports the database file, either from commandline, hardcode, or script to override or replace the respective stats as defined in the weapons or ship .tbl
4. Mod maker tests the changes in game
5. Repeat steps 2 to 4 until satisfactory

Currently the `-weaponspew` is only one way, any changes they wish to do on the weapons has to be done directly into the table. So at a minimum this FR would require some sort of import function to get the data back into FSO.

For further discussion, This import function can then possibly supercede the definitions in the weapons/ship .tbl altogether (thus not requiring the stats be defined in .tbl since they're defined in the .csv).

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.