Minecraft Forums

Quote from 11Slimeade11»

Same here. You're the third person with this problem now. Hopefully a new version should fix it

Sorry for the long delay!
This one is hard to track down, because I can't get it to crash on my computer. I've never seen a Minecraft bug that only affected certain computers, but Gl8marlon said getting a new computer solved it.
Were you ever able to spawn penguins in 1.7.10q, or did the problem start as soon as you installed this version?
Are you running it on a server with multiple people connecting?

v1.7.10q
18 August
For a full description of each penguin species and all the other features of this mod, including armor, weapons, and crafting recipes, go to the Rancraft Penguins Wiki, developed and primarily maintained by randalpik.

Thanks to:
CaveJohnson212 for translating to Russian
alex212058 for translating to Chinese (traditional characters)

Rancraft Penguins adds seventeen different species of penguins to your world:

• Emperor Penguins
• King Penguins
• Yellow-Eyed Penguins
• Magellanic Penguins
• Galápagos Penguins
• African Penguins
• Chinstrap Penguins
• Gentoo Penguins
• Macaroni Penguins <= new
• Humboldt Penguins
• Adélie Penguins
• Rockhopper Penguins <= new
• White-Flippered Penguins
• Little Blue Penguins
• Flame Penguins
• Ninja Penguins
• Butt Penguins

The configuration file

A few facts about Rancraft Penguins

1. They can be tamed and bred

2. Penguin armor and weapons
Rancraft Penguins adds four enchantable weapons and several types of armor with special characteristics (swim speed, air use, etc.). The most powerful of the penguin weapons is the Flame Penguin Repeater, which shoots regular arrows and is fully automatic, although the Penguin Katana and Shurikens have their "good points" as well.

3. A good seed for Ice Plains (and also Ice Plains Spikes!)
Many of the penguins are coastal, but four species (Emperor, King, Chinstrap, and Ninja) only spawn in frozen biomes. In Minecraft 1.7.2, using the seed "derp" will spawn you in an Ice Plains biome. If you travel 260 blocks west along the coastline, you will find the rare Ice Plains Spikes biome.

Demo videos

TheDiamondMinecart (Most Famous)

ThePenguinGamer (Most Scientifically Rigorous)

Cool Girl (Most Adorable)

More Demo Videos

Installing Penguins

Downloads

Penguin Banner

Just updated to 1.7.10 and added two new species. Woot!

Quote from Snowman183

The Human spawn egg don't work with rancraft penguins I spawn a Little Blue Penguin. How to fix? Please answer soon!

CloneCraft is an amazing mod, and I especially love the laboratory procedures. In the 1.6.4 version there's a bug in how entity IDs are assigned, though, which can cause conflicts with entities from other mods (not just Rancraft Penguins). I'll PM Jamezo97 with more info.

Okay, after some more experiments, it turns out my first idea was right: it is a conflict between the client thread and the server thread. The issue is this: When you declare this function in your mod code:

public boolean onTickInGame(float var1, Minecraft var2){
...
/* do some stuff, including setAir(300) */
...
}

...that only gets run by the client thread. Meanwhile, the server has its own variable keeping track of the player's air level, and that's decreasing as usual. Here's one way to access the server's version of setAir() from the client. It's probably not the most elegant way, but it works. Put this code after the code that calls setAir(300) in onTickInGame:

String curUser = ModLoader.getMinecraftInstance().getIntegratedServer().getAllUsernames()[0];
ModLoader.getMinecraftInstance().getIntegratedServer().getConfigurationManager().getPlayerForUsername(curUser).setAir(300);

Notice that in the sample code I just grabbed the first user (getAllUsernames[0]). That's just a simple demo to show that it works with single player not open to LAN. To do it right, you'll have to check each username you get from getAllUsernames() to see if they're underwater and wearing the helmet.

I got underwater breathing to work in 1.2.5 by doing the same thing you're trying (calling setAir(300) when the player is wearing the helmet underwater). To get it to work on the server too, I created a data packet with the current air level and sent it from the client to the server with ModLoaderMp.sendPacket every few ticks. Then I had the server call its own setAir() whenever it received the packet, so that it wouldn't keep contradicting the client.
With 1.3.2, my old code acts the same way yours does -- flashing between full bubbles and decreasing bubbles, except now it's doing that on single player. (My old code still works fine with the traditional client & server.)

At first I thought the reason was the new design where even in single player the client is also running a server thread, and for some reason, calling setAir(300) only affects one thread, so in the other one it keeps decreasing. That's not necessarily the case, though. What I do know is that right after I call setAir(300), getAir() returns 300, but that value somehow gets reverted a bit later, so that the next call to decreaseAirSupply() starts where getAir() had been, not at 300. So the question is, where is that old value coming from?

Quote from Aquilamo

I don't know if somebody mentioned it (I'm not going to reading all 11 forum pages XD), but could you make an option to tame penguins using fishes from other mods? I use Aquaculture, since it make fishing more fun, but it;s a shame I can't feed it to my penguins. Maybe the possibility to write the ID of the fish item in the config file?

Do you know the item ID for Aquaculture fish? It would be pretty simple for us to hard-code it as an alternative penguin food for this release, and then maybe introduce a config file for more flexibility later.

Quote from Emopeng

can you update rancraft penguins for minecraft 1.3.1 please

We're working on it. Still trying to get a few new features working right though.

Just updated to 1.2.5, with three new penguin species, spawn eggs, and penguin breeding. Woot!

Okay, here's a solution:
Someone named Noppes resolved a negative array size exception from ModloaderMP Server, but the fix works for our problem, too. Noppes posted improved source code for Packet230ModLoader.java, and also a link to a new version of ModloaderMP Server in case you just want to drop in the class.
Here's the post.
Noppes deserves some reps for this!

Their plan is to conquer the world by infiltrating the highest levels of government:

My second tutorial: Armor texture rendering.

Okay so, with the past couple updates of forge, they have fixed armor rendering with textures.

Let's begin.

Step 1:
Go to your ItemArmor.class or whatever it's called for you.

The way I did it was by adding a String to the constructor.

public class RioVArmor extends ItemArmor
{
public String armorNamePrefix;
public EnumArmorMaterial material;

public RioVArmor(int par1, EnumArmorMaterial par2EnumArmorMaterial, int par3, int par4, String armornamePrefix)
{
super(par1, par2EnumArmorMaterial, par3, par4);
this.material = par2EnumArmorMaterial;
par2EnumArmorMaterial.getDamageReductionAmount(par4);
this.setMaxDamage(par2EnumArmorMaterial.getDurability(par4));
this.maxStackSize = 1;
this.setCreativeTab(TheMistsOfRioV.tab);
armorNamePrefix = armornamePrefix;
}

public String getArmorTexture(ItemStack stack, Entity entity, int slot, int layer)
    {
if (stack.toString().contains("leggings")) 
{
return "RioV:" + armorNamePrefix + "_2.png";
}
if (stack.toString().contains("Leggings")) 
{
return "RioV:" + armorNamePrefix + "_2.png";
}
return "RioV:" + armorNamePrefix + "_1.png";
}

Which means my item declaration looks like this:

public static Item amethystHelmet = new RioVArmor(2000, AmethystArmorMaterial(your armor material), "amethyst").setUnlocalizedName("blahblahblah");

Now, let's go back to the getAmorTexture method in our armor class.

Ever since 1.6.1 getArmorTextureFile has changed to getArmorTexture with a few more variables.

I set my texture directory as RioV:(armorNamePrefix)_1.png/_2.png

The stack.toString().contains("Leggings") means if the unlocalizedName has leggings and/or Leggings in it, it will use the amethyst_2.png to render the leggings as normal.

The texture directory will be in mcp/src/minecraft/assets/riov/(armor pngs) as RioV: is my modID which means in the texture directory, RioV will be lowercase.

I tried to make this sound not as confusing as possible. I hope this helped.

Quote from Shaqaruden

EDIT: ok I tried putting the item declarations in the Load function and separating them from the LanguageRegistry,GameRegistry and Recipes in a function called something(to test) and then called that function within the Load function and now I get this...

and in the console is is saying all the items are missing

Keep the load and preInit as they were before.
Move the item declarations to preInit.
It works for me.

Requires Minecraft Forge version 7.7.1.632+

The Forge BiomeDictionary contains a set of tools that make it easier to support modded biomes in mods that add biome specific world gen, or mobs. It does this by assigning tags to biomes (such as FOREST) based on their properties (temperature, height, number of trees, etc.). This tutorial will cover how to register biomes you've created, manually, how to check if a biome has specific tags (for world generation), or get a list of all biomes with a specific tag (for mobs). I will assume that you already know how create a biome, a world generator, or a mob, depending on which section of the tutorial you're interested in.

Imports

To use BiomeDictionary, you must import the following:

import net.minecraftforge.common.BiomeDictionary; //Alternatively: import net.minecraftforge.common.*;
import static net.minecraftforge.common.BiomeDictionary.Type;

You should already understand what the first line does if you're at all familiar with Java, however, the second line may need some explanation. import static allows you to import a specific public field in a class in such a way that you can reference it directly, without referring to the class that contains it. In this case, we are using an import static on the enum which contains the different tags defined by BiomeDictionary. This will make your code look a lot cleaner, as it will allow us to say something like "Type.FOREST", instead of "BiomeDictionary.Type.FOREST". I'm not going to get into the details of how Java enums work in this tutorial, as it shouldn't be necessary for you to fully understand then to use BiomeDictionary. If you're interested in learning more about them, a quick google search should bring up relevant information.

How To Register a Biome Manually

You should first of all note that BiomeDictionary can automatically register a biome when a mod requests information on it using a pre-defined rule system (see BiomeDictionary.makeBestGuess() for details). However, in some cases, particularly unusual biomes will not be classified correctly, and you should register them manually. This is very simple to do:

BiomeGenBase theBiome = new BiomeGenSpecial(theBiomeID);
GameRegistry.addBiome(theBiome);
BiomeDictionary.registerBiomeType(theBiome, Type.MOUNTAIN, Type.WASTELAND);

You should already be familiar with the first two lines, which are just creating and registering the biome using FML. The third line is registering the biome in BiomeDictionary with two tags, MOUNTAIN, and WASTELAND. The first parameter of BiomeDictionary.registerBiomeType the BiomeGenBase instance representing the biome you wish to register, and all subsequent parameters (you can give as many as you want) are of type BiomeDictionary.Type, and these are the types you want to register the biome as. For maximum compatibility with mob mods, you should do this within your mod's load() method. It's also very important that you register your biome with BiomeDictionary after you've registered it with FML, as BiomeDictionary requires that a biome is in the master biome list in BiomeGenBase before it can be registered with BiomeDictionary.

For reference, here's the enum that defines all the biome types:

public enum Type
{
	 FOREST,
	 PLAINS,
	 MOUNTAIN,
	 HILLS,
	 SWAMP,
	 WATER,
	 DESERT,
	 FROZEN,
	 JUNGLE,
	 WASTELAND,
	 BEACH,
	 NETHER,
	 END,
	 MUSHROOM,
	 MAGICAL;
}

Of these tags, HILLS, WASTELAND, BEACH, NETHER, END, MUSHROOM, and MAGICAL, will never be automatically assigned to a biome, so if one of these applies to your biome, you should manually register it. It should also be noted, that if a biome is registered manually with any tag, automatic registration will not be attempted, so if you do register manually, you must register it will all relevant tags. Finally, you should never register vanilla biomes, as BiomeDictionary has automatic manual registrations for all of them.

How To Use BiomeDictionary for World Generation

Being able to restrict world generation based on biome, yet still support all biome mods without a huge amount of extra work is the reason BiomeDictionary was written in the first place. As a few amazing mods such as Forestry have done, you could look at the properties of the biome yourself, however, this is difficult if you don't know a huge amount about biomes, and most people tend to just support vanilla biomes for that reason. BiomeDictionary takes care of all of that for you, and you just have to ask it if the biome you're trying to generate in has specific tags applied to it. When you request information about a biome, if it has not already been registered with BiomeDictionary, BiomeDictionary will automatically classify it for you. Because this only has to happen once per biome, it isn't very costly at all to do this at world generation time.

I'm going to assume in this section that you already have a world generator (class that implements FML's IWorldGenerator) that you wish to apply this to, and already know the basics of adding world generation.

You should have a method that looks something like this:

@Override
public void generate(Random random, int chunkX, int chunkZ, World world,
IChunkProvider chunkGenerator, IChunkProvider chunkProvider)
{
    //World generation code
}

The first thing you have to do is get the x and z coordinates of some block in the chunk you're generating in. The easiest way to do this is:

int x = chunkX * 16;
int z = chunkZ * 16;

This will give you the coordinates of the block at x = 0, z = 0, relative to the chunk.
Now, you need to get the biome at that position:

BiomeGenBase biome = world.getWorldChunkManager().getBiomeGenAt(x, z);

And finally, you'll need to check to see if the biome is of the type you want to generate in:

if(BiomeDictionary.isBiomeOfType(biome, Type.FOREST))
{
    //World generation code
}

The code in the true branch of that if statement will only execute if that biome is of type FOREST. Keep in mind that biomes can have multiple types, so if you want, you can use &&, ||, and ! to check for any combination you want. For instance, you may want to check if a biome is not FROZEN, is both FOREST and MOUNTAIN, or is either SWAMP or WASTELAND. For a complete listing of the available tags, see either the previous section, or BiomeDictionary.Type

To summarize, here's the final code for this method:

@Override
public void generate(Random random, int chunkX, int chunkZ, World world,
IChunkProvider chunkGenerator, IChunkProvider chunkProvider)
{
    int x = chunkX * 16;
    int z = chunkZ * 16;

    BiomeGenBase biome = world.getWorldChunkManager().getBiomeGenAt(x, z);

    if(BiomeDictionary.isBiomeOfType(biome, Type.FOREST))
    {
	    //World generation code
    }
}

And that's all you have to do. It's just as easy as restricting your world generation based on a vanilla biome, but using BiomeDictionary will make your world generation compatible with any biome mod your users might install. Plus you'll find that the tags available are very similar to the vanilla biomes.

Mob Spawning Using BiomeDictionary

First of all, I want to apologize if anything I say in this section isn't quite correct. I'm not as familiar with how mob spawning works as I am with world generation and biomes, so please feel free to correct me if I make a mistake.

As with world generation, BiomeDictionary will make it much easier to support all biome mods when adding mobs that have their spawn restricted by biome. In this tutorial, I assume that you already have a mob, and know the basics of how to register it to spawn in a specific biome.

First of all, while you can do any initialization of your mobs in your mod's load() method, actually using BiomeDictionary to register them for biomes that have a specific tag applied to them must be done in your mod's postInit() method. This is to ensure that all biomes have already been registered in the master biome list using FML.

The first thing you have to do within postInit() is add the following line of code

BiomeDictionary.registerAllBiomes();

This method only needs to be called once within postInit() (and shouldn't be called anywhere else in your code). All it does is loop through the master biome list in BiomeGenBase, and automatically register any biomes that were not manually registered with BiomeDictionary by their creators. Even if your mod is not the first to call it, you don't have to worry, as the method will just loop through all the biomes, and not do anything if the method has already been called. Since there are a maximum of 256 biomes, this isn't going to be that costly while the game is loading.

Now that you've done that, you want to get a list of all the biomes that have the tag you're interested in applied to them. You do this as follows:

BiomeGenBase[] biomes = BiomeDictionary.getBiomesForType(Type.FROZEN);

At this point, you can simply loop through the list and register your mobs to spawn in that biome as you normally would.

SpawnListEntry ocelotSpawn = new SpawnListEntry(EntityOcelot.class, 2, 1, 1);

for(int i = 0; i < biomes.length; i++)
{
    biomes[i].getSpawnableList(EnumCreatureType.monster).add(ocelotSpawn);
}

This example adds vanilla ocelots to all biomes registered as FROZEN. However, there are a few problems. First of all, what if you want to spawn the mob only in biomes that are both FROZEN and FOREST. Easy:

SpawnListEntry ocelotSpawn = new SpawnListEntry(EntityOcelot.class, 2, 1, 1);

for(int i = 0; i < biomes.length; i++)
{
    if(BiomeDictionary.isBiomeOfType(biomes[i], Type.FOREST))
    {
	    biomes[i].getSpawnableList(EnumCreatureType.monster).add(ocelotSpawn);
    }
}

As I explained in the world generation section, you can use BiomeDictionary.isBiomeOfType() to check if an individual biome has a specific tag applied to it. You can of course, use &&, ||, and ! to create any combination you want. If you want to add it to biomes of one tag, or another, you should check before adding to the second tag (and any subsequent tags) to make sure it does not also have the first tag applied to it to avoid duplicate entries.

To see the full list of available tags, either look in the section on manual biome registration, or look at BiomeDictionary.Type.

Feel free to ask any questions, or point out any mistakes I've made.