Java-программисты майнкрафта, инженеры хуевы блядь .\_/.
http://notch.tumblr.com/post/7799649091/...

Вы только посмотрите на этот исчерпывающий анализ ПРОИЗВОДИТЕЛЬНОСТИ майнкрафтокода, а также на его РАСШИРЯЕМОСТЬ:
| Search through the codebase for « 11 and « 7, replace with « 12 and « 8 as necessary.
| Search through the codebase for 128, this will hit the majority of places that assume the map height as being 128, such as tile height checks.
| When changing the above locations, save yourself a recompile and make sure to change any variables from bytes to shorts or ints if you’re increasing them past 128. Being a C++ engineer, I keep forgetting that everything is implied as signed in Java.
| Search through the codebase for 127, this will hit the remainder of places that assume the map height as being 128.
| Search through the codebase for 64 and 63, this will hit the places that assume sea level is at 64, as well as Iron’s ore generator height cutoff. Personally, I dialed sea level up to 96 from 64, rather than fully double it up to 128, in order to have 32 additional tiles’ worth of water height, but have an entire 96 additional tiles’ worth of land height.
| Fix up the level feature generators for Redstone, diamond, gold et al.
| Visually grep through all of the level feature generator classes, doubling the RNG baseline and spread for each one.
| Change a few instances of 32768 to 65536 to accommodate 16*256*16 rather than 16*128*16.
| I’m not sure how much of this is a result of JAD and how much of it is actual code, but there are a few instances of “char whatever = ‘\200’;” in the MCP codebase, change it to a short or int containing 256 instead of 128.

#gfzno

6 comments recommend bookmark subscribe