Post: #8

"run without problems" is not the same as "run correctly", that's why we had to change some old codes

just a quick example is the REPORTEDCLIVER, which was working fine, but not correctly. Or sphere main clock (aka SERV.TIME) which was also working fine, but not returning high precision values (needed by fastwalk prevention engine). Or some old packets, which was working fine as always, but not on newest clients, etc. Things like this can't be softcoded, and even some other things that can be softcoded would need some internal support (eg: STEPSTEALTH property on stealth skill, etc)

but anyway, we are already preparing for an 56c pre-release launch since 3~4 months ago, also I had sent the commit starting 56d but we decided to wait until 56c get all pending issues fixed/closed. Honestly I can't say that its 100% ready because my server is running an outdated build from last month (jan/2016) to test sphere stability, so I must update it to latest build and check if it still working fine. The good news is that sphere reached an incredible stability, because my server uptime reached 30 days and it still running perfectly

so I believe everything is ready, it just need a few more days to check if there's any missing error left