Bukkit

What do you mean by Internal Rebuilding

Movecraft now has a five man long authors list. This is because in its entire history, movecraft has simply been smashing the old code together to make it continue to work. Not only is this unsustainable due to the poor coding standard left behind, it also springs large memory holes and uneccesary if statements etc.

As such we have decided to slowly and methodically, recode every aspect of movecraft from the inside out. While we continue to recode each section while we add in various appropriate APIs.

What's the point?

With the current instability in the future of minecraft modding, we are aiming to create a movecraft which can be easily ported to another platform. We also want to increase the speed of movecraft, and correcting code flow is critical to that.

How long will this take?

Anywhere between a couple of months and a week.

Will this affect me?

We are aiming to minimise disturbance to users throughout this change, hopefully you will see a large increase in the speed of movecraft and a reduction in the number of bugs. Please just keep up with these notification pages, and well make sure you know commands, config and permissions by the end.

So where are we now?

The config changes are now almost complete. We are currently working to convert craft files to YAML. We have added a few APIs here that allow modules to add options to movecraft config and craft files.

Why start with the config

Start from the bottom and work up.

Bug Fixes

A large number of the current bugs in Movecraft are down to poor algorithm implementation, or simply careless errors. We are going to go through the recode, attempting to fix these bugs. Rest assured, it is our mission to make chests and signs work.

What can I do?

We are going to need testers for every build we ship, so we are going to tr and take the following release plan.

Releases

Releases will be posted on our bukkit dev page and will have been tested for bugs thoroughly. There should not be any bugs in releases, however they may lack some of the more unstable features.

Betas

Betas will also be posted on bukkit dev. They will have been checked to ensure the API works and any bugs are at worst irritating, nothing game breaking. They are usable and offer a wider array of features, but risk instability on production servers.

Bleeding Edges

Our bleeding edge build will be sent to any server owner registered on our development interest list. Any one who makes there server a forum page is part of this list, and other admins can simply PM me to get on it.

People on this list will be emailed a download link for every new build that we feel has a feature worthy of testing. No stbaility is promised with this and Bleeding Edges will likely contain bugs and glitches, but will have the most expansive array of features and APIs.

Release date for update one?

The new config changes will likely release as a Bleeding Edge on Friday evening (GMT) and will be a beta by Sunday. As always VariousArtist will be running the tests first, then we will likely release to anyone who PMs us.

Why make your earlier build process so selective?

We do not want to give support for the early testing. There are two many things that could go wrong to provide support, it is hoped that this selective release in the very early stage will select admins who are capable of understanding movecraft without help. When it is in Release and we have time to streamline the changes, we will be able to provide help.