Idk maybe its cuss we use AdminMenu?
{
"AssetPrefab": "assets/content/vehicles/minicopter/minicopter.entity.prefab",
"CanSpawnBuildingBlocked": false,
"MaxNoMiniDistance": 300.0,
"MaxSpawnDistance": 5.0,
"PermissionCooldowns": {
"spawnmini.tier1": 86400.0,
"spawnmini.tier2": 43200.0,
"spawnmini.tier3": 60.0
},
"SpawnHealth": 750.0
}
I don't believe so by default the plugin does not auto-assign any permissions for it. I had to manually set the permission and I only changed it to 1 group which was default = all players, I can try a server reboot...
But if assigning multiple to it should cause a warning or error not default to 1 day. I have never run across a plugin that faults to default from something like that.
I can send you all 3 copies of my servers... and you will experience the same issue.
All 3 are completely different both in maps and the plugins they use
Also, many have yet to update to the latest umod update. I always update when they drop... Technically the first Umod update worked just fine on launch day so many aren't yet affected/need to update yet
Most of the people I know we're still using the older version labeled MyMiniCopter.
This last rust patch finally broke it tho. Thought about patching it but ran across your version which kinda gutted out a few things... and added some redundant stuff like default to 1 day... Many of us use VoteSkipDay which may or may not be breaking this cool down issue as well.
Since you set it to DateTime.now.AddDays I can try disabling the SkipNight plugin that's on all 3 of my servers.
https://umod.org/plugins/skip-night-ui
Yeah, so if you switch it back over to a Private Timer Clock system it appears to function fine... but if you use the game time it won't work.
You could port over that feature back from patch 0.1.9 or redo it with your own spin. I managed to port it over with just a cooldown setting and removed the 3 tier features to save some time...
But since you made it a copyrighted plugin instead of open you'd probably want to do your own Private timer spin? idk
Just some food for thought. :)
khan
I'm having an issue with the default cooldown being stuck at 1 day. Even though I set the VIP 1 2 and 3 to 60 sec and made sure the default player group had the perms even myself the admin is affected by this bug. I don't want to apply the NOCD perm if I can avoid it... @DMB7
Keep in mind that the cooldown is stored in the data file. This means if you have perm1 applied with a cooldown of 5000, use /mymini and then assign yourself the permission of perm2 with a cooldown of 1, the data file will hold the cooldown of 5000. Once that's over, you'll then have the cooldown of one from perm2.
If that is what's happening, you can go into the data file and delete the cooldowns.