amadornes

Hey! So you have a 1.11 mod and want to have a go at supporting MCMultiPart 2? Great! Let's get started!

I should first of all note that the API is NOT final, though the changes to it won't be very big and most likely won't affect you. Still, I would recommend doing this in a separate branch.

Depending on MCMP2

The first thing you'll want to do is add MCMP to your dev environment. You can read about that here: https://github.com/amadornes/MCMultiPart/blob/1.11/README.md
You'll need to use experimental builds because there is no stable build yet.

Creating an addon

williewillus

#WIP

Last updated: Wednesday, April 6

This is a quick primer for the cool 1.8.9 kids. Knowledge of 1.8.9 assumed.

• Notable class remappings:
  • See https://github.com/kashike/migration/wiki/1.8.9-to-1.9
  • If you use IntelliJ IDEA, import this migration mapping and it will zap half of your compile errors! :P
• https://gist.github.com/bonii-xx/dcb1b6a9a1d13b69a1c9

williewillus

1.8 Rendering Primer by williewillus (formatted to markdown by gigaherz)

Note: This primer assumes you are using MinecraftForge 1.8.9 build 1670 or above. Correctness not guaranteed otherwise. Note 2: This primer is for 1.8.x. Changes in 1.9 are on another gist: https://gist.github.com/williewillus/e37edde85dc78d2e138c

This guide is intended for those with a clear knowledge of general modding and want a quick up to speed on how new things work. If you are confused, please hop on IRC and ask for help!

Blocks and Items

• 1.7: EVERY BLOCK SHAPE EVER was hardcoded into RenderBlocks or your ISBRH. Oh God, just look at that class. Actually don’t, if you value your sanity.

RainWarrior

<blockstate> == {
  "forge_marker": 1,
  "defaults": <variant>, // optional, added to all variants
  "variants": {
    "<property>": {
    "<value>": <variant> // variant definition for the specified value of this property; variants for multiple values can be specified.
  },
    "<variant name>": <variant>, // variant definition for the full variant string
    "<variant name>": [<variant1>, ...], // array of definitions for the full variant - result will be the random variant
  }