@Wulf there is a problem when people renamed with the old version, then used /resetname going back to the old versions name which is different to the steam name and dont get renamed again to the new name:

Steam Name: Alfred

Renamed to: Alfonso  - before Rename update

Renamed to: Albert after Rename update

Resetname -> going to Alfonso as thats the old name that Rename got

Renamed again to Albert with Plugin

Plugin saves the old name with Alfonso on reconnect its Alfred connecting and he doesnt get renamed

Same problem is made when people got renamed from renameothers - possible fix would be to just delete the "old name" logging as its just the name at the time the player renamed - that would be also maybe a problem if people renaming their steam profile dont know, i can't understand further as the rename function is calling the player ID which is bound to the steam account not to any name - we are just having problems with people renaming / saving of renames as well actually and i have no idea why exactly

Failed to call hook 'CommandResetName' on plugin 'Rename v1.0.1' (IndexOutOfRangeException: Index was outside the bounds of the array.)
  at Oxide.Plugins.Rename.CommandResetName (Oxide.Core.Libraries.Covalence.IPlayer player, System.String command, System.String[] args) [0x00128] in <91179daa4f5a4b62b24dcba17aa2568b>:0

  at Oxide.Plugins.Rename.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x001eb] in <91179daa4f5a4b62b24dcba17aa2568b>:0

  at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <e23ba2c0f246426296d81c842cbda3af>:0

  at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <50629aa0e75d4126b345d8d9d64da28d>:0

  at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <50629aa0e75d4126b345d8d9d64da28d>:0

heres the errorlog which i´ve got after i tried to /resetname after changing to my steam name to get a new one 

Thanks for the report! I was able to reproduce both issues and both are fixed for the next update, thanks.