Hey, no forking. We are still here in the project.
You made two posts on this forum since March 10... two posts in one whole month... and the coin is only two months old... you call that still here in the project?
This is exactly what I hoped to avoid, a dead developer coming back a couple days before the fork to stir up stuff.
1. We took voting, community voted for changes current dev won't do.
2. We took voting to replace current dev, community agreed.
3. We have almost everything ready and old ghost dev comes back.
4. Important: I'm not lead dev nor do I want to be. I can easily be a lead dev/organizer but that is a lot of work. Like... Even as an experienced developer it's a lot of work. I will do it. I will be dedicated, but I am not stubborn or unwilling to give back to community or fully give over to new or old developers.
Unfortunately though old dev coming back causes people to have hope. Honestly... I've run 10 OT server and 4 Minecraft servers, 3 websites, and 4 crpytos myself. I'm not trying to say i'm better because i'm not. I just realize this dev isn't back, and if he is... What hope to we have? Still better to go with more experienced team willing to listen. What hope do we have with old inexperienced developer who is not used to trusting or working with people and goes on "sick leave"(The entire team mind you) during a crash. That's not okay. If your a single dev you fight whatever you have and at the VERY LEAST update people/let new devs take over if your sickness continues. To pretend to be a "team" and community finds out your a single person... and then all the above happens.... Going ghost for 4-5 weeks really... We just can't trust old dev.