-
Notifications
You must be signed in to change notification settings - Fork 15
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
Dashboard displays %ADJECTIVE% and %ADJ% instead of empire names #90
Comments
Oops, here's an UNmodded 3.6.1 save that has the problem (same as just added to #92) https://github.com/eliasdoehne/stellaris-dashboard/files/10269005/2200.01.01.sav.zip |
Right, I actually don't remember that well myself how the name rendering part is implemented, so I'm looking forward to the PR you mentioned but let me know if I can help with that. This is actually a very interesting topic for another reason, I had a quick look at the localization files and it seems that a lot of in-game text was moved over there, so while the changes break some things for now it creates some very interesting options for the event ledger. It may now be possible to extract anomalies and special project from the save file and render them correctly at runtime with the event description (something like |
Yup - the PR is #91 |
The save format for leader names changed, and there's another new template. Updating the PR Problem: OLD:
NEW:
|
Aand I just found
|
(Pull request coming soon, this is for explanation and documentation)
Stellaris 3.6(?) added
%ADJECTIVE%
and%ADJ%
templates while not adding them to the localisation files (I did verify files on Steam). There is anadj_format
which would work for%ADJECTIVE%
but not%ADJ%
.Here is the save file and an example straight from the save:
Nexitron_2246.06.28.sav.zip
Which should be
Nexitron Awareness
And here is a prettified JSON example of both:
Which should be
Allied Jing Systems
.Note how
%ADJECTIVE%
is in the usual format but%ADJ%
doesn't follow the same template format.The text was updated successfully, but these errors were encountered: