-
-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let's talk about new features in plugins #609
Comments
Slots Reservation
|
Info. Messages AND Scrolling Messages |
Nextmap Chooser player can nominate (with maps menu), vote for change map and another... |
GaG/UnGag |
Menu |
Admin If we been divide plugin to two - then need all of the penalties and restrictions of the player to move to another plugin. May it be so: Players restrictions (Ban, Kick, Gag, API) |
Slap/slay |
Team Balance
|
what do you mean? |
To all: Just giving existing plugin doesn't help much. We need a concrete list of features. It's kind of hard because all the plugins need to be overhauled. We need to keep compatibility too. Well, let's try anyway. |
Slots Reservation Add the function kick spectator or AFK after a preset time.. |
@Arkshine Ok i edit my previous post later |
I wanted to do something similar to SM. We need an API for plugins too. |
@Arkshine i mean this. if we have 2 reserved slots and this slots are busy. We should search player to kick from server. To free up space for a reserve slot. |
Since The only change required in the core is modifying client_print(id, print_chat, "This ^4is ^3a ^1test ^4message^1.") Result:
|
I think kicking most recent player can be default behavior. |
I don't mind, but it should have a config for that, people may not like suddenly having color everywhere. About symbol, amxx strips them from a language file, I guess this could be done for client_print_color.
Admin stuff needs to be a little more advanced, similar to SM, but yea, temporary admins has been requested several times.
I'm not sure. If we didn't have amxx.cfg with cvars already put inside, we could have used AutoExecConfig everywhere, but now it will be annoying for the user on upgrade if we move all the cvars related to the base plugins. Don't know, need more feedbacks on that.
I'm not against, but really not a priority, and you should list exactly what command you would want to include. |
Add Kickmenu with reasons. |
A cvar can be added to toggle the colors, it's not really a problem. Like you said, the only struggle will be adding the color symbols for all languages - but it's not something undoable. We should probably follow a simple rule when adding them, e.g. player names in team color and values in green, everything else in default color, so basically we need to add the colors before any I can do this if you make the
When you think about it, it's much more annoying as it is right now because with every new cvar added in AMXX, users will need to manually add that cvar in |
I'd like to add natives to kick/ban player, using server_cmd triggering me every time |
I'm with adding AutoExecConfig for new cvars its frustrating to keep to track of these cvars or make amxx.cfg file to be generated only once like AutoExecConfig so that its not override every time a new cvar is being added. |
Yeah, we can also use |
Refereed to #581 :
Other:
|
These are all mod-specific gameplay elements and should be altered with 3rd party plugins, just the way it has always been. |
Actually I'm developing with ReHLDS, ReGameDLL and ReAPI. In release notes it's cited that it has now official support. What really was changed? |
AFK kicking is a quite general, but it shouldn't be enabled by default like teleport. What about resetscore: looks like all GoldSrc games have some score systems, so it seems to be general too (but an implementation is game-specific, yeah).
All natives/forwards that require hooking the engine functions or searching in the engine are supported for ReHLDS/ReGameDLL. |
Add amx_mute for voice chat. |
Make it as the server owner can choose to set on/off this feature (Feature 1), please, i use xRedirect for this specificly and i don't need players to be kicked, good idea btw. |
^^ No memory leak ^^ |
So far I remember HLDS is well known for leaking memory. It's old, bugged and unmaintained. You can check with Valgrind. Also, if you have a lot of activity/plugins and alter often the game, you will accumulate garbage and HLDS can do weird things at some point. Admins are not necessarily coders, and you can do nothing about HLDS, it's just easier to start from a clean state when you can. |
And what about servers like Death Match? I think, Cvar should be added !!! roundendtime "1/0" (1- New Behaviour)(0- Old Behaviour)? NextMaps - Allow the last round to be finished even if the timelimit has expired |
|
CS StatsX with kill assists and SQL db? Other idea: |
Hi, I have a request for the Albanian language support. |
@4D1G06 It doesn't make sense to request from the AMXX devs to translate a specific language - of course less than 10 people don't speak all the languages in the world. Everybody is free to participate in this project. You can translate it yourself and submit a pull request. There's already a pull request for that language - #684 , so you can join the discussion there and suggest any improvements. |
Plugin Menu - #735 (comment) |
Are there any plans to add write Kick Reason, with amx_kickmenu. |
I guess, this can still be considered a request for AMXX v1.10 and a good one. It's about the Orpheu module. I think it would be cool if such module is improved, with Vector support added like Okapi. And, ofc, it beeds to be included in AMXX v1.10 . This way will make it possible to hook functions that are otherwise only possible yo hook with Okapi. Since Orpheu reads from files rather than havibg the sigs/offsets hardcoded, I think it's better if Irpheu is included instead. It also makes it easier to hook functions like pfnKeyValue for example. It's not too late. Maybe CS and the other games are dead but, at least, let us, those who still code for such dead games to be able to make amazing things without having to use other additional modules. I really hate how Okapi is hardcoded and if u want to support multiple mods for each new 1 u have to edit the plug-in again and again. With Orpheu it is much easier, allowing u to make a json-parse file without having to edit anything from the plug-in. |
@DarthMan this topic is about plugins, not modules |
Yeah it is not, but I requested that it comes with the default amxx package. And I seee no other place to post it on. |
Nextmap Chooser |
Add rock the vote to default Abstract Machine Executor X base package and a new command revote in case you chose the wrong map by mistake you can just type revote and choose a new one. |
Port AdminMod Map-Nomination-Vote Plugin into core for rockethevote and nominate. |
Avoid usage of setinfo for terrible _pw, i think some users reported that can be stolen (If really can!) LOL |
Multi-language system
|
Totally, we can create plugins where we can use ge_user_info to get the passwords of any player we see and ask him if he's an admin on server then make him lose his admin and that's kinda bad. |
Admin Help
|
That would be chaotic and totally unfunctional. No auto-translating system is 100% accurate and players rarely write properly in chat, which will make the translation even that more unusable. Menus and other plugin stuff should be translated manually. |
Having that many messages printed in the console at once can get the client kicked out from the server. That limitation is there for a reason. |
The ability of having Also, admin menu in chat, like /slay /slap /kick. |
@TibyXD those commands are redundant when you have |
painshock_value (movement slowdown value when the player get hit) |
Six years have passed, and none of the new features mentioned here have been implemented. Should everyone give up? |
AMX Mod X is not actively maintained by anyone anymore. It is over 20 years old. If you're interested in taking over, feel free to submit some pull requests.-DavidOn Apr 16, 2024 5:23 AM, all85100 ***@***.***> wrote:
Six years have passed, and none of the new features mentioned here have been implemented. Should everyone give up?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
I'm sorry, guys. The lack of general interest and IRL catching me up did not help me focus on the AMXX project. If I have the opportunity to come back, I will, but right now, I can't. Hopefully, someone can take over and continue working on it. 🙏 |
At least make 1.9 the default stable build, replacing 1.8.2 which is quite old. |
I think project managers still need to take the time to deal with the right and reasonable Pull requests, |
Before we go wild on plugins, we should discuss what changes/new features/new plugins would be welcomed for each plugin. It will be easier to manage people's ideas and we will get a better overview of the work to do. We can also sort them by priority and whether they are unwanted/out-of-scope/impossible/etc. Some changes may require modifications in core, therefore it's important to discuss everything beforehand.
I will try to update below based on the proposed changes.
waiting for feedbacks
- API: kick/ban players - A player's command to reset stats - `amx_slay` with ` @` (e.g. for CS: @ALL/@CT/@t) - Enforces sanity checks on command arguments
- Hide menu instead of being visually disabled for player who doesn't have the access level
- Ability to choose a reason before a Kick/Ban - A command `amx_team ` to open a menu with found players - An option if the player doesn't have access to `amx_slap` or `amx_slay` to make sure the player can't use that through the Slap/Slay Menu. - Don't harcode data (such ban time, etc.)
- If all slots are used, ability to search a player to kick based on certain criteria (spectator, defined afk time, etc)
- Restriction on touch - Ability to limit the amount of a weapon that can be bought/in the world - Ability to make specific weapons accessible only to people with a specific flags
Potential new plugins:
The text was updated successfully, but these errors were encountered: