Closed Istador closed 3 years ago
This is implemented partly. Not with uTinyRipper
, but still with UABE. Because uTinyRipper
doesn't export the concrete item amounts and item IDs as expected (concretely: it doesn't export properties of MonoBehaviours
, so we only know the amount of child game objects, but not the concrete amount returned by the script).
The structure of the game assets had changed a bit, so it's now easier to just extract everything important in a decent amount of time with less manual steps.
What still could be improved a bit is rewriting the extract.sh
in python, as the coordinate calculation via awk
is quite slow (resulting in 30-60 minutes runtime instead of possibly only a few seconds/minutes).
Also it currently only sums up localPosition
, without respecting the localRotation
via quaternions, resulting in wrong coordinates for a small amount of things that do have rotations in their parent game objects.
Exporting Item IDs for chests and ideas needs to be checked for correctness, as it outputs seemingly wrong IDs.
Not needed, the game isn't going to change anymore.
Figuring the Item IDs out by hand seems to be less work.
Follow up to #6.
Extract coordinates from the game assets using, to have less manual steps and the item amounts (and item IDs) in the output.uTinyRipper
instead ofUABE
What to extract/export:
extract.sh
localRotation
when calculating coordinatespretify.py
title
,description
,source
andscreenshot
that are manually changed but persist between versionswikify.sh
csv
data intowikitext
wikitext
tocsv
(as there being a lot of manual changes by now only in the wiki)