Security:MaxShipTypeSwitchCount

[TerminatioN]

Security:MaxShipTypeSwitchCount is currently set at 20, and yet it allows what appears to be an unlimited number of ship changes to anyone (might not be unlimited but I gave up around 130).

 

I've tested it myself under an aliased, non sysop name, had a normal player test it, had several others test it, changed it to other numbers, recycled the zone, etc.

 

Pretty much tried everything I can think of and still its as if the setting is totally ignored.

 

I know its not the Security:SecurityKickOff setting as that is currently set at 1 and if Security:MaxDeathWithoutFiring is exceeded then you're kicked off and it says in the log thats the reason why.

 

I'm really stumped here. Please help.

Thanks,

-TerminatioN

Edited April 27, 2009 by TerminatioN

[Jericho24.]

check server.ini

 

ShipTypeSwitchResetPeriod=

 

//If non-0, than if someone does X amount of shipchanges that is in the .cfg in this amount of time (in milliseconds), then kicks them off

[Samapico]

Staff members (mod+) are also not affected by this setting and will never get kicked.

[TerminatioN]

check server.ini

 

ShipTypeSwitchResetPeriod=

 

//If non-0, than if someone does X amount of shipchanges that is in the .cfg in this amount of time (in milliseconds), then kicks them off

Yep, thanks that was it!

 

Guess you must have gotten some inspiration since the other night. This is the same problem I was talking about.

 

 

Staff members (mod+) are also not affected by this setting and will never get kicked.

Yeah I know, if you read I accounted for that.

 

Thanks anyways! This is resolved!

[Chambahs]

"I've tested it myself under an aliased, non sysop name, had a normal player test it, had several others test it, changed it to other numbers, recycled the zone, etc."

 

I think he knew that

 

EDIT: damn, too slow.

Edited April 27, 2009 by Chambahs

[Samapico]

Yeah... it just sounded as trying a non-staff name was "one of the things" he tried, which is why I told him specifically that it would never work with a staff member.

 

Anyway, closed