themaster1970sf/TShock
1
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions

Change Utils.Reload to not take a player.

Browse source 
There are two occasions in the codebase when Utils.Reload is called and
we're competent enough that we can just call the event when the reload
happens. Unrelated note, but shouldn't this event be called prior to
reloading? I've kept it the same to preserve existing behavior, but I
think it should probably happen before the reload event takes place.

Either way, I think this is fine.
This commit is contained in:
Lucas Nicodemus 2017-12-29 08:04:20 -07:00
parent 152c67f27c
commit afdedee1c4
3 changed files with 5 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

3
TShockAPI/Utils.cs
View file

@ -495,7 +495,7 @@ namespace TShockAPI
/// <summary>
/// Reloads all configuration settings, groups, regions and raises the reload event.
/// </summary>
public void Reload(TSPlayer player)
public void Reload()
{
FileTools.SetupConfig();
TShock.HandleCommandLinePostConfigLoad(Environment.GetCommandLineArgs());
@ -504,7 +504,6 @@ namespace TShockAPI
TShock.Itembans.UpdateItemBans();
TShock.ProjectileBans.UpdateBans();
TShock.TileBans.UpdateBans();
Hooks.GeneralHooks.OnReloadEvent(player);
}
/// <summary>HasBanExpired - Returns whether or not a ban has expired or not.</summary>