Banner

Saxywolf · #1 02-21-2008

Its a linux server with Game Servers
Sourcemod shows up as loaded when I do "rcon meta list"
sm_map <mapname> works

I downloaded the Freeze Status plugin from Sourcemod

The only instructions I can find for installation is to "install as usual"

I put the freezestatus.smx file in /sourceforts/addons/sourcemod/plugins
I put the freezestatus.sp file in /sourceforts/addons/sourcemod/scripting

While facing a frozen block I type freezestatus in the console I get nothing. Not even an unknown command response. Nothing shows up in chat or the console when done with a bound key either.

The Extra Plugins section mentioned that the cfg files would automatically be generated, but I doubt there are any. It also mentioned that the plugins can be "loaded". So, I looked into the Plugin Loading and tried the following in /sourceforts/addons/sourcemod/configs/plugin_settings.cfg:

Code:

	"freezestatus"
	{
		"pause"			"no"
		"lifetime"		"global"
		
		"Options"
		{
			"debug"		"no"
		}
	}

I'm still not getting any response. Can someone tell me what to do?

SANTARII · #2 02-23-2008

restart server, if u already have, or if it still doesnt work, as far as I can tell u have done everything right, srry all the help I can give...

Saxywolf · #3 02-29-2008

follow the white rabbit

Saxywolf · #4 03-02-2008

Changes:
Shortened freeze status messages to: "Last Un/Frozen by: <Name> (<Steam ID>)"
Added language support, but still only english.
Added chat announcements when players unfreeze blocks.
Included block id in unfreeze chat announcements.
Added command "freezeannounce", for SM admins with ban ability, to manipulate announcements.
Added cvar options for announcements.
No chat announcements for freeze (freezestatus still shows who froze it last).
Added some error checking for sm_unfreeze_announce setting.

sm_unfreeze_announce 0/1/2
0: off
1: announce to all [default]
2: announce to admins only

Features I want to add:

During combat, only send messages when a player unfreezes their own team's blocks (not as a toggelable option).
Display the number of unique blocks unfrozen by a player when they unfreeze more then 1 (with a time limit?)

013109 · #5 03-02-2008

like i mentioned last night saxy, would be neat if you could just toggle this 0/1 style. And have the last person who froze/unfroze it names pop up like block health or player name. Be tons more convenient.

GenKernel · #6 03-04-2008

So I assume you got it working?

Saxywolf · #7 03-04-2008

Hi GenKernal!!!

Yup, it's working... and mostly tested.

The first major problem I ran into was the game data .txt file incorrectly referencing sourceforts mod so that the function didn't think that required function worked (geteye something). I then had trouble getting it to check the admin permission variable as the correct type using the example I found. Lastly, I had a bug in one of my debugging lines

I think I'm going to remove the freeze announce cause it's not all that useful to catch a griefer. I've been thinking about how to only announce after they unfreeze multiple blocks, but I haven't thought of a good way to do so yet.

011003,
There is no specific event for me to hook into for displaying the freezestatus when simply looking at a block when the health would display (that I know of, but I get the feeling there is something). Although I do think it's possible without such an event, I don't want to do it that way to avoid unnecessary cpu processing.

Saxywolf · #8 03-04-2008

This is what I'm proposing to make griefers as obvious as possible as soon as possible and even prevent some types of griefing all together. There is no known event triggered that I can hook into to prevent an enemy from blocking your unfreeze by beginning to unfreeze themselves. I have a pretty good idea on how I'm going to do all of it so far.

Note: They may just be de-constructing something that was built poorly, which is why there is only one instance of autokick/ban.

If they Freeze many blocks in quick succession
It must be build phase, and they are probably block spawn griefing

Give a warning to everyone else after a few blocks and
Prevent them from freezing for a specified time

If they Unfreeze an enemy block during build auto kick/ban them (all admin are immune)

greifer_kickban <0/1> // auto ban and kick the build phase griefer
greifer_ban_time <0 to 9999>// ban time to use, 0 is permanent

If they Unfreeze an enemy block during combat do nothing

If they Unfreeze their own team's block...
This is where it gets complicated...
The block count is included in the announcement if > 1
Count goes up and timer restarted if the block they unfreeze is not the same as the last
If timeout is reached, block count is set back to 0
Since pre-built bases start motionless by World by freezing them once they become owned
By grabbing a block it becomes owned

// # of seconds until their block unfreeze count is reset
announce_timeout_combat = 120
announce_timeout_build = 20

// minimum # of blocks to trigger warning
warning_blocks_combat = 2
warning_blocks_build = 3

// minimum # of blocks to trigger alert instead of a warning
alert_blocks_combat = 4
alert_blocks_build = 6

0 = scrim mode announcements
1 = public mode announcements
2 = admin mode announcements

W = Warning given to player who violates
O = message is made extra obvious by surrounding it with lines of ******* UNFREEZE ALERT *********

Any suggestions, complaints, problems you foresee?

HisChild · #9 03-05-2008

and imagine that i'm tearing down something noobish because the noob who build it left and i'm gonna do something useful with it?
Or what if i tear something down with permission?

Saxywolf · #10 03-05-2008

It will give a warning, and then an alert. Thats it. No auto-kicking.

During combat blocks frozen or unfrozen lose their team property all together. Otherwise, in the following build phase, you would get auto-kicked for removing a ramp the other team made.

Banner

Repeat

End

Forums

Tab