You're mixing two different problems. Read this before you touch anything.
1. First find out where the value lives. That decides everything.
Open GameGuardian on a rooted device, search the number, use the item, search again. If it holds after a restart, it's local. Edit the save (SharedPreferences xml, SQLite, /data/data/...) and you're done. If it snaps back after the game syncs, the server owns it, and no amount of smali editing will make it permanent.
2. Nobody has "the full app code". There is no source.
An APK is dex + native libs. What modders actually do:
- jadx to read the Java/Kotlin, class names, method names, and the whole network layer
- Il2CppDumper for IL2CPP games, you get the function list from libil2cpp.so + global-metadata.dat
- IDA or Ghidra on the .so when the logic is native
- Strings and endpoints to see what the server accepts and returns
That is the "information" you're asking about. It's not leaked, it's read out of the binary.
3. "Bypassing the server" means lying to the client, not changing the server.
Find the endpoint or the JSON model, hook the response so the client thinks it has 99999, or patch what the client sends. Two walls you will hit: certificate pinning (bypass with Frida or patch the pinning class) and payload signing or HMAC (must be recomputed or stripped). If the game is login based and validates on sync, your number is cosmetic until it re-syncs. That's normal, not a bug.
4. Do this in order: offline game, edit the save, then a game with local currency and a client side check, then a networked one. Jumping straight to an online game is why rookies give up.
Tools: MT Manager, apktool, jadx, GameGuardian, Il2CppDumper, Frida.