[ DEVELOPMENT PLUGINS ] Two plugins I am working on...
Hello all! Let me introduce myself. Shane, aka ^BuGs^, am a coder and gamer. So I felt that since I like Sourcemod so much I am working on two scripts for Sourcemod and hopefully they will be out and working by the time Sourcemod is released for general use. The two scripts are “Restrict Items” and “Ratio Item Restrict”.
Restrict Items “Restrict Items” is a new version of the Restrict script by Lduke were you have many more setting though. The way I am designing this script very complex so let me talk about it more in depth before questions are asked. This script will – by name – will be able to restrict items based on the server settings. However, it will not only be global, but also team based, map based (which has 2 more sub-levels to it), and player.
The script will have these option I am not going in depth:
Ratio Item Restrict “Ratio Item Restrict” is based off an idea that the EAST COAST GUARDINGS rule have of a “3:1” kill/death ratio and then you drop to pistols only. However, this script will do this automatically figure out of the user reaches that ratio based on their frags/deaths with a minimum frags settings. There are two basic settings – global and per “item”. Sample KeyValues Settings: Code:
"RatioLimit_Items" This script uses the bases off my other script -- “Restrict Item”. This script will not override settings set forth by the “Restrict Item” script. If you already have “awp” under “Restrict Item” settings for anything -- global/team/map/player -- and it's active -– this script will not even phrase the “awp” settings even if they exist to be allowed to use. It will not unrestrict an item just because you fell under the ratio. So that's about it. A few features not getting into depth about:
“Ratio Item Limit” is almost done... however it has lots of bugs a needs the restrict item script to work. The “Restrict Item” script is still in the first phases as there are just so many options to check and code. So that's about it. Both scripts will be first in “alpha” status – and it will be released to people who apply and/or help be debug and/or fix the script. “Beta” status will be released to the public for further refinement and same with “Release Candidates”. That's about it! Hope I was clear! Any questions/idea/help? |
Re: [ DEVELOPMENT PLUGINS ] Two plugins I am working on...
- Would be handy to be able to restrict XX amount of weapons per team, lets say allowe 1 AWP per team.
- Also dont forget to implement a (default HL2) sound when people try to buy a restricted weapon. |
Update in status...
Update!
I spent most of the day re-writing the entire Restrict Script and with some help from the Dev team and a good night's sleep, it now can restrict items based on "global", "team", "map (global)", and "player (global)". A sound plays now when you can not buy the function. I forgot to mention that if the CT for instance can not ever buy/use ak47 and you were on the CT team, you could not pickup the ak47, but a T could. Right now the hieharchy of checking is global, team, map, map (team), map (player), player. If anyone has any other order, let me know. There is no functionality right now in setting or using server commands yet. Right now if you installed this script, you have to edit the "data" files manually. |
Re: [ DEVELOPMENT PLUGINS ] Two plugins I am working on...
make the "1 team can't pick up other teams weapons" an optional feature, because it's a key part of the game.
|
Re: [ DEVELOPMENT PLUGINS ] Two plugins I am working on...
Quote:
|
Re: [ DEVELOPMENT PLUGINS ] Two plugins I am working on...
Update per say...
Restrict script is completed in it's most basic form. You have to edit the "restriction" files manually: there is no in-game GUI menu and no in-game commands. Two options are taken out right now as we been trying to develop a solution: map (team) and map (player). Both need a little more work in trying to "read sub-sub-keys" of KeyVaules files. I will let you know how this is progressing. Now, for testing, I am willing to release it on a limited bases right now. So contact me if you want to test it on your Sourcemod server. You need the latest compile of Sourcemod and 1.4.1 SourceMM. |
Re: [ DEVELOPMENT PLUGINS ] Two plugins I am working on...
I have to kno....why do per-map?
Because you can by default disable all restrictions then load up the restrictions on map change from a file. Since maps are able to have per-map configs (in most plugins) you can generally assign restrictions via a cfg file per-that map. You shouldn't have to do a "per-map" set up in the plugin as that honestly wastes memory IMO. |
All times are GMT -4. The time now is 18:42. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.