[joaquimandrade]

I take this chance to put here a non public plugin that I once made to prevent useless precaches.

Cvars:

precache_c4
precache_cz
precache_hl
precache_weapons

A cvar value 0 makes the plugin block that kind of stuff.
C4 is to block C4 stuff on maps without bombsite.
CZ is to block CZ stuff on CS.
HL is to block HL stuff. (made for CS)
Weapons is to block weapons that are restricted for the current map with the amxmodx feature to restrict (this takes 20 precaches for shield alone)

[Tirant]

thanks for sharing

[joaquimandrade]

Originally Posted by Tirant thanks for sharing

[Arkshine]

Your plugin is bad because you don't prevent the model be used. If a plugin gives a weapons or a user bypasses the restriction plugin (or others situations), it will nicely crash.

[joaquimandrade]

Originally Posted by Arkshine Your plugin is bad because you don't prevent the model be used. If a plugin gives a weapons or a user bypasses the restriction plugin (or others situations), it will nicely crash.

My plugin is imperfect, you meant!
I'm not interested in fix it but those cases can be easily prevented from the users of this plugin by removing the restriction of the weapon that can be used to crash. And even if this didn't work there were always the possibility of disabling precache blocking for weapons alone. So, the plugin is useful like it is.

[Arkshine]

that's not about being perfect or not, it's about blocking properly a resource.

A map giving weapons -> crash.
A map with given weapons -> crash.
A plugin giving weapons -> crash.
Whatever the thing using with a weapon model -> crash.
And probably others situations not thought yet.

Yes, for the users, it will be so easy to prevent that...

[joaquimandrade]

Originally Posted by Arkshine that's not about being perfect or not, it's about blocking properly a resource. A map giving weapons -> crash. A map with given weapons -> crash. A plugin giving weapons -> crash. Whatever the thing using with a weapon model -> crash. And probably others situations not thought yet. Yes, for the users, it will be so easy to prevent that...

It blocks precaches not loads. So it blocks properly what it is meant to block. If the owner of a server know it has maps that gives weapons that are restricted, he just has to remove the restrictions for them.

Anyway, with the plugin release it becomes easier to someone updating it and make it better. And people can benefit from it for normal cases. So, I prefer to let people enjoy it instead of having it taking dust.

If someone fixes it and wants to release it as a new plugin submission, feel free!

[Arkshine]

The first line is a nice joke. Thanks for the laugh. Next makes sense and I'm done here.

[Calibras]

Originally Posted by joropito I made this script to show how many entities are currently and what is the maximun number of entities. It's showing in logs using server_print and every 2 seconds. I made this for debugging purposes. Just compile, install in plugins.ini and when you want to start entity count debugging, issue a "rcon amx_debug_ent" command. If you send this command again, it will stop debugging. In my case, adding "-num_edicts xxxx" to hlds_run (in linux) worked fine. Also you can play with "-heapsize" and "-zone" options to manage memory limits. #include <amxmodx> #include <amxmisc> #include <engine> #include <fakemeta> #define DEBUG_PREFIX "[AMXX DEBUG]" new gDebugEnt = 0 new iTaskEnt = 99921001 public plugin_init() { register_plugin("Test Plugin", "0.1", "Piegtas") register_concmd("amx_debug_ent", "DebugEnt") } public DebugEnt() { if(gDebugEnt) { remove_task(iTaskEnt) gDebugEnt = 0 return } gDebugEnt = 1 set_task(2.0, "ShowEntStats", iTaskEnt, "", 0, "b") return } public ShowEntStats() { new iEntCount = entity_count() new iEntMax = global_get(glb_maxEntities) server_print("%s %d entities in world (%d max!)", DEBUG_PREFIX, iEntCount, iEntMax) }

Thanks verry much, that plugin helped me somehow help to figure out whats the problem with the zp i would think so.

[eduardolucioac]

Nice work!