02-18-2015, 03:22 AM
A workable, though time-consuming method could be to simply follow changes to the server and the issues that they fix, and also work out solutions to the many issues reports open. That would give a good familiarity to the code.
You could also try following the execution path from start to finish as a computer would. Look at what happens and what is run each tick.
Alternatively, look through header files and use VS to examine which functions are called by whom, and what do they themselves call/do. Look at some important files such as the block handlers, World.cpp, Chunk.cpp and perhaps how the simulators control the world.
An inheritance map, generated by Doxygen or VS Community Edition (like Professional but free), may also aid you in understanding how things link together.
Of course, I'm sure xoft could bypass that work and just explain it all to you :P
You could also try following the execution path from start to finish as a computer would. Look at what happens and what is run each tick.
Alternatively, look through header files and use VS to examine which functions are called by whom, and what do they themselves call/do. Look at some important files such as the block handlers, World.cpp, Chunk.cpp and perhaps how the simulators control the world.
An inheritance map, generated by Doxygen or VS Community Edition (like Professional but free), may also aid you in understanding how things link together.
Of course, I'm sure xoft could bypass that work and just explain it all to you :P