The Chat templates don’t seem to be working in the 1.10 version, but work fine for me in the 1.8 version, maybe this is something you can look into? I set them up the same way I did on 1.8 for 1.10, but they dont seem to work.
Thanks!
Having an issue where /seen, /homes, /listhomes and other command like that return “That player does not exist” even if the player name is tabbed in.
Issue I have noticed, If a worlds UUID Changes the player data will not update with it. I know this is a rare occasion, but it has happened with 2 of my servers so far. GriefProtection seemed to update with the World UUID change. Is it possible to add that feature here?
Is there anyway to add something so vanished players don’t have a msg broadcast on login?
Apologies for the lateness guys, personal things to attend to!
That looks like that could be a Sponge issue trying to get the user data, I don’t think Nucleus is at fault with that one.
I can’t reproduce this yet, but I have an idea what’s going on. I’ll investigate!
I’ll have to see how GP does it and mirror that I think - but yes, if it can be done, we will do it.
Makes sense, sure.
@Riddle I’ve just tried it on my 1.10 build, and chat is working fine for me. Not sure what else you might have installed, or if there is some error being thrown in the console (set core.debug-mode to true, then try chatting normally).
For those of you having trouble with commands such as /seen, /homes etc. - try the 0.7.1 RC1 build at 0.7.1 tracking. · Issue #299 · NucleusPowered/Nucleus · GitHub. This is not an official release, but I wanted to highlight it to get you guys to test it.
I cannot yet promise this will fix your issues, because I can’t reproduce it myself, but I’ll explain what I think is going on. When using a command that works with BOTH nicknames AND offline users, I’m not filtering names well enough, and it’s returning more people than it should be. Now, if we have an exact match for a name, that should take precedence.
You can also try starting a name with p: to select ONLY a player name, not a nickname.
The zip file on the issue has both 1.8 and 1.10 builds in there. Please choose the one appropriate for your system. Let me know how it goes.
Also for some reason when tempbanning a player it doesn’t kick them on the tempban, you have to kick them yourself for the ban to go through.
Fixed that now, will be in 0.7.1, thanks.
@dualspiral Is this Hotfix 1.10.2 or 1.8.9?
Is 0.7.1 out? Sorry for asking. Got quite busy irl lately so still have a lot to catch up XD
@Karagra_Gaming Both, the file contains both versions.
@SnowBlitzz No, I have a couple of other patches that will be going in there before I mark it as official. I just need this testing with the issue I can’t reproduce yet.
1 Like
How to kit an item with nbt?
Version 0.7.1 is now available
This is a hotfix release that fixes some major issues you guys have been having, including with some commands not picking up players.
For the release notes and the plugins, see Release [BETA] Version 0.7.1 (for 1.8.9 and 1.10.2) · NucleusPowered/Nucleus · GitHub
For those of you who are interested, those of you having issues with /seen, /listhomes etc. might be interested to know what happened, and why I didn’t see it. The bug was triggered whenever the user in question had a capital letter in their IGN as registered with Mojang. I was using UserStorageService#match, which is supposed to get all users starting with the supplied name.
However, it seems that the method doesn’t quite work - to do the case insensitive check, it should have lowercased both the name in the game profile and the supplied name, and it only lowercases the supplied name. Thus, it only worked if the account name was lowercase in the first place. I missed this because my IGN is lowercase - so I could not reproduce this until I managed to get a friend with a capital letter onto my test server.
So, I saw it, and it’s fixed now. Sorry for any inconvenience.
Can you open an issue on Sponge for this?
Issue of not being able to do /homeother (Playername with capital letter) is still in place.
Is the /thru permission off? I give it to my players and nothing might be a pex thing not sure but i do
/pex user name perm nucleus.thru.base true with no luck
Do /pex user (name) perm nucleus.thru.base 1 instead of true. Then make sure you do /pex reload. I suggest reading this thread for more info on pex commands
true works the same as having it 1
I was able get the colored chat to work on 1.10. Is there an easy way to port my 1.8 nucleus data like homes over to 1.10? I tried copying the world folder in nucleus but it didn’t seem to work.