I need someone who can code dimensions for my mod. You will need to be able to code it in a way where we are not limited to using block Ids smaller than 256. It would also be great if you know how to program terrain as well. A link to the mod in question would be here

http://www.minecraftforum.net/topic/1403995-152-code-lyoko-mod-043-minecraft-forum/

The 256 limit only applies to the core block of the dimension (stone for vanilla) and the 2 biome blocks for each biome (top & filler block).

So unless you have a massive number of biomes, you wont have problems with the 256 limit.

 

A rewrite of such proportion as to account for bigger block values is quite tedious and I believe you will need to create your own chuncks as well as your own way of storing the ids during gen

I am very well aware of this. I just don't want to have to make some of my block ids smaller.

Okay just saying, that it would be a lot less work that way by having two id ranges you occupy.

 

Anyways if you or anyone else is interested the change you need to do is in the ChunkProvider's provideChunk(int int) method. This is where the byte array is declared like this:

 byte[] data = new byte[32768]; 

After that it's used inside the generateTerrain and replaceBlocksForBiome both of which are inside the ChunkProivder.

Then it calls for cavegen and other generation classes.

And lastly it passes the byte array into a new Chunk.

Inside the chunk's constructor it's turned into ID's in the ExtendedBlockStorage which is used by the world.

 

So you would have to create your own version of chunk, which just has a new constructor.

And do some changes in the ChunkProvider (and optionally in the cavegen and other gen classes like that).

The most notable thing to understand would be how a given x/y/z position relates to a spot in the array.

Within the generateTerrain you find this line:

 int position = var42 + var10 * 8 << 11 | 0 + var11 * 8 << 7 | var12 * 4 + var31; 

which is used to get the position in the byte array, based on where in the 5 for loops we are atm.

 

I haven't gotten further yet myself, as I haven't had more time but it seems like it isn't to much which needs to be done in order for it to work nicely

 

 

 

I think I'll make another attempt at doing this then.