Minecraft Forums

Look at the vanilla implementations.

BlockLog is the abstract base class for log blocks that handles rotation and leaf decay, BlockOldLog and BlockNewLog are the concrete implementations that handle the variants for the old and new log types, respectively.

WorldGenAbstractTree is the abstract base class for tree generators, WorldGenTrees is the concrete implementation that handles generation for most of the old tree types. There are various other implementations that handle other types and sizes.

Forge's blockstates format (documentation, specification) will come in handy for the logs. This will let you specify the textures and rotation separately without having to create a blockstates file for each log type like vanilla does.

Quote from Markyroson»

Thank you for this. Should I copy and paste the code and modify it or simply extend BlockOldLog and BlockNewLog?

Extend the base log class, not the subclasses. You should try to understand what the subclasses are doing before you copy their code.

Quote from Markyroson»

Sorry, I just have never worked with this before.

What should I override once I do extend BlockLog in order to successfully create my own log?

Sorry but the only resources I found was from 1.6.4 and is way too far out of date by the looks. Not even anything for 1.7.10.

Look at what the subclasses override.

You basically need to handle everything related to the log variant including the blockstate creation (variant property and createBlockState method), blockstate <-> metadata conversion (getStateFromMeta and getMetaFromState methods) and item metadata dropped from regular and Silk Touch harvesting (damageDropped and createStackedBlock).

Keep in mind that the SwitchEnumWhatever nested classes in MInecraft's code are automatically generated by the compiler, you can just switch directly on an enum value in your code.