WorldeditCUI is not working with LilyPad

Mumfrey's WorldeditCUI does not work beyond server spawn world. Tested selection in main spawn world and is working. After jumps to other server worlds WorldeditCUI no longer shows selection. Anyone that is using WorldeditCUI is welcome to visit our server at mc.pwegoable.com and help as to why LilyPad is not allowing WorldeditCUI selection. if someone knows of a fix please post it

Thanks

http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/1292886-worldeditcui

If I am not familiar with WorldEditCUI, though from a quick glance I don't see why it wouldn't work. Though if you have world edit installed on your server it should be fine.

Though this is an issue with WorldEditCUI not LilyPad. You would need to post on the Minecraft Forums under the WorldEditCUI thread.

There has been some long discussions about why its not working . Mumfrey ( liteloader ,WorldEditCUI WEWrapper Voxel ETC... ) , the creator of the plugin , is a grade A++ programer. He is saying that LilyPads rproxy is broken and not passing data . Best thing is come on our server with the mod installed even without perms try it in plotworld . selection will not work after the jump to other worlds. Other people are starting to have these problems now that multi servers are becoming popular and WorldeditCUI becoming important in preventing WE mistakes

Could you give me the link to where he is talking about this? I will go hop in the conversation and give my two cents.

Here is the link. maybe you and Mumfrey can work this out, The same problem existed with Bungee and were fixed.

http://www.minecraftforum.net/forum...necraft-mods/1292886-worldeditcui?comment=322

The problem stems from the difference in plugin channel handling between lilypad and bungeecord - bungee takes the approach that the plugin channels should be synchronised between servers, so caches (up to 128) register messages and resends them when a player is switched to another server; lilypad has no such handling.

The fix in spigot resources just calls the /we cui command on player login to nudge worldedit into sending the selection; this functionality has since been baked into the client side mod.

As for supporting lilypad, the proxy already has some minimal handling of plugin messages to drop those targeted at lilypad, and as such detecting register plugin messages should not be too great a trial.

Looks like Flamin_scotsman has fixed the issue and is testing the new code fixes.