Dobrodosli u Samp Forums-Srbija. :D
PrijemKalendarČesto Postavljana PitanjaTražiLista članovaKorisničke grupeRegistruj sePristupi

Delite | 

 <<<<::::: About memory hacking plugins:::::>>>

Ići dole 

Broj poruka : 10
Datum upisa : 15.04.2011
Godina : 22

PočaljiNaslov: <<<<::::: About memory hacking plugins:::::>>>   Pet Apr 15, 2011 4:05 am

Can i create topic about Structure Access plugin in plugins forum ?
In short, no.

At present, information contained in the SA-MP server structures are designed to be accessed using pawn, not by peeking and poking the server memory.

Plugins are designed to extend pawn. If there is information that cannot be accessed by scripting, people should request it added to SA-MP's pawn scripting natives. I'm positive 90% of the information held by the server can already be accessed using pawn.

Memory addresses and structures within the SA-MP server change with every release, pawn natives do not. If a plugin is coded to access specific memory addresses, backward compatibility for server owners will be broken with every server update.

There are variables that we do not want the server owners tampering with; such as the amount of players on the server, version information, and read-only console variables. Servers that fake this information end up being blocked from the server lists and it costs us time researching whether these servers are breaking the rules (not fun).

This might change in future versions and plugins might be given direct access to some of the structures/classes. However, SA-MP is not designed to be 100% extensible. There seems to be a lot of confusion on this subject. SA-MP is designed to be largely configurable by server owners while still making the game moderately consistent for the players across different servers. That means, first and foremost, SA-MP is still a multiplayer extension for GTA: San Andreas. It doesn't pretend to be its own game engine.

What about hooking to callbacks(such as used by Y_Less in Multithread). Such option must be implented either by hooking or providing additional function in SDK.
Pawn is not threadsafe. The only way to interact with pawn from threads is to implement a ProcessTick function. If you start dealing with pawn from a thread that isn't synchronised with the server's main loop, it's likely you'll be calling in to it at a time when it's already doing something else.

Callbacks are not designed to be hooked or used in plugins. The plugins provide functionality to the pawn script, they're not designed for gamemode related code which the callbacks are intended. If you did need access to a callback from the plugin, you could have a script (probably filterscript) call a plugin function when it receives the callback. This is a much cleaner way than trying to hack memory addresses.
Nazad na vrh Ići dole
Pogledaj profil korisnika
<<<<::::: About memory hacking plugins:::::>>>
Nazad na vrh 
Strana 1 od 1

Dozvole ovog foruma:Ne možete odgovarati na teme u ovom forumu
Samp-Srbija :: ::.Plugin Development:::.-
Skoči na: