Project Zulu : A Better Overworld is a mod that provides a more engaging, challenging and ultimately a far better Minecraft Overworld experience thru the addition of unique Mobs, Plants/Trees, Items, Blocks, Structures/Dungeons and Game Mechanics.

PZ Features... just a few of many waiting for you to discover or craft!

PZ Hostile Mobs, just a sample of what's waiting for you in the dark or out in daylight!

PZ Passive Mobs

A few more....

and some more passive mobs...

** More sample pics to come!!!

Project Zulu for MC 1.7.10 is a continuation of Crudedragos' great work, which can be found here.

so WHAT'S NEW in the Project Zulu 1.4C2 version?

Revived Death Rules

Sample Death Rules configuration (mirrors the catch-all system prior to current version)

FOR MORE INFORMATION PLEASE VISIT...

• Original Author's Wiki
• Original Author's Blog
• Hexxit Project Zulu Wiki

SOURCE

• Source at Github (for updating)

GENERAL

BLOCKS AND ITEMS

ARMOR AND WEAPONS

PLANTS AND TREES

MOBS (PASSIVE, well most of the time)

MOBS (Hostile)

STRUCTURES/DUNGEONS

GAME MECHANICS

CHANGE LOG

Project Zulu 1.7.10 v1.4C2 Primary Link

Project Zulu 1.7.10 v1.4B4 link1 link2

INSTALLATION INSTRUCTIONS
1. Install Recommended Forge version for Minecraft 1.7.10.
2. Backup old PZ Config folder, either through relocation or renaming.
2. Copy Project Zulu jar file into the MC Mods folder (%appdata&/.minecraft/mods)
3. (Optional) Configure Project Zulu via configuraiton files in %appdata&/.minecraft/config/ProjectZulu
4. Enjoy!

CREDITS
Many many many thanks for Crudedragos for allowing me to tinker and continue with his work. And a massive thanks as well to all those that support and provide comments/suggestions/feedback on this thread. This mod can never really move forward without you guys.

NOTES: (Lifted from the original author's thread)

Awesome! I'm looking map like this for years!

I think you left something in the ender chest.

Quote from Tmtravlr»

Hey, if you send me the translation, I'll put it in the next version. =)

YAY!

Quote from Tmtravlr»

And update time!

B-b-but... not too fast! D:

(just kidding, I'll send them after a brief review)

What I liked most in this update? No more dead fish scattered all over the place in unsuitable dimensions.

(Tweet)

And I can finally fish as the mod was meant to!

---

Table of Contents:

Overview
Changes in how things work
Frequently Asked Questions
[WIP] The Cubic Chunks Mod!
Gallery
Supporting this suggestion
Special thanks

[spoiler=Tl:dr]Q: Won't this increase lag?
A: Absolutely not. The title of this suggestion and big red letters at the top of this post aren't lying. If you want to know how, then I suggest you actually read this post.

Q: Will this change terrain? Will this break existing worlds?
A: No. Terrain change is not necessary. Existing worlds can be converted fairly easily with a process described later in this post.

Q: How can sunlight or rain work with infinite vertical space?
A: I suggest you read Coping with sunlight, because it's too complex for a tl;dr.

Q: I have a different question but still don't feel like reading this post. What do I do?
A: Too bad, read the FAQ. I put way too much work into this for the entirety of it to be ignored.[/spoiler]

---

Overview:

In Minecraft, the sky is the limit - literally. It doesn't matter how many thousands of blocks a player has traveled, or what dimension they're in, or even if they're playing in creative or survival, the highest they can ever build is up to a height of 256. Why is that? If Minecraft can have a world that's infinite in the north, in the south, in the east, and in the west, why can't that world be infinite up and down too?

In Minecraft's earliest days, in Classic and Indev, the world was not infinite in any direction. This was because the entire world needed to be generated at the same time, and the entire world needed to be simulated at the same time as well. This led to a conundrum - the bigger the world, the more it lagged.
Notch didn't like this. He knew his players liked to explore and build large creations, so he found a way to make the world truly infinite. When the Minecraft '' class='bbc'>Infdev came out, it brought with it truly infinite worlds. Suddenly, players could travel hundreds of thousands of blocks in any direction, and never encounter a barrier, or become too laggy.
The Infdev update brought about a very large change to Minecraft worlds to accomplish this feat. For the first time, instead every world being just a single huge piece, they were broken up into a two-dimensional grid of pieces, called chunks. Through breaking the world up into pieces, this 'chunk system' enabled infinite worlds by letting Minecraft create new pieces and simulate them only when it needs to.

Why does that not apply to the vertical axis? Because the type of 'chunk system' Minecraft uses right now is a linear one, which, by using only a two-dimensional grid to map out chunks, means that it is impossible for chunks to stack on top of one another, and by extension, meaning that a single chunk must cover the entire vertical space. This brings back the problem that the Infdev update was supposed to eradicate, now only with chunks, instead of an entire world; the bigger a chunk is, the more laggy it is. You can't just increase the height limit and make chunks taller, because it will become laggier, and laggier, and laggier to do it.
That's why, to fix this, Minecraft must change over to a cubic chunk system. Under this system, 16³ block chunks are aligned on a three-dimensional grid, completely eliminating maximum height as an aspect of lag.

The immediate benefits:
•Minecraft worlds become as virtually infinite vertically as they are horizontally: The absolute limit being Y = ±30,000,000.
•A large FPS increase: Alpha testers report an FPS increase of 100~200%.
•Increase in running capability: Computers running Minecraft on Tiny render distance will handle only 30% the blocks they do now.

The possible features:
•Spherical render/load distance: Reduce handled blocks by up to 30% by cutting corners made of unneeded chunks.
•Server chunk occlusion/exclusion: Reduce bandwidth usage and defeat hackers by only sending data for visible chunks.
•Three-dimensional biomes: Save biome data per chunk rather than per block column, create volcanoes with magma chambers, underground rivers, tropical skylands floating over icy taigas, and more.

The disadvantages:
•Unloaded gravity-pause: Falling non-player entities and fluids will be forced to pause their fall if they reach unloaded chunks, but will resume falling when those chunks are loaded.
•Slow falling-pause: Players with slower computers and smaller render distances will have falling occasionally paused as they fall into unloaded chunks, until new chunks can be loaded.

The problems:
•Current sunlight and rain calculation methods cannot work with infinite vertical space: The solution to this is described here.
•Current BiomeDecorator cannot work with multiple vertical chunks simultaneously: The BiomeDecorator code must be altered to function correctly with this, or removed.
•Current cave generation method is executed an extra time for each vertical chunk created simultaneously, leading to lag spikes on world generation: Cave generation's method must be altered to suit this system more.
•Current grass/dirt generation algorithm forces additional chunk requests when chunks are loaded, causing chunks to load slower than they should: This algorithm must be replaced with something else.

---

Changes in how things work:

Obviously, the implementation of this new chunk system will change quite a few things. These changes are mostly either necessary or in the interest of increased efficiency. Such changes are categorized and explained below.

How worlds will be stored:
[spoiler]How the current storage works, and what changes:
Interestingly enough, the current method of storage, the Anvil format, is derived from the storage method that the original Cubic Chunks mod used. The Anvil format stores individual chunk as a series of 16³ quasi-cubic chunks. These 'fake' cubic chunks allow for easier reference of specific data, but they still can't be separated from each other, meaning that it fails to reap the full benefits of this system. Even so, the change allowed Mojang to double the maximum height with no performance hit. Chunks are stored in groups of 32², inside 'MCRegion' files, for a total of 1024 chunks.
By nature, cubic chunks does away with the 'quasi-cubic' nonsense. In terms of chunk grouping, instead of using groups of 32³ chunks, new "3DRegion" files would contain groups of 16³. This means each 3DRegion file contains 4096 chunks, four times as many as MCRegion files. However, each 3DRegion contains only one fourth the amount of blocks. For per-chunk positional metadata, 3DRegion files would use the same number of bits as MCRegion files, after compression. Calculations show that the same area encompassed by a single MCRegion file would consume 64 kilobytes of extra space with 4 3DRegion files, which is nothing.

Converting existing worlds:
Most people are probably wondering something like "But won't this totally destroy all existing worlds?". Absolutely not; conversion could not be simpler. When a non-cubic world is loaded after the implementation of this system, a conversion process will begin and convert the entire world at once(To avoid making chunk loading take longer during play). First, all existing MCRegion files will be divided into quarters to create 3DRegion files. Then, all existing chunks are divided into sixteenths using the quasi-cubic properties to identify boundaries. After that, conversion is done.

The "isEmpty" flag optimization:
A 1-bit flag is added to each chunk, named "isEmpty". If the chunk consists of 100% air blocks, this bit is 1, any other case makes it 0. When the bit is 1, all data for the chunk besides the isEmpty flag is deleted and ignored, which reduces filesize. Empty chunks are never loaded, and locations where they occur are merely simulated as entities reside in them. The chunk will only load when something requires saving inside it.[/spoiler]

Changes to terrain, ores, etcetera:
[spoiler]Terrain:
By default, nothing will change. Small bits of terrain generation code need to be reconfigured to work properly with Cubic Chunks.

Biomes:
By default, nothing will change.

Ore generation:
By default, nothing will change.

Structures:
By default, nothing will change.

The Void:
After conversion to Cubic Chunks, the void and bedrock layer will still exist and generate as they always have. However, the void(Not the bedrock layer!) will not exist as a hard limit and is able to be moved, but not removed, by editing an associated NBT data tag inside a world's level.dat. This feature, that allows for increasing the maximum depth, is intentionally disabled without external programs, to prevent terrain change of any sort. It is intended to be used by experienced mapmakers and world generation mods only.

Superflat settings:
Existing superflat worlds will not change. However, new superflat worlds will gain a new decoration parameter, 'void'. Inclusion of this parameter will cause the void to form below the lowest defined layer. Exclusion of it will cause all layers below the lowest defined layer to copy the settings of that layer.[/spoiler]

Coping with sunlight:
[spoiler]There used to be a solution here, but it wasn't deemed good enough by Jeb. Suggest solutions in this thread.[/spoiler]

Changes to servers:
[spoiler]Settings:
There's a setting inside the Server.properties file called 'max-build-height'. The setting makes it impossible for any player to place or remove blocks above that height.
With the implementation of Cubic Chunks, a new setting named "maximum-generation-depth" would be added. The void, bedrock layers, and magma layers will generate normally at and above the Y level designated by the value of this setting.

Chunk occlusion/exclusion:
Using the raytracing methods already available in the code and used for explosion calculations, servers can identify which chunks are visible to a player, within safe assumptions, and only send the data for those chunks. This both reduces bandwidth usage, and cripples the usefulness of X-Ray cheats.[/spoiler]

Render/Load distance alterations:
[spoiler]After the implementation of Cubic Chunks, view distances' radii will apply to the vertical axis too. This reduces handled blocks in the cases of tiny and short render distances, and increases them in the cases of normal and far render distances. This can be optimized by utilizing a spherical render distance instead of a cubic one, which would reduce handled blocks in all distances except Far.[/spoiler]

---

Frequently Asked Questions:

[spoiler=FAQ]Q: This is impossible.
A: No it's not. See below.

Q: Is this available as a mod?
A: Not yet! But it will be!

Q: I like X-ray! What if I don't want it to be broken?
A: First of all, breaking X-ray hacks will only be possible to do in multiplayer. That said, the system that would break X-ray would be possible to disable by the server owner. If the owner doesn't disable the system, then they don't want you using X-ray, and you should not be doing what the server owner doesn't want in the first place.

Q: I play on a PvP/Anarchy/Raid/Faction server. Won't this system let people pillar up into the sky and create a base thousands of blocks in the air and never be found?
A: No.

Q: I like Minecraft's current height limits. What if I don't want to have an infinite sky or infinite underground?
A: If this system is added, all worlds will not automatically gain an infinite underground. As stated below, the Void will remain in all worlds, even after the conversion to Cubic Chunks. The ability to remove the Void will simply be there. As for infinite space in the sky, the current build limit is over one hundred blocks above any terrain that vanilla Minecraft can possibly generate. It is ENTIRELY your decision on whether or not you take advantage of this height. If you play on a server, like stated above, the server owner can set a maximum build height. If s/he doesn't, then don't play on their server - you don't play on servers where the server owners allow things you don't like. Why would you play on an anarchy server if you hate being stolen from and killed?

Q: Will this affect Redstone at all?
A: No. This system will simply make it possible to make larger redstone circuitry than before.

Q: Won't this break existing worlds?
A: No. Existing worlds can be easily converted by dividing each MCRegion file into 4 pieces, then slicing the existing 256 block-high chunks inside them into 16 individual chunks.

Q: Won't this affect mods? Won't mod authors have a hard time updating their mods?
A: The answer to this question depends solely on the answer to the following two questions: Do parts of the modification code rely on chunk data/metadata? Does the mod author want to take advantage of the features of the new chunk system? If the answers to the first and second question are both "No", then updating a mod to this system should be very easy and quick. If the answer to the first question is "Yes", then those parts of the code will need to be rewritten somewhat, but in most cases, the changes should be fairly quick and easy. The only time that it should be hard to update a mod to this system, is if the answer to the second question is "Yes".

Q: Won't this require a total rewrite of the mod API if that's released first?
A: No. Whether or not even a small part of the mod API needs to be rewritten depends on the way that it is implemented and whether or not there are API inclusions for chunk handling and other chunk-related behavior.

Q: Could a player fall into unloaded chunks if chunks aren't loaded fast enough?
A: No, they could not, and for several reasons. Minecraft has a terminal velocity, though it might not seem like it. This velocity is slower than it should take to load new chunks below the player. In cases with exceptionally slow computers, even if the player did manage to reach an unloaded chunk, their fall would be paused until that chunk can be loaded.

Q: What would happen when water, sand, or a mob falls into an unloaded chunk?
A: Nothing. The water/sand/mob would freeze in place until the chunk is loaded and it can continue moving. You can already see this same thing happening on the horizontal axis.

Q: What will happen to the Void?
A: It will still exist, along with all its effects. The only difference is that the Void is no longer a hard limit and it can be moved. After the conversion to Cubic Chunks, the Void's location will be stored in a world's ' class='bbc'>level.dat, and this location can be changed with NBT editing tools. When and where the Void exists, chunks will cease to generate.

Q: Will this affect terrain?
A: No. However, terrain generators will gain the ability to use infinite height.

Q: Will this affect ore generation?
A: No. Ore is a part of terrain generation. As stated above, terrain will not be changed.

Q: Won't all current terrain generators be incompatible with this system and need to be rewritten?
A: No. Terrain generators work independently of chunks. When a chunk is generated for the first time, it calls the terrain generator and receives a specific section of the resultant terrain to save inside itself. Because of this, some custom terrain generators can generate steep terrain all the way to Y256, where you can experience a large, flat cut-off. Since there are no chunks above Y256 to call the terrain generator for terrain, no terrain exists there.

Q: What would happen if there's a huge solid ceiling so far above you that it is unloaded? Wouldn't you just see the sky, just with everything being completely dark?
A: Yes. This already happens on the horizontal axis, and it is an issue with sky rendering, not this chunk system. As such, this has nothing to do with this suggestion. Please do not post about this.

Q: If you go deep underground, will your plants grow/ores smelt/animals grow?
A: No, because those chunks would be unloaded, just as if you had walked far away. This is a flaw with any chunk system, regardless of shape. It is a necessary evil that allows Minecraft to have infinite worlds. The only way to fix this would be to introduce a separate new system that works with chunks as they are loaded and unloaded. This suggestion deals with the chunk system itself, and not sister processes. Because of that, that is outside of the scope of this suggestion. Please do not post about this.[/spoiler]

---

[WIP] The Cubic Chunks Mod! (Tall Worlds Mod):

Cuchaz has taken it upon himself to bring us the glorious Cubic Chunks, since Mojang refuses to do so.

Cuchaz is using a API of his own creation to help assist in the making of this mod, and he's quite far along, as seen in these two tech demo videos:
[spoiler=T-Demo 1: Vertical chunk loading][/spoiler]
[spoiler=T-Demo 2: Broken height cap and no lag!][/spoiler]
With the basic functionality in place - a complete overhaul of the basic chunk system, and height limit removed - this whole concept can already be considered proven. What remains is making sure everything else functions correctly under the new chunk system. In any case, stay tuned for future updates if it interests you(If it doesn't, then you are the weakest link - goodbye!).

You can follow the mod's development in much more depth in its very own topic!

---

Gallery:

[spoiler=A mountainside with an experimental engine using Cubic Chunks designed by Nocte. 960 block view radius, and 30 FPS.][/spoiler]
[spoiler=A different view of the mountainside with the same engine by Nocte. This time, with 1600 block view radius and 15 FPS.][/spoiler]
[spoiler="A video demonstrating Nocte's engine."]

---

Support & Submission to Mojang:

If you support this, hit the rep button in the bottom-left corner of this post. It is the only good way of accurately measuring support here.

If you wish, you can put the following banner, courtesy of laz2727, into your signature. It helps to attract support from all parts of the forum!

 [url=http://www.minecraftforum.net/topic/1707097-cubic-chunks-infinite-height-elimination-of-x-ray-and-more-60-supporters/page__st__0][img]http://img833.imageshack.us/img833/443/hov.png[/img][/url]

Please help us get word out of this suggestion! Share this with your friends, with Minecraft celebrities if you're familiar with them, or even with Mojangsters like Jeb or Dinnerbone! (Do not share this with Notch. Notch doesn't work with Minecraft anymore.)

The purpose of this suggestion is to have Cubic Chunks implemented in Vanilla. Being available as a modification does not fulfill that purpose. The modification featured in this suggestion is to act as a proof-of-concept only(Note: Its being featured here is to act as a proof-of-concept. The modification itself is on its way to becoming a fully fledged modification).

---

Special thanks:
Cuchaz, for taking Barteks' proof and running with it, to give us a truly functional Cubic Chunks mod.
Barteks2x, for updating the Cubic Chunks mod to 1.6.2, proving that it is possible.
Azraile, for posting the original suggestion and allowing me to take ownership of it.
Nocte, for helping resolve flaws and designing Hexahedra.
MineCrak, for a large amount of valuable insight and enthusiasm into the topic of Cubic Chunks.
aaronfranke, for helping resolve flaws.
PanJouda, for creating the original banner.
Flexico, for creating the predecessor to the current banner.
laz2727, for creating the current banner.
Robinton, for creating the original Cubic Chunks mod.
The_Watchman13, for answering all those stupid questions so I don't have to.

---

Note: Many calculations and information can be found among the many posts of this topic. There are too many for me to cite here, but if you wish, you can search for them yourself.

Quote from Tmtravlr»

That's actually a vanilla bug. The same happens with iron golems (go stand near one and watch the log).

They should make a sound when attacking you like an iron golem does though.

What's the sound that's meant to be playing then? The iron golems aren't making the sound, just as you said (and printing the same message). I mainly just need the file, which it sounds like you, or at least Killerreviews, seem to have functioning; I've added sounds with the sounds.json to fix witches already, and I've done the same with the iron golems now, at least with the sounds that were in the Minecraft assets folder, though it still doesn't seem to be playing the sound that's being mentioned here (and still producing the same message). It seems to be hard to find information on this unfortunately, probably because most of the golem sounds work (unlike with the witches, though that still took a bit of searching).

Ok so this is completely untested so if it breaks anything let me know, theres still some stuff to fix but hers a change log
removed penetrate, durabillity and sharpshooter for the time being due to bugs that im to tired to work out atm(it is midnight now)
changed blast to explode on collision
removed extendedplayerprops(was a good idea but i broke it to easy)
reformated entire mod to be something like 20 classes less
added .lang file and name translations are welcome.
added mcmod.info file just coz
fixed stupid mana creeper crash
AS far as i know random flowers don't grow any more(am going to look into hoe enchant idea)
changed icestep again, its maybe better

Also I'm incredibly tired now so i'd put a 50% chance on there being 14 notifications about bugs on here when i get up in the morning, just letting you know i might have missed some stuff so don't stress out to much, ill try do hot fixes tomorrow

https://www.dropbox.com/s/bh8qazbd7zjt3xi/1.6.x Alpha MoreEnchantments V10.zip

Hello!
I'm Maz and I have been modding for a while now.
I haven't released any mods and I don't plan to either. I'm modding mostly to learn and I do love learning more of this wonderful art of programming! Now with 1.6 hitting I found a question getting asked a few times and I got the chance to learn the answer so then I'll put it up here for others to learn as well

Please remember the golden rule of all tutorials I ever will create:
"First and before all, learn the basics of programming." This will save you time and tears, trust me!

If you want to learn java, then this is a great place to start and I would say that this is the pre-req. for modding.
http://see.stanford....aa-866adcae1111

A few words about errors:
[spoiler]
If you find my code to be wrong, outdated or unclear please post a comment saying so.
I'll try to fix my errors when my work and social life allows me to

If you get errors / crashes and need help then please:
- Provide the full error log pasted at www.pastebin.com or a similar paste site.
- Provide the source of all relevant classes on a paste site(with syntax highlighting set to Java), github or similar.
- Describe what you try to do, and what happens instead.
- If you post code inn the forum use CODE and SPOILER tags, else the thread becomes a mess and you're chance of getting help reduced!

Also I'm only one person, and this thread may not be the most active at a given time.
So to get help as fast as possible then remember the things mentioned above and go to
MinecraftForge - Modding Support Forum and ask there, at least if it's not directly related to my tutorials!
[/spoiler]

My plans:
[spoiler]
I don't plan on releasing any of the "common" tutorials, there probably won't be a lot of basic block tutorials and the like here. I'd like to write on subjects which are not already well documented.
Unless one can really make an improved version of the tutorial, I'd see no need to create a new text tutorial on the subject when there's already a good one out there!

My next subject will probably be another one related to Java and Eclipse more than Minecraft directly, but I'm pretty sure most of the folks here will enjoy it If you have suggestions feel free to voice them, I won't promise anything but if it's good I may do it or mention it for some of the other (and better) writers

I do have an active AFK life, just like most of the other modder/writer/human/alien's here.
So while I do want to get tutorials and information out here, I got to juggle my other stuff as well.
I will update this thread whenever I get the time and feel like it, not before! Sorry that's just how it is being adult like and all that. It sucks but that's how it is
[/spoiler]



Eclipse Keyboard Shortcuts!
Speed up you're workflow by using shortcuts, saved me a ton of time!
[spoiler]

In this text I will talk about a few things that will speed you up while using eclipse.
As with most other computer programs, eclipse got keyboard shortcuts. In fact it got tons of them so I wont even try to start covering them here!
Instead I will show you a few very usefull ones which I find myself using quite often.
So with that let's get started.

Renaming - Refactoring.
Mark any name, be it a method name or a variable name or even a class name.
Press Shift+Alt+R to start renaming. A small box will tell you to enter the new name so do it and press enter.
Eclipse will try to rename it everywhere inside you're project!

Go to decleration.
Mark any methodname, variable name or the like and press F3.
This will take you to the place where it's decleared.
I find it super useful when navigating minecraft's code!

Switch between open files.
Press Ctrl+E and you get a small box listing all the currently opened files,
use the arrow keys to select one from the list and tap enter to view that file.
PS: If you type when browsing the list, you filter the list to match you're input!

Open a Type like a class.
Instead of looking trough all the packages of net.minecraft.entity to look into the new EntityLivingBase,
you can hit a simple shortcut and open the "Open type" window.
Press Ctrl+Shift+T and start typing the type name.
It supports the use of * if you want all types with "fluid" in the name, then type
"*fluid" and you will get a list of all of them!

Open a file / resource.
You can open any file just as quickly as you could with any type above.
Just press Ctrl+Shift+R and it opens up the "Open Resource" window.
Which functions just like the one above except it searches for file names.

Quickly find variable or method inside a huge class.
If you are inside one of the larger classes like the World class and you want to find a method quickly, what do you do?
Do you ctrl+F and try to find it? Look at the Outline view and try to find it there?
Well there's an easier way, press Ctrl + O and a small box appers.
It contains a list of all the variables and methods of the class, and when you start typing it starts filtering the list.
So if I where to look for "SetBlock()" I'd just type "set" and it's right there, one click more and there we are!
Really useful! Also pressing Ctrl+O again shows the inherited members.
PS: To browse up and down the members of the list, just press Ctrl+Shift + Arrow (up or down).

Go to Line number #? Press Ctrl+L and enter the # of the line you want top, tap enter and there you are.
Organize Imports? Press Ctrl + Shift + O to make eclipse try to cleanup and fix imports for you.

Go to last edit location.
I must admit I accidently tapped this quite a few times and had no idea WHY I suddently jumped to the other side of the file!
But after learning of this shortcut I realised how useful it is.
Instead of browsing around to find where you last edited the damn file you only need to press Ctrl+Q to jump there.

Go top super/sub type quickly.
Instead of scrolling to the top of the file and clicking the extended classes name,
you can press Ctrl+T to show a dialogue where you can select super types of the class.
Pressing Ctrl+T again while the dialogue box is open will make it show Sub types instead!

Find ALL references to selected method/variable.
If you press Ctrl+Shift+G while having a method/variable marked, eclipse will search the entire workspace for references to it!
And shows you everywhere it's being used!


Some Text editing shortcuts.
Select to Line Start/End (Shift + Home/End)
Insert Line Above (Shift+Ctrl+Enter)
Insert Line Below (Shift + Enter)
Delete Line (Ctrl + D)
Move Line up/down (Alt + Up/Down)
Convert to Lower/Upper case (Shift + Ctrl + Y/X)
Toggle Comment (Shift + Ctrl + C)

Eclipse Shortcuts - Cheat sheet!
Michael Pellaton has created a nice two pages cheat sheet for guys like us
Just print it out and have it close by, and use shortcuts for everything!
After a while you won't need it anymore, you're hands will know them by reflex
Sheet can be downloaded from here: http://code.google.c...pse-cheatsheet/

Do you have any shortcuts you use constantly which aren't mentioned here?
Let me know by posting below and I will try to get it added to this list!
[/spoiler]

Adding custom sounds
Just a little info dump on how to add sounds for 1.6.X+
[spoiler]

Sound files should be placed into the following location:
"assets/{modID}/sound"
So for my mod which has a modID="mazmod" it would be:
"assets/mazmod/sound"

NB: Keep in mind all modid's MUST be all lowercase!
i.e. mazMod will result in an error when exporting the mod!

Sounds are loaded with the SoundLoadEvent, if you are unfamiliar with events you may want to look into them. The class name is irrelevant but you will need to reference it later.

public class TutSoundEvents {
@ForgeSubscribe
public void onSound(SoundLoadEvent event) {
// You add them the same way as you add blocks.
event.manager.addSound("mod_id:hit.ogg");
}

As with all events you need to register the event subscription, so forge knows to notify the class of events.
So add this to Client Proxy (or at least make sure to call it on client side only),
and call it during the setup.

MinecraftForge.EVENT_BUS.register(new TutSoundEvents()); // Name of the class containing the ForgeSubscribe above

Then you can play the sound at anytime by using the playSound.. methods of World such as:

// Args: entity, sound, volume (relative to 1.0), and frequency (or pitch, also relative to 1.0)
WorldObject.playSoundAtEntity(EntityPlayerObject, "mod_id:hit", 1.0F, 1.0F);
// if you have file names which ends with an number, exclude the number when using playSound!

Randomness to sounds
Minecraft has a simple and nice system for having variations in your sounds.
If I used just the "hit" for every onHit with my sword it would be rather static and boring.
So to fix that let's add two sound files like this:

event.manager.addSound("mod_id:hit1.ogg");
event.manager.addSound("mod_id:hit2.ogg");
}

These will be grouped as variations of the same sound, called "hit".
So by referring to the "hit" sound you will get one of the two at random!
You can of course have many many more different files than just two

To play them simply as it to play the sound name without the number:

world.playSoundAtEntity(player, "modid:hit", 1F, 1F);

NB!: asking it to play "hit1" or anyother sound name which ends in a number will fail even if it's the only sound in the group!

I hope this helped
[/spoiler]

Creating a new simple Fluid:
[spoiler]
While creating my own fluid I found a post on the forge forums where Homletmoo explained it to another user.
So I got it to work after a while and since then I have seen other questions about the fluid system, so I decided to use a few minutes to tell how to add a simple fluid.


We start by creating the Fluid, so create a class which extends Fluid.
Pass a fluid name to the super constructor.
Then we can set the Density and Vicosity of the fluid.
Lastly we want to make the FluidRegistry register the fluid.

Heres how my fluid looks like:

public class TutFluid extends Fluid {
public TutFluid() {
super("TutorialFluid");

setDensity(10); // How tick the fluid is, affects movement inside the liquid.
setViscosity(1000); // How fast the fluid flows.
FluidRegistry.registerFluid(this); // Registering inside it self, keeps things neat 
}}

We initialize the Fluid in the same way as with items and blocks.
It handles registration of itself inside the class so we only need to intialize it.
Because FluidBlocks need access to their fluids we must initalize fluids BEFORE blocks!

public static Fluid tutFluid;
// and before blocks are initialized:
tutFluid = new TutFluid();

Now on to the block. I will not cover how it's initialized as it's the same as any other block.
Just make sure it's after the respective fluid is initialized.

public class BlockTutFluid extends BlockFluidClassic {
public BlockTutFluid(int Id) {
super(id, ModTutorial.tutFluid, Material.water);
ModTutorial.tutFluid.setBlockID(id); // Set the fluids block ID to this block.
}

// Use Register Icon as usual to get the block's icon.
// If you want you can reuse the water texture and change the color of it by doing as I have below:
@Override
@SideOnly(Side.CLIENT)
public Icon getIcon(int side, int meta) {
return Block.waterMoving.getIcon(side, meta);
}

@Override
public int colorMultiplier(IBlockAccess iblockaccess, int x, int y, int z)
{
return 0x66FF00; // HEX color code as indicated by the 0x infront. This is a greenish color.
}

That's it! You should now have a working fluid block!
If you want to be able to use a bucket to pick up the fluid keep reading.

Okay let's start by creating an item which will act as our bucket item, this will be the filled bucket.
If the player uses an empty bucket on our fluid we want him to get a bucket full of that fluid, and that's the item we are creating now.

So create a class which extends ItemFluidContainer, the super constructor wants the itemID.
No need to show you that code, the interesting part is the onItemRightClick method.
You need to override that and inside it do the following (code based upon ItemBucket):
[spoiler]

MovingObjectPosition movingobjectposition = this.getMovingObjectPositionFromPlayer(world, player, true);

if (movingobjectposition == null)
{
return item;
}
else
{
FillBucketEvent event = new FillBucketEvent(player, item, world, movingobjectposition);
if (MinecraftForge.EVENT_BUS.post(event))
{
return item;
}

if (event.getResult() == Event.Result.ALLOW)
{
if (player.capabilities.isCreativeMode)
{
return item;
}

if (--item.stackSize <= 0)
{
return event.result;
}

if (!player.inventory.addItemStackToInventory(event.result))
{
player.dropPlayerItem(event.result);
}

return item;
}

if (movingobjectposition.typeOfHit == EnumMovingObjectType.TILE)
{
int x = movingobjectposition.blockX;
int y = movingobjectposition.blockY;
int z = movingobjectposition.blockZ;

if (!world.canMineBlock(player, x, y, z))
{
return item;
}


if (movingobjectposition.sideHit == 0)
{
--y;
}

if (movingobjectposition.sideHit == 1)
{
++y;
}

if (movingobjectposition.sideHit == 2)
{
--z;
}

if (movingobjectposition.sideHit == 3)
{
++z;
}

if (movingobjectposition.sideHit == 4)
{
--x;
}

if (movingobjectposition.sideHit == 5)
{
++x;
}

if (!player.canPlayerEdit(x, y, z, movingobjectposition.sideHit, item))
{
return item;
}

if (this.tryPlaceContainedLiquid(world, x, y, z) && !player.capabilities.isCreativeMode)
{
return new ItemStack(Item.bucketEmpty);
}

}

return item;

[spoiler]

This checks if you can place the fluid at that location and if you can then it places the fluid there and repalces the item with an empty bucket.
If you are using you're own empty fluid container then return it here instead.

If you are using a different item than the empty bucket to pickup the fluid you will have to modify the onRightClick method for that item.
It's of course possible to use the same item for the empty and full container, it shouldn't be hard for you to figure it out if you want to.
But if you are going to use the regular empty bucket then read on

So for the bucket to work we need to know when the player is using the bucket on our fluid.
NB: This means using events, if you aren't familiar with events go read up on them before you continue as this tutorial does NOT cover events.
That means we will need to listen for a bucket event like this:

@ForgeSubscribe(priority = EventPriority.NORMAL)
public void FillBucket(FillBucketEvent event) {
ItemStack result = attemptFill(event.world, event.target);
if (result != null) {
event.result = result;
event.setResult(Result.ALLOW);
}
}

private ItemStack attemptFill( World world, MovingObjectPosition p )
{
int id = world.getBlockId( p.blockX, p.blockY, p.blockZ );

if ( id == ModTutorial.tutorialFluidBlock.blockID )
{
if ( world.getBlockMetadata( p.blockX, p.blockY, p.blockZ ) == 0 ) // Check that it is a source block
{
world.setBlock( p.blockX, p.blockY, p.blockZ, 0 ); // Remove the fluid block

return new ItemStack( ModItems.bucketTutFluid ); // Return the filled bucked item here.
}
}

return null;
}

That's it, we now have our very own fluid!
You can of course custemize it however you would like! you could for example make it hurt on contact(by using onEntityCollidedWithBlock) or whatever you'd like.
[/spoiler]




That's it for now folks!
I hope you found some useful information within my posts
Here's something I want to share with you, a Java cheat sheet like the eclipse one above.
It can be a nice sheet to look at when you are unfamiliar with Java's basic syntax
Dream in Code - Java Cheat Sheet

Using the information from This post(linked earlier in this thread) and This page, I found the changes needed to update textures from 1.5 to 1.5.1.

For items change:

public void func_94581_a(IconRegister iconRegister)
{
iconIndex = iconRegister.func_94245_a("%MODNAME%:%FILENAME%");
}

to

public void updateIcons(IconRegister iconRegister)
{
iconIndex = iconRegister.registerIcon("%MODNAME%:%FILENAME%");
}

For Blocks change:

public void func_94332_a(IconRegister iconRegister)
{
this.field_94336_cN= iconRegister.field_94245_a("%MODNAME%:%FILENAME%");
}

to

public void registerIcons(IconRegister iconRegister)
{
this.blockIcon= iconRegister.registerIcon("%MODNAME%:%FILENAME%");
}

and textures still go in
src/minecraft/mods/%MODNAME%/textures/items/%FILENAME%.png
or
src/minecraft/mods/%MODNAME%/textures/blocks/%FILENAME%.png