Raised This Month: $51 Target: $400
 12% 

need help with restricting!


Post New Thread Reply   
 
Thread Tools Display Modes
Author Message
fishboy777
Member
Join Date: Apr 2007
Old 07-29-2013 , 02:02   need help with restricting!
Reply With Quote #1

Hello, I got "awp_punish" for my server so i can restrict the awp but also wanted to restrict the auto snipers as well but i don't have a clue on how and i tryed asking on the plugin post its self but no one has answered..

I had a friend on steam try to help me with this but we only got it to work when i typed "sm_rcon awp_punish_weps abce" in console.. So not only the awp will be restricted but all the auto snipers will be too. It works BUT I don't want to type it in each time the round changed.. I want to keep it perm restricted even when i'm not online and the round changes..

So we tryed these steps to keep them restricted for all times when the map changed.. First step we tryed was going into my /css/cstrike/cfg/sourcemod then clicking on "sourcemod.cfg" inside he had me put "awp_punish_weps abce" on the very bottom of everything to see if that works.. It does NOT work and everyone is allowed to use the auto's snipers but not the awp. Here is the code so you can check it out and see if we did anything wrong.

Code:
// SourceMod Configuration File
// This file is automatically executed by SourceMod every mapchange.


// Specifies how admin activity should be relayed to users.  Add up the values
// below to get the functionality you want.
// 1: Show admin activity to non-admins anonymously.
// 2: If 1 is specified, admin names will be shown.
// 4: Show admin activity to admins anonymously.
// 8: If 4 is specified, admin names will be shown.
// 16: Always show admin names to root users.
// --
// Default: 13 (1+4+8)
sm_show_activity 13

// Specifies whether menu sounds are enabled for menus created by SourceMod.
// Menu sounds can be further configured in addons/sourcemod/configs/core.cfg.
// --
// Default: 1
sm_menu_sounds 1

// Specifies how long of a delay, in seconds, should be used in between votes 
// that are "public" or can be spammed.  Whether or not this delay is obeyed 
// is dependent on the menu/command.
// --
// Default: 30
sm_vote_delay 30

// Default datetime formatting rules when displaying to clients.
// For full options, see: http://www.opengroup.org/onlinepubs/007908799/xsh/strftime.html
// --
// Default: %m/%d/%Y - %H:%M:%S
// 12 hour format: %m/%d/%Y - %I:%M:%S %p
sm_datetime_format "%m/%d/%Y - %H:%M:%S"

// Sets how SourceMod should check immunity levels when administrators target 
// each other.
// 0: Ignore immunity levels (except for specific group immunities).
// 1: Protect from admins of lower access only.
// 2: Protect from admins of equal to or lower access.
// 3: Same as 2, except admins with no immunity can affect each other.
// --
// Default: 1
sm_immunity_mode 1

// Sets how many seconds SourceMod should adjust time values for incorrect 
// server clocks.  This can be positive or negative and will affect every 
// system time in SourceMod, including logging stamps.
// --
// Default: 0
sm_time_adjustment 0

// Specifies the amount of time that is allowed between chat messages.  This
// includes the say and say_team commands.  If a client sends a message faster
// than this time, they receive a flood token.  When the client has accumulated
// 3 or more tokens, a warning message is shown instead of the chat message.
// --
// Requires: antiflood.smx
// Default: 0.75
sm_flood_time 0.75

// Specifies how the reserved slots plugin operates. Valid values are:
// 0 : Public slots are used in preference to reserved slots. Reserved slots are freed before public slots.
// 1 : If someone with reserve access joins into a reserved slot, the player with the highest latency and 
// no reserved slot access (spectator players are selected first) is kicked to make room. Thus, the reserved
// slots always remains free. The only situation where the reserved slot(s) can become properly occupied is 
// if the server is full with reserve slot access clients.
// --
// Requires: reservedslots.smx
// Default: 0
sm_reserve_type 0

// Specifies the number of reserved player slots.  Users with the reservation
// admin flag set will be able to join the server when there are no public slots
// remaining. If someone does not have this flag, they will be kicked.
// (Public slots are defined as: maxplayers - number of reserved slots)
// --
// Requires: reservedslots.smx
// Default: 0
sm_reserved_slots 0

// Specifies whether or not reserved slots will be hidden (subtracted from max
// slot count). Valid values are 0 (Visible) or 1 (Hidden).
// --
// Requires: reservedslots.smx
// Default: 0
sm_hide_slots 0

// Specifies whether or not non-admins can send messages to admins using
// say_team @<message>. Valid values are 0 (Disabled) or 1 (Enabled)
// --
// Requires: basechat.smx
// Default: 1
sm_chat_mode 1

// Specifies whether or not "timeleft" will automaticly be triggered every
// x seconds. Valid values are 0 (Disabled) to 1800 seconds.
// --
// Requires: basetriggers.smx
// Default: 0
sm_timeleft_interval 0

// Specifies whether or not chat triggers are broadcast to the server or just
// the player who requested the info trigger. Valid values are 0 (Disabled) or
// 1 (Enabled)
// --
// Requires: basetriggers.smx
// Default: 1
sm_trigger_show 1

// Specifies whether or not to display vote progress to clients in the
// "hint" box (near the bottom of the screen in most games).
// Valid values are 0 (Disabled) or 1 (Enabled).
// --
// Default: 0
sm_vote_progress_hintbox 0

// Specifies whether or not to display vote progress to clients in the
// chat area. Valid values are 0 (Disabled) or 1 (Enabled).
// --
// Default: 0
sm_vote_progress_chat 0

// Specifies whether or not to display vote progress in the server console.
// Valid values are 0 (Disabled) or 1 (Enabled).
// --
// Default: 0
sm_vote_progress_console 0

// Specifies whether or not to display vote progress to clients in the
// client console. Valid values are 0 (Disabled) or 1 (Enabled).
// --
// Default: 0
sm_vote_progress_client_console 0

awp_punish_weps abce
Now since that didn't work at all.. He had me go log into the server host from "gameservers" then click on "config" then click on "Advanced Editor"which opens up "Main Server Configuration (/cfg/server.cfg)" and had me put "awp_punish_weps abce" on the very bottom of everything to see if it works.. So here is the code on what he had me do and maybe its wrong or maybe its not.. Let me know..

Code:
hostname
rcon_password 
exec banned_user.cfg
exec banned_ip.cfg
mp_logdetail 0
mp_logmessages 0
mp_timelimit 0
mp_autokick 0
mp_autoteambalance 0
mp_c4timer 30
mp_flashlight 1
mp_footsteps 1
mp_forcechasecam 0
mp_forcecamera 0
mp_allowspectators 1
mp_freezetime 0
mp_friendlyfire 0
mp_hostagepenalty 4
mp_limitteams 1
mp_roundtime 3
mp_tkpunish 0
sv_restartround 1
sv_maxspeed 320
sv_proxies 1
allow_spectators 9999999
mp_startmoney 16000
mp_chattime 5
sv_allowupload 1
sv_voiceenable 1
sv_alltalk 1
sv_voicequality 5
sv_voicecodec vaudio_speex
pausable 0
decalfrequency 40
mp_falldamage 0
sv_aim 0


//Enabling sv_cheats will allow anyone to execute rcon commands and add/remove admins
sv_cheats 0

sv_maxrate 30000
sv_minrate 0
sv_lan 0
sv_contact
sv_region 0
sv_maxupdaterate 120
sv_minupdaterate 20
sv_unlag 1
sv_maxunlag .5
host_framerate 0
awp_punish_weps abce
So there you have it.. Our 3 steps that we took and only 1 of them worked which was typing in "sm_rcon awp_punish_weps abce" but I don't feel like typing it each time the map changes.. So if you can help me that would be really really great and awesome!
fishboy777 is offline
TnTSCS
AlliedModders Donor
Join Date: Oct 2010
Location: Undisclosed...
Old 07-29-2013 , 09:18   Re: need help with restricting!
Reply With Quote #2

Weapon Restrict seems like the better choice for you to use. It allows you to restrict the AWP and both Auto-Snipers (T and CT have different ones) at all times. Then, if you have a map where you don't want those weapons restricted (for whatever reason), you can use map specific configs to change the restrictions.
__________________
View my Plugins | Donate
TnTSCS is offline
fishboy777
Member
Join Date: Apr 2007
Old 07-29-2013 , 15:18   Re: need help with restricting!
Reply With Quote #3

Quote:
Originally Posted by TnTSCS View Post
Weapon Restrict seems like the better choice for you to use. It allows you to restrict the AWP and both Auto-Snipers (T and CT have different ones) at all times. Then, if you have a map where you don't want those weapons restricted (for whatever reason), you can use map specific configs to change the restrictions.
Will the weapon restrict keep both snipers restricted with a setting or will I have to type it in each time?
fishboy777 is offline
TnTSCS
AlliedModders Donor
Join Date: Oct 2010
Location: Undisclosed...
Old 07-29-2013 , 17:12   Re: need help with restricting!
Reply With Quote #4

You can setup everything in the config file and it will remain as you set it.
__________________
View my Plugins | Donate
TnTSCS is offline
fishboy777
Member
Join Date: Apr 2007
Old 07-30-2013 , 01:14   Re: need help with restricting!
Reply With Quote #5

Quote:
Originally Posted by TnTSCS View Post
You can setup everything in the config file and it will remain as you set it.
Yeah, I installed it on my server and it works really amazing and I Love it.. Thanks for the help TnTSCS... The plugin is AWESOME!
fishboy777 is offline
jamesfrankodwg
New Member
Join Date: Aug 2013
Old 08-01-2013 , 06:51   Re: need help with restricting!
Reply With Quote #6

this works perfectly fine.
____________________
Repossessed cars | Honda for sale
Salvage Exotic Cars | Canada Migration

Last edited by jamesfrankodwg; 08-01-2013 at 06:51.
jamesfrankodwg is offline
Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 05:28.


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