"First of all, thank you so much for developing UABEANext!"
Describe the bug
After exporting a MonoBehaviour StringTable dump from a bundle, editing the m_Localized text, and importing the dump back, the game gets stuck on an infinite loading screen.
To Reproduce
Steps to reproduce the behavior:
Open the localization-string-tables-english(en)_assets_all.bundle file from the game Between Horizons.
Select the Monologues_en MonoBehaviour (StringTable) asset and click 'Export Dump'.
Edit a single English word in the text dump (saved strictly as UTF-8 with UNIX LF line endings to ensure no encoding issues).
Click 'Import Dump' and select the edited .txt file.
Save the bundle to the memory, then save the physical .bundle file and replace the original in the game folder.
Launch the game and see it freeze endlessly on the loading screen.
Expected behavior
The bundle should repack correctly without breaking the internal byte structure, and the game should load normally, displaying the edited text.
Screenshots
Additional context
Game: Between Horizons (Unity IL2CPP, uses Addressables).
I tested this by just changing one English word to another to completely rule out font/special character support issues or bad formatting. The formatting of the dump is strictly UTF-8 with LF. It seems the repack/import process might be slightly corrupting the internal structure or byte alignment of the bundle for this specific game's Unity version. Let me know if you need the specific .bundle or dump files for testing!
"First of all, thank you so much for developing UABEANext!"
Describe the bug
After exporting a MonoBehaviour StringTable dump from a bundle, editing the m_Localized text, and importing the dump back, the game gets stuck on an infinite loading screen.
To Reproduce
Steps to reproduce the behavior:
Open the localization-string-tables-english(en)_assets_all.bundle file from the game Between Horizons.
Select the Monologues_en MonoBehaviour (StringTable) asset and click 'Export Dump'.
Edit a single English word in the text dump (saved strictly as UTF-8 with UNIX LF line endings to ensure no encoding issues).
Click 'Import Dump' and select the edited .txt file.
Save the bundle to the memory, then save the physical .bundle file and replace the original in the game folder.
Launch the game and see it freeze endlessly on the loading screen.
Expected behavior
The bundle should repack correctly without breaking the internal byte structure, and the game should load normally, displaying the edited text.
Screenshots
Additional context
Game: Between Horizons (Unity IL2CPP, uses Addressables).
I tested this by just changing one English word to another to completely rule out font/special character support issues or bad formatting. The formatting of the dump is strictly UTF-8 with LF. It seems the repack/import process might be slightly corrupting the internal structure or byte alignment of the bundle for this specific game's Unity version. Let me know if you need the specific .bundle or dump files for testing!