Is there really no way to definitively identify a world's current version?
I have a survival world that I haven't played in a long time. Since then I've updated Minecraft to play snapshots and test things in other worlds. In addition the world files have been moved around and possibly MCEdited so I don't really trust modified dates and whatnot.
I don't want to log into this world and have it auto convert to the latest version. I just want to know what version it is so I can use the new launcher to run that version of Minecraft and check it out before converting it to the latest, especially because I know it's pre-1.6.4 and I don't want to lose structures, etc.
The game has to know somehow what version a world is, so that it knows what conversions to make on the world file...
Do you know how basic the function for the formula would be :|
Algorithm simplicity =/= less CPU load. Case in point, the infinite loop:
while(true) {
//whatever
}
And AFAIK there is no method of keeping "colonies" of things intrinsic to MC. It would be a huge headache, very prone to conflicts, and a bad idea.
I think a better an more realistic idea would be to let plants such as mushrooms keep a private TTL (time to live) variable that made them pop-put/disappear after so much time had passed, and based on their surroundings. This would control infinite growth (except maybe on a dark infinite plane), but not remove the advantages of having mushroom growth (from both a realistic and farming standpoint).
Granted as far as I can tell, there is also no intrinsic method of having blocks keep private variables for themselves either. And adding this to a potentially infinitely spreading block could be very dangerous. Things like doors/redstone can be open/closed, or on/off, but they don't replicate.
That can happen. It can spawn anywhere in 3x3 square around the mushroom commonly, and uncommonly, in a 5x5 square. 1 block diagonally falls well within the 3x3 square.
Can you tell me which rule it seemed to defy? If I was unclear, or worse, made a mistake, I would like to clear it up.
For the visual learners:
Top view:
Side view:
= original seed mushroom
= more common growth from original seed
= uncommon growth from original seed
= no growth from original seed
1
I have a survival world that I haven't played in a long time. Since then I've updated Minecraft to play snapshots and test things in other worlds. In addition the world files have been moved around and possibly MCEdited so I don't really trust modified dates and whatnot.
I don't want to log into this world and have it auto convert to the latest version. I just want to know what version it is so I can use the new launcher to run that version of Minecraft and check it out before converting it to the latest, especially because I know it's pre-1.6.4 and I don't want to lose structures, etc.
The game has to know somehow what version a world is, so that it knows what conversions to make on the world file...
5
Algorithm simplicity =/= less CPU load. Case in point, the infinite loop:
And AFAIK there is no method of keeping "colonies" of things intrinsic to MC. It would be a huge headache, very prone to conflicts, and a bad idea.
I think a better an more realistic idea would be to let plants such as mushrooms keep a private TTL (time to live) variable that made them pop-put/disappear after so much time had passed, and based on their surroundings. This would control infinite growth (except maybe on a dark infinite plane), but not remove the advantages of having mushroom growth (from both a realistic and farming standpoint).
Granted as far as I can tell, there is also no intrinsic method of having blocks keep private variables for themselves either. And adding this to a potentially infinitely spreading block could be very dangerous. Things like doors/redstone can be open/closed, or on/off, but they don't replicate.
1
That is all.
1
For the visual learners:
Top view:
Side view:
= original seed mushroom
= more common growth from original seed
= uncommon growth from original seed
= no growth from original seed