Minecraft Forums

Tutorial for block and item textures in 1.5 http://www.minecraftforum.net/topic/1722368-15-icons-and-block-textures/

As long as it works on run mode it should work on debug mode.

Umm, this might help. http://www.minecraftforum.net/topic/1722368-15-icons-and-block-textures/

Quote from diesieben07

You misunderstand the word API. An API means: An additional thing that needs to be installed (e.g. NEI is the API for the NEI plugins, the NEI Plugins don't include NEI, but depend on it.)
An API for regular mods can be a coremod. And even without a coremod this can be done more efficently.
And your code style is weird, too. For example:
You have a Singleton pattern in your main class, but still all the methods are static, WTF?
Any IOExceptions during download are simply ignored. Not even a Warning message that something went wrong. Not a good thing.
Also you use ConcurrentHashMaps for no reason. You don't have mutliple threads.
Also you loop through every single player every tick. Why? It's enough to change the Cape URL once.

Okay, thanks for showing me my problems. It helps to have some one who knows his stuff to tell you whats wrong so you don't do it next time and learn. I loop through the players because I can't change all the URLs of the players in one swoop. So thats what is up there. The concurrent hash map was an oversight.. Another mod I maintain uses it so I didn't know if I should use it or not. What should I call it if its not technically an API? I wanted to make it so it was compiled with the mod it is serving so that people did not have to download it separately. As for the Singleton pattern, I should read up on that... Take a look now?

Quote from diesieben07

As cool as this may look, the code is horrible. It puts a lot of unnecessary strain on the Client CPU and has some very weird and badly done code.
The only way to do this properly is to become a FML Coremod, sorry.

Yes, that would be more efficient. But this is an API for regular Forge mods. So it doesn't make a whole lot of sense to do it that way.

Yeah

It looks like your cape images are not right. Use Notch's as a template. http://skins.minecraft.net/MinecraftCloaks/Notch.png

Cool, np.

I use Forge, and you need to register the model render class in the RenderingRegistry. It looks like this.

RenderingRegistry.registerEntityRenderingHandler(MyEntity.class, new RenderMyEntity());

Also, make sure your texture file is in the right place. That could be the problem too.

Quote from josh103

but jadar i am using model biped

I know but it sounds to me that there is a problem with the render. it seems like you're not registering that or something.

Okay cool, thanks.

Quote from xxAKSxx

Looks so awesome can i get permission to use this code in my OpenSource Project

the only change that i'll make(maybe) is to change the package declarations

Yep Technically you don't need to change them.

Make sure you have a model and render class for it. An that you register the render and model correctly with Modloader.

Developer Capes is used to add developer/tester only capes to your mod!

Notice: Usage changed in version 3. Please refer below to see how to set up DevCapes now.

Note: Previously called DeveloperCapesAPI, DeveloperCapes was renamed because Jadar realized he was stupid. And that this is a library.

It does all the work of adding capes while trying to minimize conflict between mods. It works by reading a JSON file that is hosted somewhere on the internet, i.e Dropbox, that contains the URL of the cape image and all the players to get that cape. Players are stored in groups and groups are given a cape. You can have as many groups as you want.

Current Version



A star on the GitHub page would be appreciated if this helps you! Also, if your mod uses this library, leave a post below saying so and I'll add it up here.

Getting Started

To start using Developer Capes, see "Set Up" below. See "Usage" below to find out how to implement the library in your mod.

Setting Up the Development Environment

1. Download source code as a zip by clicking "Download Zip" on the right.
2. Unzip to a tempory directory. You can delete this once the source is copied.
3. Copy everything in src/main/java/ to the root of your mod source code.

Usage

Once Developer Capes is in your classpath somehow, you are going to want to add this to your mod when it initialized.
*Note: The note that was previously that said DevCapes didn't have to go in a client proxy has been redacted. You need to put it in the client proxy again

DevCapes.getInstance().registerConfig($CAPES_JSON, $IDENTIFIER);

$CAPES_JSON is the URL (in Object or String form,) InputStream, or File to a text file hosted on a server, Dropbox, or GitHub, that has all the data Developer Capes needs to add your capes formatted in JSON.$IDENTIFIER is a unique mod identifier so DevCapes can keep one mod's groups separate from the other.
The JSON for the config looks like this:

"$CAPES_TXT_URL" is the URL to a text file hosted on a server, Dropbox, or GitHub that has all the players, groups, and capes in it. The layout looks like this:

{
"Group1": {
"capeUrl": "http://www.example.com/group1_cape.png",
"users": [
"JadarMC",
"MinerID642"
]
},
"Captain_Shadows": "http://www.example.com/captain_cape.png"
}

You are going to want to make sure there is a comma after every element in the array, or string, etc, -except- when it is the last one in it's scope. If you do the logs will make this very clear.

Images
The cape image files are 22x17, and should be of the PNG format. Additionally, Developer Capes supports high definition capes. Those must be of the size that is divisible by 16. The height must be half of the width. So 1024x512, 2048x1024, and so on. Host them on a server, Dropbox, or GitHub.

Standalone Mod
* Download mod JAR. Open the jar in a ZIP viewer like 7-Zip.
* Create a config file called anything you want. Guide here. Host it as plain text on the internet.
* Extract the "capesInfo.json" file from the JAR you downloaded. Open in in a text editor.
* Change the value for key "capeConfigUrl" to the URL for your config file.
* Put the file back into the JAR. Save the JAR.
* Distribute the JAR.

Building and Packaging your Mod
When you build and package your mod, you're going to want to make sure you build with the Developer Capes classes.

Thats it! If you have any trouble, make a post here in the Minecraft Forums post or make an issue on GitHub.

Example

In the end, your mod will look like this.

// Init method in main mod class
@Init
public void preInit(FMLPreInitializationEvent event) {
proxy.initCapes();
}

CommonProxy

public void initCapes()
{
}

ClientProxy

@Override
public void initCapes()
{
DevCapes.getInstance().registerConfig("html://www.example.com/cape.txt", "ExampleMod")
}

HD Capes

Thanks to MinebookUK we now have HD Cape support! To use it, just make an HD Cape. It needs to be the size of the resolution it is in. For example, the basic cape is normally 64x32, but it only uses the top left 22x17 for the cape. Increasing the total size of the image will make it work properly. So 512x256, 1024x512, 2048x1028, and so on. Here are some templates for different sizes (courtesy of MinebookUK.)

512x256.
* Put the file back into the JAR. Save the JAR.
* Distribute the JAR.

FAQ


Licence/Permissions

DeveloperCapes is licensed under the MIT License.

You may re-distribute this content but only in your mod
You may change the source code of this library.
You may re-use code found in this project.
You may not hold me liable for any damages
You must include the license and copyright with all copies of code whether compiled or not.

Updated Forge mod versions for 1.5

Quote from rickybuilder

Is this mod compatible with tje following mods?

-modloader

-Optifine

-Smartmoving

-Player API universal

-render player api

-Timber mod

-Emoticons Mod

Yes but instead of Modloader install Minecraft Forge and the MCCapes Forge mod.