Still on 1.7.10
Sep. 28th, 2014 12:38 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
owsf2000I wonder if this is one of the first minor effects of Mojang being bought by Microsoft - slow updates to initial version release bugs.
We had tried to update Pseudo World to 1.8 about a week after it was released but found there were 2 conversion bugs introduced.
1. When players logged in, probably just for the first time, flowers and apparently some chests would get popped into items and fall on the floor.
I had noticed the flowers outside of Main Station popped and lying there for no reason (I kind of assume it's because they were next to light sources but I really don't know for sure) but it wasn't until a bit later after fixing some of the things with #2 below that I went inside the station and saw several chests... just..... gone. That was the breaking point of doing a rollback to 1.7.
2. All nether portals were deactivated. Meaning we had to reactivate them all manually. And this was a bit more problematic than you'd think given how many portals we freaking have. Plus, inactive portals aren't instantly relit when you go through the other side. So often times we ended up with temporarily cross-linked portals and new portals forming next to, or on top of, or nowhere near, existing (but inactive) portals.
I had reactivated and fixed a bunch of portals, but there were still a LOT to light. And the odds of me forgetting or outright not knowing all of the ones that exist were quite high anyhow.
The delays in fixing stuff like this (We ALWAYS have at least 1.x.1 if not 1.x.2, 3, 4, etc, within the first week or two of a major release) may just be mojang having to pick up bukkit and update that to 1.8. But then I guess the whole bukkit mess is linked to the microsoft deal indirectly.
If it continues on, we might have to bite the bullet on this and update again and deal with the buggy code. I'm going to want to do some planning for it beforehand however.
We had tried to update Pseudo World to 1.8 about a week after it was released but found there were 2 conversion bugs introduced.
1. When players logged in, probably just for the first time, flowers and apparently some chests would get popped into items and fall on the floor.
I had noticed the flowers outside of Main Station popped and lying there for no reason (I kind of assume it's because they were next to light sources but I really don't know for sure) but it wasn't until a bit later after fixing some of the things with #2 below that I went inside the station and saw several chests... just..... gone. That was the breaking point of doing a rollback to 1.7.
2. All nether portals were deactivated. Meaning we had to reactivate them all manually. And this was a bit more problematic than you'd think given how many portals we freaking have. Plus, inactive portals aren't instantly relit when you go through the other side. So often times we ended up with temporarily cross-linked portals and new portals forming next to, or on top of, or nowhere near, existing (but inactive) portals.
I had reactivated and fixed a bunch of portals, but there were still a LOT to light. And the odds of me forgetting or outright not knowing all of the ones that exist were quite high anyhow.
The delays in fixing stuff like this (We ALWAYS have at least 1.x.1 if not 1.x.2, 3, 4, etc, within the first week or two of a major release) may just be mojang having to pick up bukkit and update that to 1.8. But then I guess the whole bukkit mess is linked to the microsoft deal indirectly.
If it continues on, we might have to bite the bullet on this and update again and deal with the buggy code. I'm going to want to do some planning for it beforehand however.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2014-09-29 03:46 pm (UTC)