Minecraft Forums

Got an orange and a cherry, from Pam's Harvestcraft.

Two and a half years ago, Peyton and Steelfeathers came up with a brilliant idea: a competition to see who could make the best 'simple' pack. Nine months ago, Peyton remade the challenge as the Simple Pack Showdown 2. Now I'm bringing it back for the summer, with iteration number three of this wonderful competition.

Challenge:

Within the time limit specified in the rules, create a 1.8 compatible texture pack in the simplistic style using one of the palettes submitted by your fellow competitors below.

What is a simple pack, you ask? It is quite simply a pack that uses color, line, shape, and design to flesh out beautiful textures. It does not rely on filters or detailed shading, and it does not attempt to look realistic. A simple pack is NOT, however, a collection of bucket fill textures or plain squares with outlines. For visual explanation:

Rules:

1. Take a palette, Leave a palette -- Before beginning your entry, submit an original color palette. You will then be able to choose from among the palettes already submitted to use for your entry. But you cannot choose your own palette. (Multiple people can choose the same palette)

2. You must use the palette you choose! No combining palettes or adding colors. Once you declare your choice, you're stuck with it. :]

3. If you absolutely MUST use a different palette, you must start your entry again from scratch!

4. Any resolution allowed, but simple style only. This means no realistic or ultra detailed textures. The most important things to keep in mind are color and stylization.

5. All textures must be your own original work, and must be created for this competition. You can revamp an old pack of yours if you choose, but do not simply copy and paste preexisting textures.

6. The following blocks are to be completed (at minimum):

• Stone blocks (smooth stone, ores, cobble, etc)
• Tree blocks (logs, planks, leaves)
• Common natural blocks (dirt, sand, gravel, etc)
• Crafting blocks (crafting table, furnace)
• Nether blocks (netherrack, soul sand, etc)

7. The current deadline is Friday, July 31. Voting will begin that day, and end on Saturday, August 8.

8. All entries submitted must include the palette being used and at least 3 in-game screenshots.

Palettes:

They still look good either way. xD

And I decided to take you up on the swirls challenge, Bluberry.

So I decided to go in a different direction, after realizing how much my computer hates the default resolution with mods. Yay, 8x pack!

Quote from Cozzmy13»

Well, I'm still at high school, so I have plenty of time to do ****, right now I'm thinking of a project for the summer, a game of some kind, but it's pretty hard to get something started.

Should we get back to texturing?

If you're thinking about making a game, I'd check out the Unity engine. It uses C++, and makes it pretty easy to get started with game development. And yeah, we probably should get back to texturing. Umm... I have things!

Quote from Cozzmy13»

You won't get anywhere with the "sound hard" attitude, just make small steps, C++ is the easier one, but you will make only console programs if you don't want to learn some GUI libraries(Qt and GTK come to mind). C# is the more complicated one, but you will have a graphical editor for your GUI.

Also, you won't actually be able to find a working place only by knowing those, there are a lot of mediocre programmers at the queue, so, yeah.

I actually find C# to be much easier than C++. Part of that is needing to know libraries to make GUIs in C++; QT is evil and should never see the light of day in a modern environment. Or at the very least no one should have to learn it in a week while also writing code for an Arduino. They key thing to note is the fact that C++ can be written in literally any IDE (even Notepad if you're particularly masochistic), whereas C# absolutely requires Visual Studio. Which, if you don't get a student discount (and aren't okay with piracy), can be majorly expensive if you want the good versions.

A good thing to do when learning a language for the first time is to take a well-commented program, recompile the code, and then dissect it to figure out how it works. You can pick up a lot of things that everyone does but no one really explains how to do like that, which is hugely helpful when you're trying to condense your code or even debug something that you've already written. And Stack Overflow is one of the best resources, along with cplusplus if you're writing C or C++.

And I can definitely attest to not being able to find a job only knowing a couple languages. I've got C, C++, C#, Java, Assembly, HTML, CSS, Javascript, ASP.NET, JSP, PHP, jQuery, and SQL and I'm still having issues finding jobs. Because for some reason, hobby development and school projects don't count as experience, so I need to get a programming job to have experience to get a programming job.

Quote from Neilex

Peggle should have some screens here http://forum.feed-th...rce-pack.28795/

The tiling errors and terrible colour choice... They hurt my eyes! D=

DEADLINE NOW CHANGED TO OCTOBER 6, 2013!

If you regularly visit the TAU thread, you'll know that there's a new multipurpose palette loose on the internet. It is known as the DB32 Palette, named after its creator over on PixelJoint -- DawnBringer. It's meant to be a general-use palette for, well, anything. And we're going to put it to use in Minecraft textures.



That is your palette. Your goal is to create a texture pack (just the block files, not items) by the end of the summer. That means the deadline is October 6, 2013. Any resolution is accepted, as is any style (including non-pixel art). There are different rules for different styles, obviously. There will also be a separate judging, which means there will be two winners.

Pixel Art Challenge

• Any resolution accepted (16x, 32x, 64x, etc)
• Odd resolutions are fine (10x, 22x, etc)
• All work MUST be pixel art (No brushes may be used. Same with smudge, burn, etc.)
• Only the colours in the palette may be used
• Transparent colours may be used for ice and glass
• Biome colours are fine, as long as the colours on the template use this palette

Non-Pixel Art Challenge

• Any resolution accepted (16x, 32x, 64x, etc)
• Odd resolutions are fine (10x, 22x, etc)
• Any combination of pixel art and brushes is allowed
• The only colours allowed to be specifically selected are the ones in the palette. Midtones may not be selected and used anywhere else.
• Transparent colours may be used
• Biome colours are fine, as long as the colours on the template use this palette

Both Challenges

• Only the blocks folder is needed for judging, but the entire pack will be judged. This means ctm, items, mobs, everything.
• Judging will be done by public vote
• The prize will be a cute little icon, made using the palette colours, to stick in your signature
• A pack without the entire blocks folder can still be judged, but the mixing textures need to be specified
• The end date may be pushed back by popular demand, though two and a half months should be a decent timeline
• All textures must be made specifically for this challenge. No recycling packs.
• To submit your pack for judging, one image containing all block textures is required, along with two screenshots. Each additional component (ctm, items, mobs) will require another image showcasing that component as a whole, as well as another screenshot.

Have fun!

Some cute 8x apples! =D



And zoomed:

Bluebird 3.8! What's new?

• Less clutter in the file, and a few textures I forgot to add last time

Old versions (In case any of you need them.)
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

Q: When can we expect the 2016 update?

A: Soon. Hopefully.

Q:Why did you start a continuation?
A: I spent 2 years of my life on this pack. My heart and soul went into this, and people loved it. My thinking was that just because I don't play the game and don't want to work on the pack anymore others should not be unable to play with it. People were disinterested however, and it didn't take off.

Q: Can use textures/edits from this pack in my own?
A: Sure. I'd prefer if you asked me first though.

Q: Can I use this pack in my adventure map?
A: Yes, just link back here for the download so I can keep track.

Q: Can I make a video of this pack?
A: Yes, and please send me the video if you do so I can feature it here

Want to help support the pack? Put this banner in your signature, or wherever else you want it!

Hello Internet, It's me Max and I have recently finished my realistic overhaul of the default lighting.

This resource pack adds nothing to the default textures other than edit the lightmap. The whole point of this resource pack is to make the game look more realistic with a shaders-ish effect. If you are familiar with some of my other resource packs, you may recognize these effects in my "Naturus" resource pack. I originally edited this lightmap for that pack, however, this pack separates the lighting effects from the rest of the features in Naturus, making it compatible with almost every other resource pack. Anyway, I hope you enjoy it and feedback is always appreciated. And as always, It would be great if somebody was to do a video review of this pack, It would mean a lot to me

DOWNLOADS:

- Vanilla Lighting Overhaul --> http://adf.ly/1G32bh

- Vanilla Lighting Overhaul (bright) --> http://adf.ly/1G32gd NOTE: You still need to have your brightness on moody it's just it will seem more bright

FEATURES:

- Yellow Sunlight

- Orange torch/lava/glowstone etc. glow

- Orange/yellow sunset

- Darker Nights

- Darker Caves

- Darker End Dimension

- More red/flamey Nether Dimension

REQUIREMENTS:

- Brightness MUST be set to moody or nothing will work

- You MUST be using Optifine or nothing will work

- It is strongly recommended that you keep smooth lighting on at least minimum for the full effect

COMBINING WITH OTHER PACKS:

One of the great things about this pack, is that it can be combined with almost any other resource pack. Doing this is very simple. You must turn on both the resource packs at once, making sure that my resource pack is on top. If you have any problems, feel free to contact me via private message or simply posting to this thread.

SCREENSHOTS:

BEFORE:

AFTER:

BEFORE:

AFTER:

BEFORE:

AFTER:

BEFORE:

AFTER:

BEFORE:

AFTER:

IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII

It took me over a month to make this, it only takes 1 second for you to click the like button. Think about it.

IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII

General Useful Information:
Here are the block ID's so you don't have to count each time you want to create a new .properties file.




CTM[/anchor]
CTM: Connected Textures Mod

This feature is great because it allows you to customize what blocks of the same type look like when they are adjacent to one another in a variety of ways.


There are currently SEVEN (7) methods in which you can implement CTM into your texture pack. These methods are:

- CTM (The Original)
- Vertical
- Horizontal
- Top
- Random
- Repeat
- Fixed




Directions to use:
1. You will need to open up your texture pack folder/zip file.

2. Create a folder inside the texture pack zip/folder called "ctm" and open that up.

3. Create the following new .png files* based upon which methods you are using. IMPORTANT: Make the images the same size as your terrain.png or they will not work properly.
verticalctm.png
hortizontalctm.png
randomctm.png
repeatctm.png
topctm.png
originalctm.png


*They don't HAVE to be named like this but I recommend it for sake of simplicity and uniformity across texture packs.

4. Create .properties files using notepad (more info specific to each method below!)
You no longer have to name them block<n>.properties or terrain<n>.properties, but if you do not follow this convention, you must specify block IDs or tile numbers inside the .properties file instead.

All property names are case-sensitive.



General properties used by all methods:

(Required) Name of source texture. This can be anywhere in your texture pack and multiple .properties files can share the same source (with different tile numbers).

source=<path of png within texture pack>

(Required) Method to use when choosing a block's replacement texture:
ctm: Standard 8-way method (glass in the original CTM).
horizontal: Connect to blocks on left and right only (bookshelves).
vertical: Connect to blocks above and below only (columns)
top: Connect to block above only (sandstone).
random: Pick a tile at random.
repeat: Repeat a fixed pattern over large areas.
fixed: Use a single fixed tile. Equivalent to random with only one tile.

method=<ctm | horizontal | vertical | top | random | repeat | fixed>

(Required for some methods) List of tiles to use. Remember that tiles are indexed from left to right, top to bottom starting at 0 with 16 per row. See image at top of page. Syntax is a list of tiles or tile ranges. The following are equivalent:
tiles=4-6 8-10
tiles=4 5 6 8 9 10

tiles=<list of tiles between 0 and 255>

(Optional) Connect type. For methods that connect to adjacent blocks, specify how the game should decide if two blocks should be connected.
block: Connect if block id of this block = block id of neighbor.
tile: Connect if tile texture of this block = tile of neighbor.

The default is block for /ctm/block<id>.properties and tile for/ctm/terrain<tile>.properties.

connect=<block | tile>

(Optional) Faces. Limit the mod to only certain faces of the block.
bottom: Bottom face (negative y).
top: Top face (positive y).
north: North face (negative z).
south: South face (positive z).
east: East face (positive x).
west: West face (negative x).
sides: Shorthand for north south east west.
all: All sides.
NOTE: This property is ignored on non-standard blocks.

faces=<combination of: north south east west top bottom sides all>

(Optional) Metadata. Limit the mod to only blocks with certain metadata values. Uses the same syntax as the "tiles" property and can be any list of values between 0 and 31.

metadata=<list of values between 0 and 31>

(Optional)List of block and/or tile IDs this method should apply to.
Multiple .properties file can refer to the same block/tile and they will be processed in alphabetical order by filename. All tile-based entries are checked before block ID-based ones. The first match wins.

blockIDs=<list of block IDs 0-4095>
tileIDs=<list of tiles in terrain.png 0-255>

These two properties can be omitted if they can be inferred from the filename instead:

/ctm/block<id>.properties assumes
blockIDs=<id>
tileIDs=
/ctm/terrain<tile>.properties assumes
blockIDs=
tileIDs=<tile>

unless you specify them explicitly.

(Optional)Render pass. Specifies the render pass during which the new texture should be used.

0: Normal, solid block rendering pass. Virtually all blocks use this pass. Only on/off transparency is supported.
1: Existing translucent blocks (water, ice, etc.). With MCPatcher, two new rendering passes are available:
2: Same as pass #0 but with backface culling disabled. Use this to render all six faces of the glass block frame.
3: Extra pass with full alpha support. Will be hidden when rendered behind water, etc., from pass #1. The blending method can be changed in

/renderpass.properties.
renderPass=0

NOTE: Due to renderer limitations, specifying a renderPass requires block ID-based ctm (either by naming the file /ctm/block<nnn>.properties or using blockIDs=... instead of tileIDs=...), not tile number-based.

The rendering passes happen in this order: 0, 2, 1, 3

To make colored glass, you need two sets of tiles: one for the frame and another for the overlay. Here is an example, assuming the first four rows of the image are the frame and the second four are the overlay:

/ctm/block20.properties:
source=/ctm/myglass.png
method=ctm
tiles=0-11 16-27 32-43 48-59
renderPass=2

/ctm/block20a.properties:
source=/ctm/myglass.png
method=ctm
tiles=64-75 80-91 96-107 112-123
renderPass=3

/ctm/block102.properties:
source=/ctm/myglass.png
method=ctm
tiles=0-11 16-27 32-43 48-59

/ctm/block102a.properties:
source=/ctm/myglass.png
method=ctm
tiles=64-75 80-91 96-107 112-123
renderPass=3

NOTE: We use renderPass=2 for the glass block frame (block 20) but not the glass pane (block 102). This is because the glass pane is rendered with 0 thickness which causes Z-fighting unless the back face is culled. So the default render pass of 0 is actually best.




****************************************
Let's take a closer look at each method.


CTM (The Original)

This one is the most difficult to create but the most useful of all the CTM methods. It lets you have the most versatility for how blocks appear when placed near others of the same kind.

method=ctm
source=<source png>

(Optional) List of tiles to use, must be exactly 48 tiles. The default is the upper left 12x4 area:

tiles=0-11 16-27 32-43 48-59

How to connect each texture:
Each arrow denotes where the tile needs to be seamless in order to tile right.




Vertical

One of the most common uses for this is to create columns out of stone slabs.
The order of the textures needs to be as follows:

How it looks in verticalctm.png:

method=vertical
source=<source png>

(Required) List of tiles to use, must be exactly 4 tiles. There is no default; you must specify a list here.

tiles=<list of tiles>

example .properties file:

source=/ctm/verticalctm.png
method=vertical
tiles=0-3

Horizontal

method=horizontal
source=<source png>

(Optional) List of tiles to use, must be exactly 4 tiles. The default is the rightmost 4 tiles on the first row. [For sake of left-to-right, I made the example .properties file be the first four tiles (in the top left) on the first row.]

tiles=<list of tiles>

example .properties file:

source=/ctm/horizontalctm.png
method=horizontal
tiles=0-3

Top

method=top
source=<source png>

(Optional) Only one tile is needed.

tiles=<tile #>

example .properties file:

source=/ctm/topctm.png
method=top
tiles=0

Random

This is perhaps the most common type used. This is extraordinarily useful because it allows the game to select from multiple textures for the same block. This can be used to add variations to any texture*, especially ores, flowers, and wildgrass.

method=random
source=<source png>

(Required) List of tiles to choose from. There is no default; you must specify a list here.

tiles=<list of tiles>

(Optional) List of weights to apply to the random choice. For example, if you have

tiles=6-11
weights=10 1 10 2 7 3

then tiles 6 and 8 will have a weight of 10, 7 will have a weight of 1, etc.
Weights do not have to total 100 or any other particular value. In the above example, tiles 6 and 8 will be used ~30.3% (10/(10+1+10+2+7+3)) of the time and so forth.

weights=<same-size list of weights>

(Optional) Desired level of symmetry for the faces of each block. Applies to standard blocks only.
none: All 6 faces are textured independently. This is the default.
opposite: 2-way symmetry; opposing faces have the same texture, but each pair can potentially have a different texture.
all: All 6 faces have the same texture.

symmetry=<none | opposite | all>

*except sidegrass. This feature seems to not work properly.


Example .png file: (ignore the sidegrass; as I said, it doesn't work properly)
In this example .png, you can see that there are multiple variations of each ore, logs, etc.


Example .properties file:

source=/ctm/randomctm.png
method=random
tiles=32-34

Repeat

This method is great. It allows you to take a pattern larger than your resolution and tile it. For example, you can take a 128x128 stone texture and make it tile in your 16x texture pack. This will tile 8 blocks x 8 blocks, giving much room for increased variation.

method=repeat
source=<source png>

(Required) Width of the repeating pattern.

width=<width of pattern>

(Required) Height of the repeating pattern.

height=<height of pattern>

(Required) List of exactly width * height tiles. You do not have to arrange them in a rectangle, but doing so makes things easier to see how the pattern will look in-game. The total area cannot exceed 256 tiles, but a 20x12 pattern is permissible.

tiles=<list of width * height tiles>

(Optional) Desired level of symmetry for the faces of each block. Applies to standard blocks only.
none: All 6 faces are textured so that the pattern tiling looks the same from
all sides. This is the default.
opposite: 2-way symmetry; opposing faces have the same texture, which means
that tiling on the south and east faces will be mirrored left-to-right from
compared to the north and west faces.

symmetry=<none | opposite>

Example images:



Example .properties file (for the sand example used above)

source=/ctm/repeatctm.png
method=repeat
width=8
height=8
tiles= 8-15 24-31 40-47 56-63 72-79 88-95 104-111 120-127

-----SPECIAL APPLICATIONS-----
I know many of you may want to do dirt and grass this way. However, it looks horrible unless you make your sidegrass use the same method. Here is my example of how to do it right:


Grass texture:

Sidegrass texture:

Dirt texture:


You are going to use the following filenames for the .properties files.

terrain0.properties

source=/ctm/repeatctm.png
method=repeat
width=8
height=8
tiles= 136-143 152-159 168-175 184-191 200-207 216-223 232-239 248-255

terrain2.properties

source=/ctm/repeatctm.png
method=repeat
width=8
height=8
tiles= 0-7 16-23 32-39 48-55 64-71 80-87 96-103 112-119

terrain3.properties

source=/ctm/repeatctm2.png
method=repeat
width=8
height=1
tiles= 0-7

Fixed
Use a single fixed tile. Works much like random but with only one tile.

method=fixed
source=<source png>
# (Required) Single tile to use.
tiles=<single tile>

Better Skies[/anchor]

Better Skies is a much-desired addition to the game for many texture artists. This allows you to change what the sky looks like to suit your pack.


1. You will need to open up your texture pack folder/zip file.

2. Locate the FOLDER inside the texture pack zip/folder called "terrain" and open that up.

3. Create a new folder (inside the terrain folder) called sky0

4. Create a new .png file called sky0 inside the sky0 folder. Make sure the dimensions are 3x by 2x, where x is the resolution of your texture pack.
To get the correct tiling, follow the guide images below, making sure each number is matched up with the appropriate connecting side in the appropriate rotation.





5. Create a new file called sky0.properties (to do this, open up notepad and make sure to save it as a .properties file)

Each file represents one layer of sky. MCPatcher will continue loading them until a .properties file is not found. The order is the order in which they will be rendered in game. NOTE: The "sky0" folder in the path refers to the overworld. If there were other worlds with skies (the Nether and End do not use the standard sky rendering methods), they would be in /terrain/sky<world number>. You only need to provide values for the properties you wish to change. (This is not common.) The default Minecraft values for each property are given below for convenience. Property names are case-sensitive.

Here are the different properties you can include in the .properties file:


(Optional) Name of source texture. This can be anywhere in your texture pack and multiple .properties files can share the same source. If not specified /terrain/sky0/sky<n>.png is used, but I recommend including the path.

source=<path of png within texture pack>

(Required) Fade in/out times. All times are in hh:mm [24-hour format]
For reference:
Sunrise = 6:00 = /time set 0
Noon = 12:00 = /time set 6000
Sunset = 18:00 = /time set 12000
Midnight = 0:00 = /time set 18000

The fade times control the brightness when blending.
between startFadeIn and endFadeIn: 0 up to 1
between endFadeIn and startFadeOut: always 1
between startFadeOut and endFadeOut: 1 down to 0
between endFadeOut and startFadeIn: always 0
(Note that you do not need to specify startFadeOut; its value is uniquely determined by the other three.)

startFadeIn=hh:mm
endFadeIn=hh:mm
endFadeOut=hh:mm

(Optional) Blending method. Here "previous" can refer to the default sky or to the previous custom sky defined by sky<n-1>.properties. Supported blending methods are
add: Add this sky bitmap to the previous.
subtract:
multiply: Multiply the previous RGBA values by the RGBA values in the current bitmap.
dodge:
burn:
screen:
replace: Replace the previous entirely with the current bitmap. There is no gradual fading with this method; if brightness computed from the fade times is > 0, the full pixel value is used.

(The default method is add.)

blend=add

(Optional) Rotation. Whether or not the bitmap should rotate with the time of day. (The default is true.)

rotate=true

example sky0.properties:

source=/terrain/sky0/sky0.png
startFadeIn=18:00
endFadeIn=18:45
endFadeOut=06:20

I have noticed that in order to make a second sky work and have it fade well you should use the "screen" method of blending. Here is an example sky1.properties

source=/terrain/sky0/sky1.png
blend=screen
startFadeIn=06:00
endFadeIn=06:45
endFadeOut=18:45

6. You can have an infinite number of "skies" in the sky0 folder. To add more, simply create additional .png and .properties files with the names sky1, sky2, etc. and repeat steps 4 and 5.





Custom Colors[/anchor]
There is a lot you can do with the custom colors mod: change the colors of light, fog, custom biome colorings, etc.

INDEX:
File list
Base water particle (splashes, bubbles, drops) color.
Nether and End colors
Lilypad color
Colors for each potion effect
Spawner Egg colors
Map colors
Sheep colors
Text colors
Custom Biome palettes




Below is a full list of files used by the Custom Colors mod:

/color.properties
/misc/redstonecolor.png - 16x1 redstone colors (0=fully off, 15=fully on)
/misc/stemcolor.png - 8x1 pumpkin/melon stem colors (0=sprout, 7=fully grown)
/misc/lavadropcolor.png - Nx1 lava drop colors (x=age of particle in ticks)
/misc/myceliumparticlecolor.png - any size, random mycelium particle colors
/misc/xporbcolor.png - any size, array of xp orb colors
/misc/swampgrasscolor.png - 256x256 swamp grass color palette
/misc/swampfoliagecolor.png - 256x256 swamp foliage color palette
/misc/pinecolor.png - 256x256 pine tree color palette
/misc/birchcolor.png - 256x256 birch tree color palette
/misc/watercolorX.png - 256x256 water color palette
/misc/underwatercolor.png - 256x256 underwater color
/misc/fogcolor0.png - 256x256 fog color for the overworld
/misc/skycolor0.png - 256x256 sky color for the overworld
/environment/lightmap0.png - Nx32 overworld lighting palettes
/environment/lightmap-1.png - Nx32 Nether lighting palettes
/environment/lightmap1.png - Nx32 End lighting palettes

To begin:

1. You will need to open up your texture pack folder/zip file.
2. Create a new .properties file called color.properties




You only need to provide values for the properties you wish to change. The default Minecraft values for each property are given below for convenience. Property names are case-sensitive. All colors are in hex color format, 000000 to ffffff.
Convert from RGB to HEX

Base water particle (splashes, bubbles, drops) color.
Biome water color multiplier is applied to this value. The value should match the color of your base water texture. If your base water texture is grey so that you do coloring via /misc/watercolorX.png, you should set this to ffffff.

particle.water=334cff

Base portal particle color: a random multiplier between 0.4 and 1.0 is applied to all three r/g/b values.

particle.portal=ff4ce5

Nether and End colors:

fog.nether=330707
fog.end=131318
sky.end=181818

Lilypad color:
This is a single color that is used across all biomes.

lilypad=208030

Colors for each potion effect:

Final color is the average of these colors weighted by level of each potion effect.

potion.blindness=1f1f23
potion.confusion=551d4a
potion.damageBoost=932423
potion.digSlowDown=4a4217
potion.digSpeed=d9c043
potion.fireResistance=e49a3a
potion.harm=430a09
potion.heal=f82423
potion.hunger=587653
potion.invisibility=7f8392
potion.jump=786297
potion.moveSlowdown=5a6c81
potion.moveSpeed=7cafc6
potion.nightVision=1f1fa1
potion.poison=4e9331
potion.regeneration=cd5cab
potion.resistance=99453a
potion.waterBreathing=2e5299
potion.weakness=484d48

potion.water represents a plain bottle of water

potion.water=385dc6

Spawner Egg colors:

egg.shell.Creeper=0da70b
egg.spots.Creeper=000000
egg.shell.Skeleton=c1c1c1
egg.spots.Skeleton=494949
egg.shell.Spider=342d27
egg.spots.Spider=a80e0e
egg.shell.Zombie=044975
egg.spots.Zombie=799c65
egg.shell.Slime=51a03e
egg.spots.Slime=7ebf6e
egg.shell.Ghast=f9f9f9
egg.spots.Ghast=bcbcbc
egg.shell.PigZombie=ea9393
egg.spots.PigZombie=4c7129
egg.shell.Enderman=161616
egg.spots.Enderman=000000
egg.shell.CaveSpider=0c424e
egg.spots.CaveSpider=a80e0e
egg.shell.Silverfish=6e6e6e
egg.spots.Silverfish=303030
egg.shell.Blaze=f6b201
egg.spots.Blaze=fff87e
egg.shell.LavaSlime=340000
egg.spots.LavaSlime=fcfc00
egg.shell.Pig=f0a5a2
egg.spots.Pig=db635f
egg.shell.Sheep=e7e7e7
egg.spots.Sheep=ffb5b5
egg.shell.Cow=443626
egg.spots.Cow=a1a1a1
egg.shell.Chicken=a1a1a1
egg.spots.Chicken=ff0000
egg.shell.Squid=223b4d
egg.spots.Squid=708899
egg.shell.Wolf=d7d3d3
egg.spots.Wolf=ceaf96
egg.shell.MushroomCow=a00f10
egg.spots.MushroomCow=b7b7b7
egg.shell.Ozelot=efde7d
egg.spots.Ozelot=564434
egg.shell.Villager=563c33
egg.spots.Villager=bd8b72

Map colors:

map.air=000000
map.grass=7fb238
map.sand=f7e9a3
map.cloth=a7a7a7
map.tnt=ff0000
map.ice=a0a0ff
map.iron=a7a7a7
map.foliage=007c00
map.snow=ffffff
map.clay=a4a8b8
map.dirt=b76a2f
map.stone=707070
map.water=4040ff
map.wood=685332

Sheep colors:

sheep.white=ffffff
sheep.orange=f2b233
sheep.magenta=e57fd8
sheep.lightBlue=99b2f2
sheep.yellow=e5e533
sheep.lime=7fcc19
sheep.pink=f2b2cc
sheep.gray=4c4c4c
sheep.silver=999999
sheep.cyan=4c99b2
sheep.purple=b266e5
sheep.blue=3366cc
sheep.brown=7f664c
sheep.green=667f33
sheep.red=cc4c4c
sheep.black=191919

Text colors:

color of exp level text

text.xpbar=80ff20

color of "Boss Health" text

text.boss=ff00ff

color of sign text

text.sign=000000

color codes generated by \247 + 0123456789abcdef

text.code.0=000000
text.code.1=0000aa
text.code.2=00aa00
text.code.3=00aaaa
text.code.4=aa0000
text.code.5=aa00aa
text.code.6=ffaa00
text.code.7=aaaaaa
text.code.8=555555
text.code.9=5555ff
text.code.10=55ff55
text.code.11=55ffff
text.code.12=ff5555
text.code.13=ff55ff
text.code.14=ffff55
text.code.15=ffffff
text.code.16=000000
text.code.17=00002a
text.code.18=002a00
text.code.19=002a2a
text.code.20=2a0000
text.code.21=2a002a
text.code.22=2a2a00
text.code.23=2a2a2a
text.code.24=151515
text.code.25=15153f
text.code.26=153f15
text.code.27=153f3f
text.code.28=3f1515
text.code.29=3f153f
text.code.30=3f3f15
text.code.31=3f3f3f

Custom Biome palettes:

You may assign custom biome palettes to any standard block (i.e. one that does not already have its own special color multiplier method). The syntax for this in color.properties is

palette.block.<image in texture pack>=<list of block IDs>

The image must exist in your texture pack and must be 256x256. For example, to color all stone and ore blocks with /misc/stonecolor.png

palette.block./misc/stonecolor.png=1 14 15 16 21 56 73 74

Block ID + metadata is also supported using the following syntax:

palette.block./misc/sandstone.png=24 43:1 44:1

Custom Animations[/anchor]
This is very handy. It allows you to create animated textures, items, etc. It is common to animate torches and furnaces.

It is important to note that unless otherwise specified, animations do NOT support partial transparency.

INDEX:
How to Assemble an Animation
Water Animations
Lava Animations
Portal Animation
Fire Animations
Custom Terrain Animations
Custom Item Animations

1. You will need to open up your texture pack folder/zip file.

2. Create a new folder called anim

3. Create a new .png file using the naming pattern described below inside the anim folder. Make it x pixels wide (x is the resolution of your pack). The height doesn't matter so long as it is divisible by x. Each image should be a vertical strip of separate frames.

Custom animations are read from these files, all in the anim/ folder of the texture pack .zip/folder

How to Assemble an Animation:

1. Begin by first creating your base texture (don't forget to check for tiling errors). For my example I will use this water texture I created:


2. Animate the texture.
There are many ways to animate a texture and most of them have a specific use or purpose. For low-resolution textures (32x or lower) the easiest method is to copy the base image, move it down to the next frame, edit it slightly, copy the edited texture, move it to the next frame and repeat. For HD textures (64x and up) the easiest method to use is to apply animation filters to the texture. In GIMP and Photoshop there are a variety of filters you can use, so find which ones suit your style.



When animating a texture with a filter, it will create a multi-layer image. This image will not be read by minecraft so you need to:
3. Copy each frame to the tall image. It is easiest to set a grid up with snap-to's with the grid being x by x pixels, where x is the resolution of the texture.
4. Make sure to lower the opacity to the desired setting, otherwise you will not be able to see through the texture. (mostly for water and portal animations)
5. For FLOWING lava/water animations, simply scale the image's height by one frame. NOTE: the height has to be divisible by the texture's resolution




Water Animations:

This animation supports partial transparency.


files:
custom_water_still.png
custom_water_flowing.png


example .png's (without the opacity lowered):



Lava Animations:

files:
custom_lava_still.png
custom_lava_flowing.png

example .png's:


Portal Animation:

This animation supports partial transparency.

file:
custom_portal.png

example .png:


Fire Animations:

This animation supports partial transparency*

files:
custom_fire_n_s.png
custom_fire_e_w.png
(this is the hardest animation, in my opinion.)

*The screen overlay for when you are on fire is rendered from the above files tiled twice across the bottom of the screen, and it supports partial transparency. However, the fire on blocks, while rendered from the same files, does NOT support partial transparency, EXCEPT in the Nether. I would expect to see this fixed at some point.


example .png's (without opacity lowered):



Custom Terrain Animations:
You can create an animation for any tile in terrain.png. ### is the tile index (0-255), not a block or item ID (see image at top of page)

This has a wide variety of applications, notably torch and furnace animations.


files:
custom_terrain_###.png

example .png:



Custom Item Animations:

You can create an animation for any tile in items.png. ### is the tile index (0-255), not a block or item ID

files:
custom_item_###.png


=============================================
Each custom animation may also specify its animation speed and frame order. Create a text file with the same name as the animation but change .png to .properties. In the file, make a series of entries

tile.X=Y
duration.X=Z

X starts at 0 and represents the order you want frames to display in. Y is the tile number in the animation .png file. The first tile is 0, the second is 1, etc. Z is the duration you want that frame displayed, in game ticks (if omitted, duration is assumed to be 1 for that frame). For example, to make an animation with 3 tiles, run on a 5-frame animation with a pause in the middle, the .properties file might look like this:

tile.0=0
tile.1=1
tile.2=2
duration.2=5
tile.3=1
tile.4=0

You may create a custom animation for any texture in the game. Create a .properties file in the anim/ folder of your texture pack. In it, supply the source and destination texture, along with coordinates of the area you wish to animate. The following example animates the first painting in kz.png.

from=/anim/mypainting.png
to=/art/kz.png
x=0
y=0
w=16
h=16

"from" is the location of your custom animation. "to" is the texture you wish to animate. "x, y, w, h" are the coordinates of the rectangular area of that texture. The width of the "from" texture should be equal to the value of "w"; if not, it will be scaled automatically. You can have many different animations applied to the same texture by creating separate properties files for each. The properties file can also contain tile order and speed information as described above.




Random Mobs
-coming soon-




HD Fonts
-coming soon-




Better Glass

(Optional)Blending method for render pass 3. This will be applied to all blocks using that rendering pass.
alpha: Normal alpha-based blending. This is the default.
overlay: Overlay blending based on color. RGB values > 0.5 brighten the color behind it, < 0.5 darkens, and 0.5 is neutral.

blend.3=alpha

(Optional)Whether to enable lighting on textures drawn during render pass 3.
Particularly for overlay blending, this may not be desirable. The default is true for alpha blending and false for overlay blending.

enableLightmap.3=true

ALL EXAMPLES ARE MADE BY DRFROZENFIRE (except the Original CTM image). MOST ARE TAKEN FROM THE SYNTHETIC REALITY 256X TEXTURE PACK.
Any images used herein are copyrighted and licensed to Drfrozenfire. Permission to use these images must be granted by Drfrozenfire.

I want Steelfeathers to make another challenge.

5 colors per block hardcore pixel art all the way

Quote from Flop_Penguin

Stop crying about it and go make your own texture pack! Or don't download the copied ones!!

Your logic is that there is nothing wrong with stealing. Therefore, I can assume you don't mind being robbed. You can save us all a lot of trouble if you just go ahead and give me everything you own.

I know some of you know this by now, but you CAN have the Beta 1.7.3 terrain in 1.0.0+! All you need is a cureent Minecraft Version Changer, or a Minecraft Version Changer that updates itself after every patch release, OR you can have a back-up Beta 1.7.3 .jar file to switch back and forth with the current Minecraft patch. What I did was when I made a map in Beta 1.7.3 earlier today, I put a single block of cobblestone on the very spot I spawned on to mark my original spawn point. I made a map in which I filled up every single pixel starting with on my spawn point from the middle to the very edges and in between. Once I had that map filled, which is more than 1,000 blocks from the spawn point in every direction, so I literally had I'll say at LEAST 10,000 blocks of Beta 1.7.3 terrain I'm guessing?

Anyways, While I was filling up the map, I didn't look up or anything so next time I go exploring, I don't know what's there like mountains because I didn't see where I was going, just looking straight down at the map while travelling to fill it up. Then I head back to my home which is near my original spawn point. Then I switched to 1.0.0 since these pre-releases for 1.0.1 really have nothing to offer for me so far. I wasn't underground at all when I was in Beta 1.7.3, so maybe there's a chance that there'll be undergound ravines here and there and if so, maybe a slight chance there'll be a stronghold, all below the Beta 1.7.3 terrain generation. Of course, I'll keep going on in Beta 1.7.3 to make another map with more Beta 1.7.3 terrain generation and still have all the 1.0.0 stuff. Of course, only in 1 direction I'll let 1.0.0 terrain generate so as to have plenty of ravines, a few Strongholds, a few NPC villages and if very lucky, a mushroom biome!

One more thing! If you dolike I did, you'll want to put the game on "Peaceful Mode" because it does take around a few Minecraft days and nights to fill it up, especially if you keep hitting roadblocks! :tongue.gif: There was a LOT more generation to record on a map than I thought. I spent around 45 minutes filling it up literally! And I'm sure a lot of you can do it in less that time too! :tongue.gif: Well, that's I have to say!

Today, one of my friends in real life was getting called all sorts of names by some racists in my town, when I got home I decided I was in the mood for some pixel art in MineCraft, with the racism being the furthest thing from my mind. I Googled for pictures for a few minutes and came across a picture with a bear or something in it. It was very pixelated, but it had multiple layers and was at an angle. I went into Paint and remade the bear pixel by pixel and added my own flare into it. I thought that since it was part blue and part red that I'd make another one with the colours flipped. Once I looked at it I realized that the bears could be holding hands so I nudged them next to eachother and did that too. I looked back at my color pallet and realized I could do six more bears (probably even more than that) so I made those too. I looked at the picture in Paint and thought about how the bears were different, but they were still holding hands and smiling.

I wanted to work the phrase "Color doesn't matter as long as your hearts are in the same place.", but I am bad with letters in MineCraft and I didn't think there would be nearly enough space.


Paint-

MineCraft-

---

Thoughts on my thoughts or just on the picture being a picture?