Move Utils.Ban -> TSPlayer.Ban.
Arguably, this is one of the more controversial methods that's being kept. Because it kicks and bans a target player, it's more useful than removing it and requiring people to interface with the TShock Ban Manager directly (not a good move for the future). Whether or not this method sucks is up for debate, but right now I think it's totally fine to keep it around in a different location.
This commit is contained in:
parent
a5a3aae599
commit
152c67f27c
4 changed files with 30 additions and 31 deletions
|
|
@ -71,7 +71,8 @@ This is the rolling changelog for TShock for Terraria. Use past tense when addin
|
|||
* Removed `Utils.ActivePlayers()` -- use `TShock.Players.Length` instead. (@hakusaro)
|
||||
* Moved `Utils.Kick()` to `TSPlayer` since its first argument was a `TSPlayer` object. (@hakusaro)
|
||||
* Removed `Utils.ForceKick()`. (@hakusaro)
|
||||
* removed `Utils.GetPlayerIP()`. (@hakusaro)
|
||||
* Removed `Utils.GetPlayerIP()`. (@hakusaro)
|
||||
* Moved `Utils.Ban()` to `TSPlayer.Ban()`. (@hakusaro)
|
||||
|
||||
## TShock 4.3.25
|
||||
* Fixed a critical exploit in the Terraria protocol that could cause massive unpreventable world corruption as well as a number of other problems. Thanks to @bartico6 for reporting. Fixed by the efforts of @QuiCM, @hakusaro, and tips in the right directioon from @bartico6.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue