I'm working towards building custom edit modes that can support SA PS2 and mobile versions for III and VC, but first I wanted to bring my SA Mobile mode up to speed with PC, and that means finally straightening out the global variable names.
SA Mobile - Standard Files v3.2.2
SASCM.ini - opcode processing
opcodes.txt - Opcode Search text
custom.dat - loads IDE files for model ID numbers
default.ide - loaded by custom.dat
peds.ide - loaded by custom.dat
vehicles.ide - loaded by custom.dat
veh_mods.ide - loaded by custom.dat
CustomVariables.ini - Format option: Custom Variable names
keywords.txt - shortcuts for common opcodes
missions.txt - original mission names option
american.gxt - standard file, adds comment strings for GXT keys
SA Mobile - Test Files
SASCM.ini - CleoA update
opcodes.txt - CleoA update
custom.dat - with IDE lines from default.dat and gta.dat (see below)
CustomVariables.ini - matching all common Variable names with PC
CustomLabels.ini - matching Labels with PC
CustomArrays.ini - matching Arrays with PC
american.gxt - looks like this file gets updated with patches
802 12 Girl_Weapons 1219 8 Airport_Gates
This is just the IDE lines taken from default.dat and gta.dat. These could be read automatically if SA Mobile's game directory is set to Sanny's data\SA Mobile folder, but that seems like an awkward place to sync my compiled and copied scripts. And these files seem more appropriate under the custom edit mode folder anyway.
Update: Since SA Mobile doesn't Compile + Copy it would probably be easier to simply set the game folder to Sanny's edit mode's data folder and manage file copying manually than trying to manage a custom.dat file..
The data\maps\ files are contained within main.8.com.rockstargames.gtasa.obb. Rename a copy of the file to a zip extension to extract. patch.8.com.rockstargames.gtasa.obb holds the files from the \data directory.
Update: I ran WinMerge on my IDE files for PC and SA Mobile and the files are nearly identical. The only differences are to a handful of draw distance figures. The object IDs are all the same, which suits this purpose nicely. PCv1 and PCv2 are identical. I know from previous experience that many of the PS2 object IDs don't always match with PC.
american.gxt seems to be locked away in an APK file somewhere. I'm still not sure how to get at it.
Cleo for Android Opcodes and Text
SASCM.ini supplement - append to the end of file.
opcode.txt supplement - append, no need to sort