Bukkit

Today i would like to introduce you the newly added command completer. Im not using brigadier for this because i already have a custom command manager.

The animation shows the completer in action. If you hit a completable argument and you want to know its name just hit the # key and completer will be skipped.

The completer also supports double quoted strings to make it possible to complete arguments separated by space. This is something that gave me haedaches over the past couple of days since im not using brigadier and client doesnt know which part it completes when hitting space.. but i managed to find a solution and it is backwards compatible. Would even work in 1.12.2

In any case have fun watching the animation and leave a comment if you like.

In reply to arrbos:

 Hi arrbos, I'm on vacation til Wednesday. When I made all commands working again I will check if I can buil beta. 

In reply to arrbos:

 well you can do that with NoPerms Plugin Backend. Its not a plugin just a name for it. Used it for testing since i was thinking adding perms is an easy task once you know all your command nodes.

Status update: I could not resist to replace the current command handler since it was always eating my free time when extending it. It was also ugly to look at ;) So i replaced it over the weekend.

The command hierarchy is now much cleaner and i will also see if i can do some autocomplete magic on tabComplete when matching syntax (this was not possible with the old handler cause of old structure). Will see. Hint: I adapted the Command Handler from PermissionsEx since i feel really comfortable using it in front as in backend.

With this change i also cleaned up permissions and we have more options now :D

Since simple perms is almost never used and was disabled cause of issues in the past versions this was a necessary step. Let me know if you need the integrated perm system .. I currently dont see the need since everyone is probably using some sort of permission plugin anyways.

As for permissions and how to use -> I will create a documentation for you before releasing the plugin so you are not lost when you startup and all your known commands are gone.

( Yes your gates will still work i didnt change the database ;) )

Short commands like wxdial wxremove will probably move to "/wxt gate <gate> remove" it should take much more time to type this especially if you can tabComplete.

Let me know if i should add /wxt dial <gate> too instead of using /wxt gate <gate> dial which would be more logical for me but maybe not for you. I can always add additional alias.

And as for the Version i am currently testing on 1.12.2 and move from there to 1.13.2 and then to 1.14.2

Current issue i have found is that water sometimes gets glitchy at least it happened to me once in 1.12.2 so i might to switch to non deprecated methods. This would be one of the steps i have to take before releasing.

Todo:

* Integrate LuckPerms (should be easy)

* Test 1.12.2, 1.13.2, 1.14.2

* Finalize Commands and Permissions

* Create Mini-Dokumentation to get you started

* IF water is still glitchy i need to move to non-deprecated api when checking blocks.

* Check if uuid usage affects owner system and database persistence

In reply to HomeWorlds1:

 I use my bitbucket for source. Its public btw .. but i will sync it from time to time to github as well. Mostl likely when i push releases.

After days of hard work tabcomplete now works well. I can register them now like i do with the command backend and im really happy with the result since it doesnt use much code.

For Values enclosed in double quotes with spaces in it there is a client problem i cannot fix without a workaround. Seems that tabcomplete on client uses spaces to split words...

Arguments are positional so ... when typing 'gate "Gate Stronghold"' and autocomplete right a way there is no problem but as soon as you delete the last double quote it will autocomplete the next positional syntax ... either i find a way to better parse it or implement a workaround to glue them together.

Will see what i come up with.

In reply to HomeWorlds1:

 Im reintegrating permission system atm which i had removed in previous versions since they didnt work and PermissionsEx was still a thing. Also found a bug where the detection would always choose last registered SupportPlugin which is kinda not what it should do ;) Anyways im still working on this plugin whenever i have time.

In reply to King_MudkipIII:

Yes.

Short update: Gates work with 1.8.8. There are some minor display bugs on the client regarding the "woosh" effect of the gate but i will check if latest bukkit version fixes this.

Im planning to add LuckPerms instead of Pex since the latter isn't actively maintained any longer for ages. So in the meantime reply to this post and tell me what you think about that.

In reply to Forge_User_24996800:

 Pex 1.13.2 with which server version? CB or Spigot?

Thing is i temporarily had to drop support class so i can move on. Or else i need to use some other method to attach to permission plugins other that adding dependency...