Ok. Yeah I’m sorry I didn’t notice I got added back to my “Owner” rank and it had exempt cooldown. It’s fixed now 
. Thanks a ton.
1 Like
Also I know this is a bit of a silly thing to request, but would it be possible to make a perm to allow players to make only a specified amount of warps like there is an option for homes? I want to add that ability to a rank. 
Warps are meant to be an administrative thing, so I’m not willing to add this to warps themseleves. If there is demand, I’ll look at adding a /pwarp system, that is, a “personal warp” that players can set a limited number of, but are accessible by all, but I don’t know how essential it is to add that and how much it would be used - adding every feature under the sun isn’t a goal here.
The backbone for such a thing does exist, so it probably wouldn’t be too hard to do.
That would work as well, I am just looking for something players can use to set warps to their shops or things like that. Or maybe you could add it in a way like a lot of the plots plugins do like: /pwarp playername warp#. This is not something that is a must have it would just be a nice little addition.
Just wanted to say you are doing an amazing job with this plugin! Players on my server love the change. Few things I noticed that I thought I would ask about.
- You already know but is there an eta on the /fly randomly not working fix?
- Private Warps for players would be nice.
- SocialSpy seems to have a randomly stop working issue also. But it is not as fast as /fly
- Vanish as staff and using /tp still reports you tp’d to a player on the map
- Also not sure if this was meant to be this way speed 1 is like crawling speed 2 is normal minecraft speed 3 is what would normally be speed 2.
Thank you. I appreciate all comments, good and bad - it’s a fun project for me and feedback helps shape it.
- So, the latest version has a speculative fix, but if it isn’t working, which I thought would be the case, I’ll need to spend a bit of time trying to work out what Pixelmon is doing, and without the source code, that’s going to be difficult. I’ll do my best though.
- It depends what you mean by a private warp really. What would you want out of such a feature, how would it work?
- SocialSpy - can you explain how? Is it with certain commands?
- Yep - I’ll fix that
/tpissue once I get a moment to do so! - So, I think I tried to make it similar to essentials, 2 should be normal speed for walking, I think. I’ll look into it again.
- Current Version /fly is not fully working. I do know the issue was not in Essentials
- Private Warps like player specific. I am working on a Pixelmon Adventure server and i want to setup a command block that gives players a /pwarp when they complete a town to get back to it. I do not want them to have all the warps on the first join… If that makes sense.
- Randomly after a reboot socialspy just stops turning back on. It was a issue with Essentials also.
- Essentials had speed 1 walk speed 2 faster. When i switch i changed my donation shop to speed 3 no big deal.
Private Warps like player specific. I am working on a Pixelmon Adventure
server and i want to setup a command block that gives players a /pwarp
when they complete a town to get back to it. I do not want them to have
all the warps on the first join… If that makes sense.
Use the plugin discoverywarps
Actually, Discovery seems like a good idea and I would really suggest looking into that.
The other way you can do it is to use perrmission based warps. If you set warp.separate-permissions to true and use /nucleus reload, each warp needs the permission nucleus.warps.<name>, so if the warp was called red, the permission needed to use the warp would be nucleus.warps.red. You can then get the command block to just give the player that permission.
1 Like
You can set per-warp permissions
1 Like
Version 0.4.4 has been released!
Yeah, I’m sorry, yet another bug fix release. Any of you who have downloaded the build from earlier today will have the bug fix, this is just the official version.
The change in this version is to prevent an exploit allowing users to redeem kits multiple times and ignore cooldowns. Updating is HIGHLY RECOMMENDED.
Ore: https://ore-staging.spongepowered.org/dualspiral/Nucleus/versions/0.4.4+b69b6ad
GitHub Releases: Release [BETA] Version 0.4.4 · NucleusPowered/Nucleus · GitHub
now my homes are broken all together; it gives me an error occured trying to perform this action when trying to set a home. but some other people are still able to sethomes. not sure why mine is broken.
just a warning… updating to 4.4 to fix the kit shit… actually breaks your kits in the process; throwing errors and letting players spam redeem them also. you’ll need to remake all your kits.
I’m not getting the kits breaking thing. no spam redeem either. this is why i dont go to new sponge forge versions so fast lol
In main.conf, set core.debug-mode to true, then see what is thrown out to the console. The more information I have, the more I can try to do to solve it.
i removed my profile cleared the cache and got my homes working; however, doing so made kits unlimited no cooldowns
apprently kits are STILL spammable… -__- but only by some people; not everyone. i don’t understand.
The only thing I can think of is permissions. Check if they have the permission: nucleus.kit.exempt.cooldown - if they do, remove it.
I can’t look into the code right now, as I’m away from my computer.
nope; no1 has an exempt cooldown for kits. i private msg a few people and they cant spam it but some others can; i’ve also noticed that upon logging in sometimes it tells me that i have multiple kit things and that it has to fix it. this happens alot, i dont know if that has something to do with it or not though.
another thing with the latest build is the teleporting; it always throws errors but does the command anyway in some cases; however it will not teleport players to you; you have to result in using /minecraft:tp tpaing works but general teleport commands, etc do not.
Oh, I think I know what’s happening with teleporting. Does it give you java.lang.NoSuchMethodError errors? If so, it’s because API 4.1 has had a breaking change, and so newer builds of Nucleus only work on new Sponge builds. While you should use the latest and greatest, I understand why you are reluctant.
I’ll try to spin up a build that will work for older Sponge versions.