robustus

oh lord man, been a while since I worked on Minecraft. Gave up modding because the source code kept changing too much and yadayada decided to work on my own game. If it's still somewhat the same as when I was working on it, I had to pretty much rewrite the ChunkProvider, and in the provideChunk function you can insert checks on height there. I had a funky biome that would leave large areas of water so I wanted to rename these areas like "Lake" or something, so I inserted a check, if this biome, i'd do checks to see if there was water and if the water checked passed I changed that area to the biome Lake. I started to get fed up with playing within the confines of the Minecraft generation rules after that and looking into my own engine but yeah it almost needs a whole new generation system to do sophisticated stuff without bogging down the code. If you simply just want to do checks on which biome is next to which biome you need to start breaking down the GenLayer files. I'd recc. playing around with it all anyway, I learned so much coool stuff messing around with it, like making nice beautiful huge rivers.

I hear ya, I been working on learning what everything does in world generation for literally years now and am still learning, but I can possibly lend a hand if you ever need any questions. The real break though for me came when I learned what all the GenLayer classes do and how to use them to customize the entire world gen process. For example if you want biomes to be different sizes and how they connect to each other etc etc. It is pretty fun messing around with it.

I modify size of the biomes in a customized GenLayer, but looks like you got it your way also.

thanks. Taking a look at the Box blur approach. I just have issues comprehending how and where in the code to compare 2 chunks and where it actually splits the chunks where biomes connect in the middle of it I think

so ive kinda become obsessed with learning about noise generation to do some cool things with the terrain but I can't seem to figure out a way to stitch the terrain easily from one biome to the next because im using custom noise functions inside each biome. I kinda see how they do it via the heightmap creator in the chunkprovider where they blend the base heights of the biome but im trying to connect a little more smoothly. Easiest way I can think of just a simple worldgen to check the biome edge and smooth out the terrain a little bit, but was hoping maybe better alternatives. Problem seems to be reliable checking where the biome edge is what have you. I don't know really where to start Ive googled the issue and seems there is no real solution to stitching terrain any tips or ideas would be appreciated

I didnt get too deep into this but if the lights are spawned in the biome decoration they are fine if they are spawned earlier than that they wont update.

i would try first to delete the tintindex option at all from the stone that you dont want colored and make trhe colored part tintindex of 0. if that doesnt work try replacing block/cube_all with block/block

is there any way around this? I'm totally rewriting my mod from scratch to update to the current version. In pre 1.8 I was able to change a few textures based on conditions that didn't need metadata set, like biome, altitude etc...

are those two //'s in your code snippet above in the actual file itself??

ok, I think I get it. Im looking specifically at this bit of code if I have to guess this is taking all mutable blocks around a certain block to get the color of the current block, is that correct?

Can someone explain to me what this does? Ive looked around but have not seen an explanation. Ive seen it a few times but have not needed to use it or have used other methods but am running into it would like to know it is used for. Thanks

Just wanted to say thank you, I used trollworkout's code to get slabs up and running. I tried for few days to get it working on my own so I could at least understand it but I think the ItemSlab was where I couldn't put it all together, so I finally gave in and tried his, and got it working, the itemslab saves the day. Just a few notes though incase someone else comes across this thread, I did have to tinker a little with the code, as the slab was showing up 3 times in the creative tabs as the item, the half and the double slab, and for all intensive purposes you only want the itemslab to show up because it's the key to the blocks logic, so I added this bit of code onto the SlabBlock code and also need to add in that breaking the block will return the Item and not the block, not sure how you made it work completely on your end troll as I didn't want to go reading all your code but just wanted to throw my 2 cents in in case anyone is having trouble because, these slabs are, I feel unnecessarily difficult. Thanks

thank you for your response, very helpful. I'm wondering if I would be better off almost rewriting the entire mod from scratch in 1.9 instead of trying to patch up the old code. What would you suggest?

So basically I have this fairly large mod that I was working on. Spent countless hours on it, countless hours learning the ins and outs how to make mobs how to do render custom blocks etc the whole works. This is a large mod. Every time an update happens its hours to go through and fix everything. I kept the mod up to date until 1.7 but the upgrade to 1.8 seemed really to knock the wind out of my sails. I have tons of custom rendered blocks on top of everything else like mobs and world gen etc. I wonder if it is worth it to even begin to try and update the mod all the way to 1.9. If I did I imagine by the time I get there the next version will be out and the mojang programmers will probably rewrite and make stuff even more difficult. Ive noticed the amount of mods are shrinking as Im sure plenty of people are tired of constantly having to completely recode their mods in some cases. (Also please do not take this the wrong way, my complaints have nothing to do with Forge and the people who spend even more time then I can ever imagine updating Forge to deal with these completely rewritten parts of Minecraft. You guys are champions. ) I just don't want to let the mod go unfinished and unreleased tho, I spent many many many hours and I believe people would really love it. How long does it take to get familiar with the new json system of rendering blocks? Once familiar with it, is it easier than the previous rendering system? Does anyone else feel kind of exhausted and defeated? Guess Im kinda just hoping for a pep talk lol. Sorry for the ramble.

Maybe someone can help me I was looking for more control over the spawning of my custom mobs, for example wanted to make a very very rare mob but it seem the normal way to do it even if you put very low weight on how many mobs spawn its still much more than I want, I was wondering if anyone knows of a code to spawn a single mob like you would a regular block during terrain gen, like how setblock would do it for blocks, is there a way to do with this mobs? Thanks

oh my bad then i thought I was using 1.7.10 i guess Im using 1.7.2

I dont see that method in EntityEnderman and if I try to add to the boolean of carriable blocks it is saying its private. I guess I will have to try to overwrite the enderman

Is there a hook for this or do I have to overwrite the vanilla enderman?

In my mod I have a biome cluster that is all custom blocks which I keep crashing in and its giving me this error Which points to this block of code in EntityEnderman And since the biome is all non vanilla blocks I am assuming this from what I can tell is possibly the issue here? I tried removing the Enderman from the spawnlist in the biomes but still having this problem. Anyone have any advice? Thanks

You can set biomes up to have a border biome, like how ExtremeHills has ExtremeHillsEdge or used to, so you can have your Biome, and have a border biome that either you generate the extra blocks on or just have the altitude of the biome a little higher to give the appearance of a wall.

Ive been learning mob animations myself recently and have been using the same code. BTW thanks Jabelar for that and your tutorials, very useful. I think and I could be wrong, that the code sets the proper rotation angles of the child, but the actual rotation point locations need to be adjusted as well to offset now from the parent instead of the normal offset. Its a bit complicated, maybe I'm explaining it wrong.

Add them the same way as you do custom biomes just make the name the same as the vanilla and it will override it.

http://www.minecraftforge.net/forum/index.php/topic,17885.msg90964.html#msg90964

http://www.minecraftforge.net/forum/index.php/topic,17885.msg90964.html#msg90964

You shouldn't need to edit the terrain generation to have your own custom top and filler blocks, just specify them in the normal way.