Quote:
I am writing a plugin will do a lot of work every frame and use quite a lot of memory, so it might be worth trying to write a extensions instead.
|
This is probably a false assumption, SourcePawn is extremely efficient especially if you're just doing calculations / logic on the plugin side (there is a small performance penalty to calling natives). It is very rare for plugins to even be measurable against all the work the game server does every frame, and there is absolutely no benefit to consuming memory on the C++ side rather than the SP side.
Quote:
The other way is to still write a plugin, after getting required data and pass to extension.
|
This is what the extension API is explicitly pushing you towards - and is why it doesn't have any interfaces for invoking SM natives or much in the way of game APIs. Extensions should be small, reusable components that provide functionality that plugins can't do natively - and they have less and less relevance in the era of things like DHooks.
__________________