The following warnings occurred: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Warning [2] Undefined variable $data_size - Line: 3 - File: inc/plugins/sharethispage.php(362) : eval()'d code PHP 8.1.28 (Linux)
|
Fun with numbers.. - Printable Version +- The House of JUSTiSO - A Clash of Clans Community (http://www.justiso.net) +-- Forum: The H.O.J. - A "Clash of Clans" Community (http://www.justiso.net/forumdisplay.php?fid=7) +--- Forum: Clash of Clans - General Discussion (http://www.justiso.net/forumdisplay.php?fid=8) +--- Thread: Fun with numbers.. (/showthread.php?tid=412) |
Fun with numbers.. - Zooks - 07-19-2014 So as we were discussing, here's a project from a while ago I'm sure you'll find interesting. It's since been abandon though because the client server nature of things was making for a bit of a grey area. This is address manipulation so its technically perfectly legit so long as its preformed on MY computer... Where in lies the problem however is that without decompiling the source it becomes very difficult to track how and more importantly "where" updates are being made. So anyway... take a look.. [attachment=101] First, we attempt to locate the appropriate memory address by tracking a recent value change. In this case, I had just removed a bush and was awarded 4 gems -- the address I'm seeking was recently updated from 452 to 456. [attachment=102] Next, we apply a change to one or ALL found locations in an attempt to update the correct address directly without completely bringing the OS to its knees . [attachment=105] As you can see, this attempt proves successful to the tune of 99,999. [attachment=106] The joy is short lived however - after plugging away for some 12K in straight gem upgrades, the server detects a discrepancy and say's "Ut-Uh". On reboot, all values and upgrads are returned to "pre-modify" status. Booooo. The end.. or for you nerd types... -EOF |