Wenn dies dein erster Besuch hier ist, lese bitte zuerst die Hilfe - Häufig gestellte Fragen durch. Du musst dich registrieren, bevor du Beiträge verfassen kannst. Du kannst auch jetzt schon Beiträge lesen. Suche dir einfach das Forum aus, das dich am meisten interessiert.
A couple weeks ago, an exploit was discovered in which Necromancers could receive an unfairly high advantage over other classes. Utilizing this exploit required both implicit knowledge and intention to execute and, as a result, we are issuing account suspensions and removing affected records from the leaderboards.
You may be wondering why we're executing this now rather than when we originally fixed the exploit; the long and short of it is that this was a very complicated issue to track and we are, as always, dedicated to ensuring we are not punishing players who may be innocent.
Thank you for your patience and understanding while we work to maintain as honest and fair a gaming environment as we can.
Structs had static addresses in the past. At each patch (due to recompilation) those changed and I had to "teach" HUD to the new addresses.
Now the static addresses are gone, and they are dynamic every single time you start the game (I am not sure if they can change while the game is running).
Even if HUD could dynamically detect those addresses, it would be slow (full memory scan) and the other problem is a new kind of "trap" which cause a game client crash if you reach the trap.
So a full memory scan is not even easy to archive, however there is a solution: pause the game process, scan the memory for the addresses and then resume.
Also there are other changes (for example, a very vital property called PlayerDataIndex is gone from the memory and it is/was used to know which player is yours in the game) which makes the life even more complex...
Based on the above, I think there is only slight chance that HUD will ever work.
Kommentar