fwdekker / fo76-dumps Goto Github PK
View Code? Open in Web Editor NEWData dumps of Fallout 76 game files
Data dumps of Fallout 76 game files
The perks column in the NPC_
table has an equals sign in every entry. No equals sign is actually followed by a value, so the equals sign should be removed.
Reduces code duplication.
The IDs.csv
and *.db
files are very large (>100MB) and should be compressed to reduce download times. This should be done in all future releases, and all existing releases should be updated as well.
When exporting data containing non-Latin characters (such as those in the Cyrillic alphabet), the characters are replaced with question marks (?
) in the output file. Instead, the original character should be preserved so that the scripts may be used to generate dumps for languages other than English.
This issue was copied from the old repository. It was originally opened on 2019-01-23.
The ENTM dump should include the Storefront Confirm Image List
entries. Probably also the ETIP
and ETDI
entries.
Information on armour, outfits, etc. should be dumped as well. In particular, think about stats such as DR, ER, etc.
The wiki should have an explanation on how to use flattened lists, because naïve users may not understand what the best way to work with them is.
An export should be made that lists the items that a vendor may sell. The number of items is not desired here; only which items should be noted.
Instead of only displaying the edid, each keyword should include the full link, which includes the edid, name, and formid.
In DIAL.wiki
, each dialogue export should have a short list of all actors that are involved in that section. They should be identified as [NPC_:<base ID>]
to make searching for them easier.
There should be a dump of weapon and weapon mod stats, including references to the CTs.
When a holotape shows terminal entries, the dump should tell the reader the ID of the terminal entries so that an editor can look those up.
All components columns for COBJ are empty
When editing the release, GitHub shows that there was an error uploading the dump file. This file should be created again and uploaded to the release.
In tabular exports, quotation marks are not escaped inside strings. The function to do this is present, but it doesn't do its job.
Instead of the tuple component [amount]
.
Include the credits.txt in every dump.
Dumps should contain more information about NPCs. In particular about their appearance. Check e.g. Caleb Fisher for what kind of information would be nice.
Export wiki-formatted tables of all quest stages with descriptions.
This issue was copied from the old repository. It was originally opened on 2019-03-13.
When _SerialiseToJson.pas
tries to read a NaN as a float, an error message saying "Error reading float in ..." will appear. While the value is correctly exported as the string "NaN", it's better if false positive error messages do not appear since they obscure actual error messages.
Serialising the cell with form ID 0052accd
returns the following error message:
<Error reading float in " \ [00] SeventySix.esm \ [63] GRUP Top "CELL" \ [9] GRUP Interior Cell Block 9 \ [8] GRUP Interior Cell Sub-Block 8 \ [42] [CELL:0052ACCD] \ [3] XCLL - Lighting \ [10] Directional Ambient Lighting Colors \ [2] Scale">
This issue was copied from the old repository. It was originally opened on 2019-01-09.
Describe the dump you'd like
Can you dump the facegen data for all npcs?
Additional context
Properties are currently dumped as a list of strings of the format key=value
. Instead, they should be dumped as an object using those keys and values.
As per the new code style guidelines.
Should I construct very simple objects inline or should I use listsToJsonObject
, which requires the construction of two arrays? The former is less code, but the latter may be less error-prone?
Currently, the created dump files do not have the same name as the released dump files. In particular, I have, say, IDs.csv
as output, but then upload it as tabular.IDs.csv
. I should just automate that already by including the tabular.
part in the first place.
Hi im an editor for the fallout wiki and needed the Editor ID for The nuka cola quantum paint for the x-01 but im kinda confused on how i open up the files (sorry if im being dense im just not the best with tech)
Create a post-processing script/program for the created dumps. This script/program can be written for Windows only since xEdit is Windows-only. The script performs the following operations:
.001
), and removes(?) the partial dumps.*.csv
into a single SQLite database.wiki.
or tabular.
in front.Stretch goal: Also invoke xEdit before doing the rest, and wait until the user closes it before continuing with the above steps.
This tool is useful because it means I can create releases with less effort from my side. Lowers my "barrier" to creating new releases as it were.
I could write the tool in bash, but I don't have a lot of experience with that. I'll probably go with Python or Kotlin. The tool should be included in this repository... somewhere?
The README should have documentation on the various columns available in the tabular exports. It should explain what various columns mean and how they are calculated.
This functionality is currently duplicated quite often.
Some special JSON cases (e.g. newlines) are currently not properly escaped. Escape them. cf. my old gist
A full-fledged GUI with which you can select which (types of) dumps to include, e.g. select to exclude IDs but include TERMs.
Count the number of errors and warnings generated by my code and include those counts.
The terminal export script uses the writeTerminalContents
function which writes directly to outputLines
. Instead, it should build and finally return a string which is added to outputLines
by the caller.
Describe the bug
The export of the deep sleep routine holotape contains the string ERROR
instead of the line.
To reproduce
Steps to reproduce the behavior:
ExportWikiDIAL.pas
on the deep sleep routine holotape (00571f69
).Expected behavior
The voice line spoken by A.T.H.E.N.A. should be exported.
Version information
Additional context
For some reason, the erroneously exported line (see dialog topic 00571f0e
) has 7 lines in it instead of the usual 1. I do not know why. Is the spoke line randomised? Does it change per player or every time you listen to it?
The dialogue export script writes directly to outputLines
. Instead, it should build and finally return a string which is added to outputLines
by the caller. Additionally, the addQuest
function should be split up into multiple functions if possible.
In addition to providing version information in the release description, the release description should also provide
Describe the dump you'd like
Would be great to have a dump of consumables (ALCH)
CLAS properties are currently represented as floats, even though the there is no extra information after the decimal point. Rounding them to integers will remove visual clutter.
Some lines of code exceed the limit of 120 characters per line. This limit should be enforced throughout all scripts.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.