What about CamelCase style for all spmod plugins api?
I don't really mind if it is CamelCase or camelCase, I used camelCase for first native and just kept that styling.
- cvar manager, something fast as cvar pointers in amxx
That could be implemented later, it's not "must be" right now. But could be implemented by someone else. I'm open for any PRs.
- message manager
- event manager
- menu manager
Those will be implemented, but I can't tell when, now I'd like to focus on command manager. If someone has some free time to spare, I'll welcome any contribution.
engine specific module: prethink, addtofullpack, etc
Those will be implemented later, when querying modules will be done, but there will be just engine module, not like in amxx where we have two modules engine & fakemeta, then people won't be confused which one should they use.
game specific modules: cstrike, others
As same as engine module, at first I'd like to have core functionality more complete, then start to work on them, cstrike will be using regamedll api, there will be modules for games: DoD and TFC (most popular ones?). I don't want to add other game specific module unless someone wants to code it and then maintain it, because I don't feel like keeping dead code.
- packetmanager for plugins/modules?
Could you elaborate more? Do you mean DataPack or something else?
Do you want copy code from sourcemod or write own?
I look at sourcemod and amxmodx mostly for reference, but I don't deny that I may copy some code in the future.
Thanks, fixed.
