We love the new update with using more than one entrance and one exit. But we are having problems adding more entrances, it's saying it was added but is throwing a error in rcon and not creating it

Failed to call hook 'PortalCommand' on plugin 'Portals v3.0.0' (NullReferenceException: Object reference not set to an instance of an object)
  at Oxide.Plugins.Portals+PortalPointBehaviour.Destroy () [0x0001d] in <877eacd0938c43f7a74e8ef45b13e193>:0 
  at Oxide.Plugins.Portals+Portal.Destroy () [0x0002a] in <877eacd0938c43f7a74e8ef45b13e193>:0 
  at Oxide.Plugins.Portals+Portal.Spawn () [0x00000] in <877eacd0938c43f7a74e8ef45b13e193>:0 
  at Oxide.Plugins.Portals.PortalCommand (BasePlayer player, System.String cmd, System.String[] args) [0x003aa] in <877eacd0938c43f7a74e8ef45b13e193>:0 
  at Oxide.Plugins.Portals.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x000dd] in <877eacd0938c43f7a74e8ef45b13e193>:0 
  at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <3e46d2a997e94a3cb08cf065508cd483>:0 
  at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <1fe782f4b27a43ae85d29ebb2d56c007>:0 
  at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <1fe782f4b27a43ae85d29ebb2d56c007>:0

Thank you for reporting that. I'll look into that.

ok so i think i narrowed what the problem was. It seems its attached to the remove command. so these problems merged into one. So I cant remove the portals visually with the regular remove. when you add the args for the name it breaks. but even if you remove visually it never fully removes the portal out of config. the code is still there for it and I guess when you go to add to it again it breaks cause there's nothing there to add on too

,
    {
      "Name": "namess",
      "IsOneWay": true,
      "RequiresIndiviualPermission": false,
      "TeleportationTime": 0,
      "Entrances": [],
      "Exits": []
    }​

This should be fixed with version 3.1.0.