[Isobold]

Sorry, probably its my fault, but I can not definitifly restrict a weapon. I activated weaponrestriction an it works fine till the end of a map.

But on the next map I have to restrict the weapon again. What I would like to do is to restrict a weapon till the end of the days, even after a serverrestart the weapon should be restricted. I already tried to type save settings, but it only works till the end of the map.

Can I do this directly with amx mod x or do I need a seperate plugin?

[[nFb]GraveKeeper]

It works for me. Make sure you hit save. Of course you could just put a command line to restrict the weapon at the bottom of your server.cfg

Example:

amx_restrict on rifle

Or you can put any gun like

amx_restrict on awp

[DoubleTap]

amx_restrict on shotgun
amx_restrict on rifle
amx_restrict on sub
amx_restrict on scout
amx_restrict on g3sg1
amx_restrict on sg550
amx_restrict on m249
amx_restrict on flash
amx_restrict on hegren
amx_restrict on sgren
amx_restrict on defuser
amx_restrict on nvgs
amx_restrict on shield

[Isobold]

That is exactly what I was searching for, thx very much ;)


(This solution should absolutly become part of the amx mod x documentation/how to...)

[[nFb]GraveKeeper]

We are glad to help.

Did you put the command in your server config to make it work?

[Isobold]

yes, I put it directly into the server.cfg ;)
I didn't tried it out yet, cause I had much to do, but if it don't work, I'll be back ;)


The solution works fine ;)
Thx again

[Isobold]

it worked fine on one serverrestart, after a second it do not work again

edit:
I found out why. On each mapchange, metamod reloads a part of amxx, so it also overwrites the weaponrestriction.
I have now written into the amxx.cfg and into the server.cfg
This version really works ;)
If amxx overwrites the server.cfg, it makes the same things, and if one day I get amxx to work 100% fine, that its not reloaded on each round by metamod, the server.cfg will do the job.

(I also know why amxx is reloaded each round (or at least a part of it). The user who starts the server can not write in the serverdirectory or create a file, thats probably why amxx "forgets" all the settings on each mapchange. Probably thats also why I can't teleport ;) )




I know, it's the wrong place, but can someone give me a hint, why the user can not write into a directory in his own homedirectory.
This directory came from root (I copied hlds as root into the homedirectory of the user), but as root I already made a chmod 755 on hlds. Never the less, the user can not write anything in this hlds-directory. When I type ls -al the rights are -rwxr-xr-x .

Please, help (did I mentioned that its an unix-server ;) )...

[Knuckle$]

To ban shield for example, go into console and type:

amx_restrict on shield
amx_restrict save

This will create a file named weaprest.ini and it will stay banned. Make sure you have your "restmenu.amx" enabled in your plugins.ini

[Isobold]

This file is not created, because of my rightsmanagment-problem ;)

[dragonchaos]

Originally Posted by Isobold I know, it's the wrong place, but can someone give me a hint, why the user can not write into a directory in his own homedirectory. This directory came from root (I copied hlds as root into the homedirectory of the user), but as root I already made a chmod 755 on hlds. Never the less, the user can not write anything in this hlds-directory. When I type ls -al the rights are -rwxr-xr-x . Please, help (did I mentioned that its an unix-server ;) )...

Use "chown <username> <file|folder|*>" add -R to make it recursive

of course ... you could do "chown --help" to actually read about it

Make sure you are root when you do this ... I think the user would not have rights to change ownership