[REQ] Per map plugin.ini

AndraX2000 · **Author**

Currently, you can only disable a plugin after a map has been loaded. Serveral users have had errors because of precaching plugins on maps with a lot of entitites. It would be nice if you could have a per map plugin.ini.

Attached is a modified version of meta_api.cpp which does just that. The ini files are stored in configs/maps/mapname.ini. For example configs/maps/de_dust.ini would be a plugin.ini file that would load for de_dust. If no mapname.ini file is fould, the default /configs/plugins.ini is loaded instead.

My C++ coding is a little rough so the request is that one of the programmers looks at the changes, cleans them up to make them match the AmxModX coding style and incorporate this into the source tree.

Thanks.

jopmako · 08-12-2006 , 12:23 Re: [REQ] Per map plugin.ini

nice point

BAILOPAN · 08-13-2006 , 12:19 Re: [REQ] Per map plugin.ini

This sounds like a good idea, however, I would propose a slightly different convention: file names being configs/maps/plugins-<mapname>.ini

AndraX2000 · 08-16-2006 , 21:18 Re: [REQ] Per map plugin.ini

Quote:

Originally Posted by BAILOPAN

This sounds like a good idea, however, I would propose a slightly different convention: file names being configs/maps/plugins-<mapname>.ini

Good point, that would probably be less confusing. Attached is meta_api.cpp with a change to that naming convention.

TheLinx · 08-16-2006 , 21:57 Re: [REQ] Per map plugin.ini

How about:

configs/plugins-<mapname>.cfg

like plugins-csdm...

SweatyBanana · 08-16-2006 , 22:27 Re: [REQ] Per map plugin.ini

You would want it in a seperate folder to keep it less cluttered.

TheLinx · 08-17-2006 , 05:49 Re: [REQ] Per map plugin.ini

Make it availible so you can customize that! You choose in amx.cfg or any other .cfg which path and where it should be

Xanimos · 08-17-2006 , 10:40 Re: [REQ] Per map plugin.ini

Right now how it loads those other plugins, it would load all those plugins at once it doesn't look for the name only that it has plugins-<something>.ini
so that wouldn't work in just configs.
Thats why BAILOPAN suggested using configs/maps/ which a lot of people already have this folder because of custom map configs. Plus that wouldn't be that much more difficult to use.

**Hawk552** · 08-17-2006 , 11:08 Re: [REQ] Per map plugin.ini

I noticed the maps folder doesn't actually come standard in the AMXX package. Maybe make it, and add one file inside like "de_dust" or "trainyard" and just some example config that's all commented?

AndraX2000 · 08-17-2006 , 12:05 Re: [REQ] Per map plugin.ini

Because the file paths are pretty much hard-coded into meta_api.cpp, it would take a substantial rewrite of the code to allow you to choose where the individual plugin.ini files are stored. It just wouldn't be worth it.
Keeping them as configs/maps/plugins-<mapname>.ini seems to be the cleanest, easiest to maintain solution.

Also, adding an example config that is completely commented would actually work out poorly. That is beacuse this doesn't work like the <mapname>.cfg files, which work by loading the <mapname>.cfg file in addition to the default server.cfg. This loads the plugin-<mapname>.ini file instead of the default. So a completely commented plugin-de_dust.ini would actually prevent any plugin from being loaded fo de_dust.

Attached are two sample files from my server. The plugins.ini file goes in configs/ (like normal) and contains some 3rd party plugins that we find fun. However, when we play de_dust, we like to turn off most of the third party addons. The plugins-de_dust.ini file goes in configs/maps/. Note that plugins-de_dust.ini is a complete plugins file. It still has all of the standard plugins listed.