Bukkit

In reply to MrSqueak:

 Im stuck at finding a good solution to import gates created before MC 1.12. since there is no magic number conversion available anymore and i really dont want to provide one (which is heck of work due to the new material implementation by MC ...) well to make it short im working on creating a new database interface to store gates differently at the moment so i can update them better later.

In reply to King_MudkipIII:

 Hello King, sadly i hadn't much time to spend due to work life balance changes. Will have some days off next week though.

So its been 5 days now. Last time i paused development for some days cause i needed to create a plan to fix numours bugs.

First off .. gate detection during build was buggy in 1.13.2 so i needed to fix that. Turns out it never really worked well. In 1.12.2 gate detection would always fall back to Standard gate shape since this was the first Shape in the array. So if you had issues when hitting a lever when obisidian was nearby then this is fixed now.

Made it possible to make gate detection visible in world i.e. by replacing blocks with colored whool blocks. Im temteped to turn this into a feature but maybe no one will ever need it so maybe i will just add this to the debug section ;)

Anyways i will disable any handlers that checked the gate or re-created one when activating the lever. Turns out this will make your server lag in some cases where the gate is either damaged or in a somewhat corrupted state i.e. missing blocks. Also, as mentioned, if gate material is found nearby detection routine would take too long to find a match especially if you have many custom gate shapes created.

I believe this is not what you would expect so i will switch to triggered gate creation.

What this means you enter /wxt gate build from shape StandardSignDial (which is tab completable if its too long for you to type) which will set build mode.

After that you can either create a gate on your or just auto-build it. Up to you. In any case the final complete command will create the gate from a shape and turn it into a stargate. So its up to you which method you want to use.

Have to move some parts around as we still want to have gate protection. Will probably add a command to validate a gate or all gates.

Last but not least .. you probably will have to re-add gates since the database contains magic values which is hard to translate in newer api versions.

But you dont have to do it the hard way. You get an import routine that can read legacy versions database file. Incompatible data will be thrown away but can be exported. If you have many gates with custom-set gate materials you will most likely need to set them again. This will be documented on my wiki in a how to.

Thinking about it i might just add a builder where you set your custom design and apply it to named gates. Will think about it.

Please reply if you have many gates with custom gate materials set i.e. light, portal or gate set to something else than default. Depending on the feedback i would try to find the best solution possible.

Thanks you for your support.

As of now the command system is now fully operational. For now simple perms is still not working as expected and thus disabled. Maybe it will find its way back if you really need this feature i.e. you dont want to use a permission plugin such as pex or luckperms.

Plugin now works for 1.12.2 servers. Will now move to the next stage and make it work for 1.13.2 which includes moving from deprecated api to new.

In reply to Forge_User_24996800:

 yes you can. I have made sure that this still works. Might have to retrigger stargate creation though. Also some new stuff i found. See latest post =)

 Short update note: Since yesturday im working on fixing commands i just moved from old to new. After that i need to handle some other things like

* Online Mode UUID Change

* Remove Material TypeID usage

Hoping to get this done this weekend. Currently developing on 1.12.2 since this is the easiest start for me. After that i will move to later versions and fix stuff from there.

In reply to Forge_User_56589807:

Merci pour ton message.

J'espère que ce texte a du sens. Je traduis le texte avec Google Translate.

C'est agréable de voir que vous aimez WormholeXTreme. J'en suis très content.

Je suis déjà très motivé mais vous pouvez toujours soutenir le projet avec le bouton Faire un don en haut à droite.

J'espère trouver un peu de temps le week-end pour créer une version bêta, puis j'espère pouvoir livrer une version pour les tests.

Peut-être que cela fonctionnera comme il se doit.

Malheureusement, je ne peux rien promettre, car lundi le travail vous impliquera à nouveau pleinement.

In reply to Reggie_AU:

 Im doing this in my free time. Checkout post #174. Its not like nothing has happend. A lot has changed since then not only do permission plugins come and go but also new version of minecraft get released and things change. This plugin is very old and sometimes it feels like it wasn't ment to be updated but i spend hours of time to make it happen even as others just said "let it die".

Imagine this: whenever i go back to programming i need to fix things i already had fixed last time and test everything again. If you remember the years after 2015 it wasn't even clear what will happen to bukkit or if we are even allowed to develop plugins after the takeover.

To answer your question: No, I will not give permission to re-release any of my plugins here on bukkit or other platforms as a "Q&D fixing" under the same name or look alike. When i get time to finish my work there will be a release. If you dont want to wait you might want to switch to another plugin.

However since its Open-Source you can look at the code create your own plugin by using your own namespace, own plugin-name and most importantly not just copy paste the code from this one and not just do a bug-fix release. To create such an acceptable plugin you would need to most likely rewrite this from scratch and come up with your own ideas.

What i would rather like to see is go to my github page, fork it and try to fix things. The version tag matches the uploaded artifact. Maybe you see things I overlooked. At the time i started planing i didnt see a way for a fix release and started working on refactoring critical parts of the plugin so it would make it easier for me to work on things whenever i get back to coding. Over the years i have come to most likely acceptable release candidate which wil find its way published when i feel comfortable since i have high standards when it comes to releasing a version.

A personal note from my side: im feeling rather offended by this question you could have asked me via PM. Open-Source doesn't mean you just take the code and fix it and claim it as your own. This is the reason why some ppl don't open source their plugins.

I have worked on this for too long in my free time to make this happen. So i will finish this. When i dont feel this drive any longer i will announce it. But knowing me this won't happen anytime soon.

If you feel the need to discuss this further please write me a PM.

Best wishes,

lycano