Missing plugin name prefixSolved

For some odd reason after unloading and loading the project and changing a default message i get this error.

Worked fine before.. I changed the message back to the old one but this error is keep happening.

 private static Dictionary<string, object> _PermissionDic()
        {
            var x = new Dictionary<string, object>
            {
                {"npcpoints.default", 20.0},
                {"npcpoints.vip", 50.0}
            };
            return x;
        }

private Dictionary<string, object> permissionList;



 private void LoadVariables()
        {
            permissionList = (Dictionary<string, object>)GetConfig("Permission", "Permission List", _PermissionDic());
        }

 private void OnServerInitialized()
        {    
            foreach (var entry in permissionList)
                permission.RegisterPermission(entry.Key, this); 
        }
(02:35:39) | Missing plugin name prefix 'pointsystem.' for permission 'npcpoints.default' (by plugin 'Test Plugin')
(02:35:39) | Missing plugin name prefix 'pointsystem.' for permission 'npcpoints.vip' (by plugin 'Test Plugin')
try this
                {"pointsystem.npcpoints.default", 20.0},
                {"pointsystem.npcpoints.vip", 50.0}​

if i look in other plugins u need now use as prefix the pluginame for example: pluginname.permissionname

but i am new to this all c# so just a idea :)

In response to dIMjIM ():
try this
{"pointsystem.npcpoints.default", 20.0}, {"pointsyste...
I dont fucking know why it now needs the class name before the permission but it worked thanks.
In response to TheReaper ():
I dont fucking know why it now needs the class name before the permission but it worked thanks.
They aren’t required, it is just a warning that has been there for the past couple years. Namespaces permissions will eventually be required though.

The warning is based on the class name of your plugin, so if your permissions do not have that then the warning will show.

Right: pointsystem.default
Wrong: npcpoints.default

To me, it sounds and looks like you renamed the plugin from NPCPoints, which is why you didn’t see the warning before.
In response to Wulf ():
They aren’t required, it is just a warning that has been there for the past couple years. Namespaces...
Its true i did rename the project but it didnt was named npcpoints etc. 
And it cant be only a warning because the perms dont work if not changed.
In response to TheReaper ():
Its true i did rename the project but it didnt was named npcpoints etc. 
And it cant be only a...
It is only a warning, I'm the one who added the warning for it years ago. ;)

There's literally nothing stopping a permission from working as long as you are registering it and properly using it.

https://github.com/theumod/uMod/blob/oxide/src/Libraries/Permission.cs#L246

Explaination of the linked code:

  1. Permission is registered
  2. Checks for permission name AFTER permission is already registered
  3. If permission name doesn't match class name, a warning is logged
Locked automatically