[DJEarthQuake]

Safemode loads server without Amxx on select maps.

HOW TO USE:
First backup plugins.ini as plugins.ini.backup. Make safe_mode.ini and add maps.

. ├── amxmodx │ ├── ACKNOWLEDGEMENTS.txt │ ├── configs │ │ ├── amxx.cfg │ │ ├── clcmds.ini │ │ ├── cmds.ini │ │ ├── configs.ini │ │ ├── core.ini │ │ ├── custommenuitems.cfg │ │ ├── cvars.ini │ │ ├── maps.ini │ │ ├── miscstats.ini │ │ ├── modules.ini │ │ ├── plugins.ini │ │ ├── plugins.ini.backup │ │ ├── safe_mode.ini │ │ ├── speech.ini │ │ ├── sql.cfg │ │ └── users.ini

Example safe_mode.ini.

//Optionally add up to 24 plugins on top line. Use Map_Specific_Plugins as needed.
"op4ctf_chasm" "plugin1.amxx" "plugin2.amxx" "plugin3.amxx" "plugin4.amxx" "plugin5.amxx" ...  "plugin16.amxx"
"op4ctf_crash"

Original.
Latest version.

[fysiks]

Randomly using syntactical tricks that the compiler is OK with but that makes the code harder to read for no reason is completely and utterly ridiculous. For example, randomly leaving out parentheses for functions calls is dumb (it also breaks certain intelligent code editors like AMXXPawn for VS Code).

What does this plugin have to do with "safety"?? I don't see any "safety" related functionality, though it's kinda hard to understand what your plugin does at all. What does this plugin actually do?

To prevent plugins from running on certain maps that have too many models cached, you should simply use the per-map config and plugin files that are built into AMX Mod X.

You have a whole bunch of plugins names that are hard coded into this plugin which makes it not suitable for a public release.

If you do want/need to modify the behavior of plugins in plugins.ini, you don't need to edit plugins.ini at all. There is a feature in AMX Mod X that allows you to modify the plugin list without using plugins.ini. Any file in the configs folder that begins with "plugins-" and ends with ".ini" will be loaded after plugins.ini allowing you to enable or disable plugins from there.

Regarding calling this from other plugins, if you're writing the code of the plugin that is being called by another, you don't need to use any callfunc_*() commands, just build in proper natives that can be used elsewhere like it should be. Using callfunc_*() should only be a last resort for plugins that can't practically have natives added.

[Jhob94]

The only way to resolve the 512 error you must not precache over 512 models/sounds/sprites.
Check precache kit on my signature for more information.

[DJEarthQuake]

Thanks for the feedback. It makes a short plugins.ini list from base system. Nothing unreleased. This happens just before the map is loaded however it is called. Using natives makes it more of a project to install for admin as well as all the work involved with cache manipulation configs. Both too complex for regular admins to install. Those are deterrents. When host has myriad of plugins typing out disabled alongside each one in the built-in ini system is not going to work, it is loaded too late. In fact avoiding use of it by-and-large except for adding a plugin back by prefix on occasion and use this 1 file instead of many option instead is safer than removing cache items IMHO. Windows has a safe mode which loads a minimal set of drivers. Name was inspired by that. There are no third party plugins forced and hard coded anywhere. Users make their own safe_mode.ini or don't. If you are talking about a piece of my for the sake of an example config, that's what eg means. Users make their own. Just list the map name. Add up to 12 plugins to sandbox. True safemode would be starting with no plugins then adding one at a time. It is much easier to manage on 1 file. Precaching is not the only way. It takes something away from the map I thought.

[fysiks]

Originally Posted by DJEarthQuake Thanks for the feedback. It makes a short plugins.ini list from base system. Nothing unreleased. This happens just before the map is loaded however it is called.

plugin_end() is always called before the map actually changes. Any plugin file modifications can be done here (I do this successfully in one of my plugins). Also, your plugin can't properly handle any plugins loaded in any other plugin INI files so it just doesn't make sense.

Originally Posted by DJEarthQuake Using natives makes it more of a project to install for admin as well as all the work involved with cache manipulation configs. Both too complex for regular admins to install. Those are deterrents.

Nothing in this statement is true. Using natives changes nothing about installing the plugins for the admin.

Originally Posted by DJEarthQuake When host has myriad of plugins typing out disabled alongside each one in the built-in ini system is not going to work, it is loaded too late.

That makes no sense. It's not hard to comment out plugins in plugins.ini. Using "disabled" is only needed when you're using map-specific plugin INI files alternate plugin INI files.

What is loaded too late? Late relative to what?

Originally Posted by DJEarthQuake In fact avoiding use of it by-and-large except for adding a plugin back by prefix on occasion and use this 1 file instead of many option instead is safer than removing cache items IMHO.

What is are "cache items"? There is no concept of "cache" with respect to loading plugins.

Originally Posted by DJEarthQuake Windows has a safe mode which loads a minimal set of drivers. Name was inspired by that.

This type of debugging is rare and is so easy that you don't need to complicate it with a really confusing plugin.

Originally Posted by DJEarthQuake There are no third party plugins forced and hard coded anywhere.

I didn't say anything about "third party plugins". There are several plugins hard coded here. Not everybody will necessarily have or want to use the default plugins, even in "safe mode".

Originally Posted by DJEarthQuake Precaching is not the only way. It takes something away from the map I thought.

Prechaching has thing to do with this, not sure why you mention it.

[DJEarthQuake]

Anything to do with cache was per Jhob94’s comment. Everything else yours.

Editing safe_mode.ini, one file, in configs directory putting map name down instead of modifying multiple files in configs/maps every time plugins are added is incomparable. It’s significantly less work and without margin of error.

There is a delay before configs/maps is reached. Plugins are all loaded before some are disabled. That’s when the crashes occur.
https://github.com/alliedmodders/amx...b4bfc5bb343362

On the plugin end. When I first tried this on plugin_end it did not work 100% of the time or at all. That was years ago and I did not make any notes. So I checked when maps change, what plugins are responsible. That handled it in all situations. If you are saying I can make it work with less work, I am open to that. Thank you.

There are some other ideas that I can test to address plugin_end consolidation again.

Admin.amxx is part of the base system and that was put in as a fail-safe so admins still are admins when using this plugin. If I did not put it there, Amxx is completely hosed until somebody gets to the console or waits for nextmap. Either way that’s unprofessional. Suggesting admin.amxx as a 3rd party plugin is rather Orwellian.

What I thought about was 2 plugins.ini. One for base system and other for all 3rd party plugins. I used to do that.

Base is always loaded then if map is not on the list the other 3rd party plugins.ini is loaded. Once again with the timing plugin_end was not keeping up or I thought I tested there and didn’t.

[fysiks]

Not sure how you came to the conclusion that the using the basic built-in functionality is all that hard.

I've used plugin_end() to modify which plugins are loaded since 2009 (14 years ago).

Your plugin is hard coded in several ways making it untenable for generic use. Just keep it to yourself unless you're planning on removing all the hard coded plugins and limits.


P.S. I'll try to ignore this thread from now on since you're not making any sense.

[Jhob94]

Originally Posted by DJEarthQuake Precaching is not the only way. It takes something away from the map I thought.

I have no idea what you are talking about. The error, as it says, is about precache. If you want to remove something you must unprecache the wanted files.

[DJEarthQuake]

Plugin updated. All discussed issues addressed. Utilizing plugin_end. Softened code.

[DJEarthQuake]

Originally Posted by fysiks For example, randomly leaving out parentheses for functions calls is dumb (it also breaks certain intelligent code editors like AMXXPawn for VS Code).

Never noticed since I use CLI like NANO. Merely placing a semi-colon after enum declaration. That fixes it. Functions show in the Symbols sidebar. Parenthesis has nothing to do with it. I checked.