PSO2es is made in Unity, so all programming is done in C#. Until about halfway through 2019, Sega were leaving their C# .DLLs fully exposed in the game APK. C# code is very easy to decompile and read, and we were easily able to incorporate their database reading/writing libraries into ESBreaker.
However, a few months ago, they started using a feature of Unity called IL2CPP to build the game. IL2CPP compiles the C# code into an intermediary language, then compiles that into C++ specific to each platform the game's intended to run on. C++ is much, much harder to decompile, especially after it's been put through this process - that's the point of IL2CPP.
Despite this, our old version of their database library does still work - mostly. All text field types that were present before they switched to IL2CPP work absolutely fine and will continue to do so for the foreseeable future.
However, in the same update that they switched to IL2CPP, they added an extra text field to the Specialization/Plug-In menu. When we build our database, our copy of the library doesn't know that this field needs to exist, so it simply builds the database without it. When the game tries to read the text that should be in that field, it can't, so it gets stuck waiting for text that's never going to come.
We've tried various things to fix this, but none of them have worked. If anyone else wants to give it a shot, we're open to suggestions. Until then, all we can suggest is that you use the es Tweaker to uninstall the translation patch when you need to specialize a chip or upgrade a plug.
PSO2es is made in Unity, so all programming is done in C#. Until about halfway through 2019, Sega were leaving their C# .DLLs fully exposed in the game APK. C# code is very easy to decompile and read, and we were easily able to incorporate their database reading/writing libraries into ESBreaker.
However, a few months ago, they started using a feature of Unity called IL2CPP to build the game. IL2CPP compiles the C# code into an intermediary language, then compiles that into C++ specific to each platform the game's intended to run on. C++ is much, much harder to decompile, especially after it's been put through this process - that's the point of IL2CPP.
Despite this, our old version of their database library does still work - mostly. All text field types that were present before they switched to IL2CPP work absolutely fine and will continue to do so for the foreseeable future.
However, in the same update that they switched to IL2CPP, they added an extra text field to the Specialization/Plug-In menu. When we build our database, our copy of the library doesn't know that this field needs to exist, so it simply builds the database without it. When the game tries to read the text that should be in that field, it can't, so it gets stuck waiting for text that's never going to come.
We've tried various things to fix this, but none of them have worked. If anyone else wants to give it a shot, we're open to suggestions. Until then, all we can suggest is that you use the es Tweaker to uninstall the translation patch when you need to specialize a chip or upgrade a plug.