Hax on the Top 25 Wealthiest board

[Zaxxon]

I think deleting the impossible scores should be top priority and the duplicate scores second. Re-theming would be fine, but is a distant third place concern.

[CommanderData]

Hi guys (and girls!), I have done some cleanup that helps visibly in the Top 25 Wealthiest.

1) Removed a few obvious cheaters
2) Removed some duplicates that were visible (and some that were not)

If you see other issues that I can correct (more dupes or hax) please let me know. Unfortunately the server is too slow for me to process a single MySQL query that can remove ALL dupes for ALL names at once, so I manually ran a de-dupe on obvious names that were in the list.


Interesting aside on the duplicates:
Apple used to allow the UDID (unique device identifier) to be read by applications. This was what RT used to grab to "identify" the gamer, not in a truly identifiable way, but at least it would ensure you didn't post the same scores multiple times when accessing the server.

Bad things started to happen as people migrated to new devices and copied the Hall of Fame files with them, they would get re-submitted with a new UDID.

Even more bad things happened after Apple removed UDID access from apps. Then all we had was an "advertising identifier", which is re-randomized whenever you install the app or whenever Apple or the Device user desires. That creates MORE duplicates!


I've changed the PHP routine that stores new Hall of Fame data on the server, so it will IGNORE the UDID / advertising identifier field. Instead it performs a query on the database to see if any entries match the data you are uploading (name, rank, floor reached, gold, number of steps/kills, etc).

If it finds a matching record already there it won't insert another anymore

[Zaxxon]

I'm probably talking out of school, but doesn't Rogue Touch generate a fairly random "seed" number when it creates the dungeon? Maybe start saving/sending that with the score and have the board only accept one score per dungeon...?

[CommanderData]

I'm probably talking out of school, but doesn't Rogue Touch generate a fairly random "seed" number when it creates the dungeon? Maybe start saving/sending that with the score and have the board only accept one score per dungeon...?

Hi Zaxxon,

It's a good idea but unfortunately Rogue Touch is so old-school it actually doesn't use a single pre-generated seed in sequence for the world generation

Rogue Touch 2 and Spirit Hunter Mineko actually are being designed with a seed system, my hope is to be able to share seeds for competition purposes and stuff. Logging those with the player's run will also allow us to group together everyone who played on the same seed.

In that case we'd actually still allow multiple loggings per seed, but if more than one individual was seen with the same seed value they all get ignored on the primary leaderboard and appear on the "seed competition" board instead

[Nighthawk]

Rogue Touch 2 and Spirit Hunter Mineko actually are being designed with a seed system, my hope is to be able to share seeds for competition purposes and stuff. Logging those with the player's run will also allow us to group together everyone who played on the same seed.

In that case we'd actually still allow multiple loggings per seed, but if more than one individual was seen with the same seed value they all get ignored on the primary leaderboard and appear on the "seed competition" board instead

"Daily Seed runs" should be a one-shot and done system, handled on the device end so that players can only take one shot at it. Allowing multiple attempts at the same daily seed would just be baaaaaaaad.

After that day, then "publish" the seed so that a player can go back and try it again a few times. Obviously, these attempts shouldn't be recorded on any leaderboard other than the player's local device.