[Suggestions] AMXX 1.8.3
 

--------------------------------------------------------------------------------------------------------
Suggestion List
--------------------------------------------------------------------------------------------------------

1. Drop/Strip functions with the ability to drop weapons by weapon slot/index plus the possibility of stripping/dropping multiple weapon slots/indexes at once (ex. drop both primary and quaternary weapons / drop CSW_AK47 and CSW_DEAGLE)

2. Set user max speed native (automatically overwrite the speed value of the player when switching weapons with the specified value, similar to what cs_set_user_model native does for player models)

3. Set user weapon and view model natives (automatically overwrite the weapon/view model of the player with the specified model, similar to what cs_set_user_model native does for player models)

4. Player spawn forward with both pre and post hooks, with the ability to block any kind of spawn by returning the forward handled

5. Forwards/Natives to allow players to block/terminate a round

6. Gag functions included in the plugin package of amxmodx

7. Split slay/slap menu into two different menus

8. Forward for when a client is completely connected and natives/commands can be executed on them (like 3 seconds after client_putinserver)

9. cs_set_user_team should automatically enforce the specified team internally to avoid issues when using the native on players who didn't select a team previously

10. Forward to intercept/hook cs_set_user_team native

11. Forward to intercept/hook when user flags are changing

12. Including nvault_utility into the main amxmodx package

13. Cvar to allow map change only at the round end

14. Removing the money limit for counter strike ( controlled by cvar )

16. Round end events should be also called on round restart, along with adding a parameter to tell whether the round ended with a restart

17. New round / Round start events adding a parameter to tell whether it is the first round of the game or not ( first round should be defined as first round after map change, first round after round restart )


--------------------------------------------------------------------------------------------------------
Note
--------------------------------------------------------------------------------------------------------

Please note that these suggestions are mainly meant for counter strike and not for other game modes

Re: [REQ] Amxmodx 1.8.3 natives
 

Feature requests like this should be submitted via bugzilla with severity set to "enhancement".

https://bugs.alliedmods.net/

Re: [REQ] Amxmodx 1.8.3 natives
 

It's better request it via Github: https://github.com/alliedmodders/amxmodx

Re: [REQ] Amxmodx 1.8.3 natives
 

The forum is fine for discussing something if you are unsure. Ideally, once discussed, you should file a bug report as easier to track the issue, or if you can code, making a PR on GitHub.

About the natives, I don't know.

Re: [REQ] Amxmodx 1.8.3 natives
 

Come on Arks, it would be great to have them, you will make our lives easier :P

It's too 2005 to hook Ham manually for this kind of things... especially if you are working on bigger projects which are split into several plugins

It really drives me nuts using APIs or doing these things manually

Re: [REQ] Amxmodx 1.8.3 natives
 

I don't agree with you. Such things are very basic and anyone should know how to do them properly. Adding a native for everything does not seem resonable, especially when it isn't hard to do directly.

Btw, Ham did not exist in 2005.

Re: [REQ] Amxmodx 1.8.3 natives
 

The natives would not make sense. Expected behavior is for the view model to change when you deploy a different weapon. It's not like a player model where it's expected to remain the same. Would you want your knife view model to remain when you switch to an AK47?

Practical usage wouldn't be any different to using fakemeta or engine.

Re: [REQ] Amxmodx 1.8.3 natives
 

@The speed natives

I don't know how this can not be useful... i mean seriously, would you rather hook ham in every plugin you would like to mess up with the player speed instead of using one simple native to do so ?

@Weapon Models

The weapon and view model change will be set when you switch weapon, but it would be more useful if you would have a native to do so and to reset it, first you don't have to hook ham manually, and second you will not need to add natives for every weapon to avoid bugs such as using two skins for the same weapon and having both skins being set at the same time etc

@PartialCloning, I know how they work, but it would be better to have a native to do this automatically, instead of doing it manually, then add natives for every weapon to avoid the situation above

Re: [REQ] Amxmodx 1.8.3 natives
 

"Not have to hook ham manually", especially for something so simple, is not a nearly good reason to create these new natives.

Then use them.

Re: [REQ] Amxmodx 1.8.3 natives
 

Why invent the car when we have horses?

Bumped