AlliedModders

AlliedModders (https://forums.alliedmods.net/index.php)
-   General (https://forums.alliedmods.net/forumdisplay.php?f=7)
-   -   Innapropriate flag for telemenu in amxmodx (https://forums.alliedmods.net/showthread.php?t=304288)

Fr33m@n 01-10-2018 09:55

Innapropriate flag for telemenu in amxmodx
 
In my server, admins like to use teleport plugin from amxmodx base package.

But the fact that it's linked by default to flag "h - amx_cfg command" aka ADMIN_CFG is a bad thing.

This flag have nothing in common with a teleport feature, and i bet that many server managers who want to give teleport ability don't want to give the ability to mess in cfg.

That why i purpose a poll for selecting a different flag and we will commit those changes in amxmodx 1.8.3 rather than relying on client changes.

I have selected a few candidate and i will list them :

m - custom level A (for additional plugins) or ADMIN_LEVEL A
While it's not for say an additional plugin since it's included in the base package, it still not enabled by default in amxmodx config. So it still an addition. Plus it's not conflicting with other function provided by flags.

c ADMIN_KICK or d ADMIN_BAN or e ADMIN_SLAY coud be more common candidate, but they will interfer with the specified functions.

fysiks 01-10-2018 09:57

Re: Innapropriate flag for telemenu in amxmodx
 
Changing the default will break backwards compatibility.

klippy 01-10-2018 10:04

Re: Innapropriate flag for telemenu in amxmodx
 
Are you talking about amx_teleportmenu?
In that case, cmdaccess.ini exists for that exact reason.

Fr33m@n 01-10-2018 10:07

Re: Innapropriate flag for telemenu in amxmodx
 
Quote:

Originally Posted by fysiks (Post 2571044)
Changing the default will break backwards compatibility.

A valid example of a "break" could be welcomed because we are talking about constant in base plugin, not the amxmodx architecture itself.

For my point of view, there is not that much imcompatibity. I'm a coder, and i'm well aware about amxmodx plugins or coding stuff, so please give me a valid example.

Fr33m@n 01-10-2018 10:09

Re: Innapropriate flag for telemenu in amxmodx
 
Quote:

Originally Posted by KliPPy (Post 2571046)
Are you talking about amx_teleportmenu?
In that case, cmdaccess.ini exists for that exact reason.

Well, i'm well aware of that, but it was more for simplify the thing for regular user.

klippy 01-10-2018 10:12

Re: Innapropriate flag for telemenu in amxmodx
 
Quote:

Originally Posted by Fr33m@n (Post 2571048)
Well, i'm well aware of that, but it was more for simplify the thing for regular user.

Well cmdaccess.ini is exactly there to simplify things for a regular user. They just have to edit one character in a file instead of recompiling the plugin. That's why cmdaccess.ini was created in the first place and changing it is by no means advanced and every server administrator using AMXX should know about it.

fysiks 01-10-2018 19:56

Re: Innapropriate flag for telemenu in amxmodx
 
Quote:

Originally Posted by Fr33m@n (Post 2571047)
A valid example of a "break" could be welcomed because we are talking about constant in base plugin, not the amxmodx architecture itself.

For my point of view, there is not that much imcompatibity. I'm a coder, and i'm well aware about amxmodx plugins or coding stuff, so please give me a valid example.

Your point of view as a coder does not give your opinion about backward compatibility any more weight. Also, your justification is purely subjective and that makes it ineffectual.

For a default value like this, you have to first consider the regular user who doesn't fully understand the back end stuff. They will not understand or know where to look when things stop working when they upgrade to the next version of AMX Mod X. For the standard user, there should be no changes to default values when there is already built-in features specifically for changing this value on your own server.


All times are GMT -4. The time now is 14:53.

Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.