Converted lsj won't convert back to lsf

[PoroDev]

trafficstars

Hello,

when trying to convert lsf to lsj then doing the opposite, it give an error due to Null token. The error seems to come from the readAttribute function when it encounter this kind of lines :

"DLOG_SpeakerName": {
	"type": 33,
	"value": null,
	"handle": "he074cbb8g0e2eg4347gb3beg6941d9ddb989",
	"arguments": []
}

Seems to come from the value being null, I'm new to this project so I don't know if it's new to BG3 tho.

[Norbyte]

Hi,

This bug was fixed in v1.18.3.

[PoroDev]

Hello,

Seems like I still have the issue with it on "Globals.lsf" file. Still the same error with the token being null during the readAttribute function.

[Norbyte]

Hi,

Which global.lsf file is this? One from the savegame?

[PoroDev]

Yes, the one from a save using last version of the game.

[kaldais]

Same issue, I'm unable to convert the globals.lsx back to globals.lsf After trying to account for those nulls in the reader, I unable to write null back into UTF.

[Norbyte]

Additional fixes were made for this in v1.18.5. My test saves all loaded properly after an LSF/LSJ conversion

[PoroDev]

This issue is still present in 1.18.5 :

This happens in the ReadTranslatedFSString function, i can share my Globals.lsf file if needed for tests.