[Slice]

It's understandable that the SA-MP team can not focus on patching non-critical bugs and implementing all the features the community wants.

Some plugin developers have begun going over many of these things. It is, however, very time consuming and not at all future-proof to spend countless hours "memory hacking" the server.

Given the right prerequisites, the community would thrive in this area. By implementing low-level, but consistent, APIs for plugin developers, the SA-MP team would allow the community to keep SA-MP evolving in-between versions.

Some examples of easy to make, but very useful APIs for plugin developers:

• Allow plugins to capture, modify, and discard incoming/outgoing RPCs
• Make some internal structs/classes public (sync data, vehicle data, ..)
• Disclose the list of RPCs

The reason many great plugins die is nobody has the time/effort to do the work of finding memory addresses and such with every new release.

Some things that could be achieved and future-proof with the proposed changes:

• An NPC plugin that gives full control over the NPC
• Fixing sync bugs as they are discovered (infinity shooting, sliding, knives, etc.)
• Many new scripting functions (many sought-after Do/Set X ForPlayer, for instance)

One final point: doing this would slow down the currently ongoing reverse-engineering of the client/server.