Bukkit

-What steps will reproduce the problem?
It seems MessagechangeLite can't find the permission nodes on CB 1.0.1-R1 or I must have changed something in the permissions since the update. I tried with a fresh config and only used the two original nodes from that config, still I got the same problem; No matter what group I choose the joining/leaving message becomes the "default" from the plugin.

-What is the expected output? What do you see instead?
Well I would hope the nodes woked

-What version of the product are you using?
2.0

-Do you have an error log of what happened?
No, but here is the debuglog when I:
Start the server: http://pastie.org/3018267
Join: http://pastie.org/3018295
Leave: http://pastie.org/3018298

Here is my permissions: http://pastie.org/3018309
Here is the MessageChangerLite config: http://pastie.org/3018318

-Please provide any additional information below.
I think this should provide enough info, sorry if this made it harder for you to see the bugs, but I figured it would take less space.

thanks. for ALL that information, really.. this makes it a lot EASIER :-)

No joke.. would like all tickets would be like that..

there is one problem with the pastie permissions file at line 270, could you check that in the original one?

BTW: you don't need to use permnode2 etc as name you can call it whatever you like.

Also you can enable debugging of pex with /pex debug enable (?) irrc...

I will take a look at it probably this evening, just pushed everything up to 1.0.

BTW: which version of pex are you using? I'm relying on superperms..

@DonRedhorse: Go

Yea I saw that on pastie, but I couldn't figure the flaw, whatever I pasted after after the veteran group became like that. Please don't stress by doing something yet, I must have done something wrong in the PEX. My original permissions had the same. The YAML parser find no mistake though.

Yea I know I can change that, it is just that I thought numbers would be fine even though I see how much easier it could be with names now...

I use the newest version of PEX, version 1.17

well enable debug for pex... I use the superperms, so nothing specific.

The only problem could be if your group inherit from each other, but that doesn't look like it.

The only issue I produce is that I walk the permission nodes alphabetically, but RandomPlayer is only in group Mod only, but the pastie is broken there..

it is the additional ' after the null in line 270 in pastie... that makes the rest not working..

@DonRedhorse: Go

I fixed the ' after null, fixed the permissions, but the main problem is still there.

Here is everything once more with original config and fixed PEX:

Permissions: http://pastie.org/3022947

MessageChangerLite config: http://pastie.org/3022957

Debug MCL and Permissions join: http://pastie.org/3022977

Debug MCL and Permissions leave: http://pastie.org/3023012 (note this is a guest group who should have custom message 4 - messagechanger.message.permnode4)

These are directly copied from config and cmd, no edit at all, no idea why the joining pastie turned yellow..

hmm... you don't have the permission inside the specific world, only in the global one..

could that be the issue?

I will look at the code and will try to make a change in the parsing so that it will go to default at the end..

now it falls back to me that I didn't really want to implement permissions..

@DonRedhorse: Go

I think that is it, I am so sorry to trouble you so much. I don't think you need to do all that extra, if you just say it needs to be put in the world node as you have, it should be fine ^^

I am very happy with the work though, there is no other plugin that can do this correctly. Also please note that I talk for my community of 23 members and far more guests! We are very grateful to all the plugin developers who listen to us users :)

Also, sorry to respond so late, I have been very busy with school and some larger community projects.

so is that figured out? sorry to come back more than a month later..

Yes, all I needed to do was to put the node in all the world nodes

Btw, I have some new suggestions for messages if you would like to add them :)
Would it be possible to change the message that comes up when you type in commands that doesn't exist? (The default message is
"Unknown command. Type "help" for help.") Maybe make the messages for /save-all customizable as well?

sorry didn't see this..

Unknown Command is very good for Unknown Commands... I have a list with funny quotes if you want some.

Otherwise save-all will probably not work

@DonRedhorse: Go

Sure, would be awesome if you could make "unknown command"-message customizable.

What I meant by /save-all was the messages coming up after you have typed the command, you see them as grey in the chat: "CONSOLE: Forcing save.." "CONSOLE: Save complete." There are also messages like: "CONSOLE: Disabling level saving.." and "CONSOLE: Enabling level saving..", for some other commands. But I don't mind if you can't do that, isn't really necessary :)

@IronPixel: Go

Well unknown command should be still around, if not I will probably update it because I need it myself. I have to much fun reading the lines it displayes when somebody uses a command which doesn't exist.

Concerning the save-all, I don't think that there is an event for that, but I can take a look, but iirc those messages are just on the console or not?

@DonRedhorse: Go

No, the console commands gives a message in dark grey (&8). All of them, save-all, disabling saving and enabling. To be honest I just want to remove them, but it might be useful to customize them in the future for use on a backup/save plugin.

@IronPixel: Go

ah... well I will keep that in mind when I need to dive into the code again..