Draco18s

Functions aren't magic. They do things. There's plenty of reasons to have more than one constructor, but they're not required.

You delete the file in your local repository, push a commit, and sync. So remove the method you don't need. If they're identical, you don't need one of them. This is like having a shopping list that says: Milk Bread Milk

Yeah, do that. Your block does not override createBlockState() and yet it tries to have properties.

Complain to the mod that's crashing (biomesoplenty). This forum is for people who MAKE mods.

I've been there. My tablet doesn't know the word "do"

I'll admit I might be wrong, its been a while since I messed with it.

http://www.vogella.com/tutorials/EclipseDebugging/article.html

Quick: Name a block that emits particles

Is your texture going to be transparent? No? Use opaque. Look at where vanilla makes particles.

Or the block class...

Its an issue with z-sorting. But without giving us the model and block classes we literally can't help you. Also:

and its not xEnd, yEnd, its xWidth and yHeight.

Same goes for the UV coordinates (almost: they're actually start and size), measured from the top left corner IIRC

Packets.

Huh?

You missed the fact that my example layout was 6x5 didn't you?

Note that for programming you also need the JDK...which Minecraft does not autodownload.

I swear, you're either misrepresenting the argument on purpose in order to create strawman or you're actually not understanding it. Lets take this layout: The left side is just a mirror of the right, so I'm not bothering to draw its offsets. If we want to rotate it, we get this: Notice how two of the positions (besides the center) remain filled, even though they are different parts of the whole layout: This is because of how rotations work: they swap the X and Z values (and sometimes flip their sign). https://math.stackexchange.com/questions/1330161/how-to-rotate-points-through-90-degree In order to make what we want to happen, we treat things as relative. Instead of +2X we call it +2R. if Facing.Forward.Z is our Forward offset (moves up under no rotation) and Facing.Forward.X is our Right offset (moves right under no rotation) We'll do this process by focusing only on this blue block: In this orientation it's +1F,+2R. Lets animate that. Now lets rotate it 90 degrees. HOLY SHIT IT WORKS

No its not. Two blocks to the right? pos.offsetZ(Facing.getX() * 2).offsetX(Facing.getZ() * 2) Three blocks left and one up? pos.offsetZ(Facing.getX() * -3).offsetX(Facing.getZ() * -3).offset(Facing.UP) There's always a point from which you can perform all of these calculations and there is no rotation that this doesn't support (unless you want your machines to be constructed on their *sides* too, but even THAT functions if you do it right). It doesn't support mirroring very well, but you CAN do it. The whole even/odd things it moot too. If its an even number of blocks your "center" is just offset to the side a bit, one side extends 1 block away from "center" and the other side extends 2. I dare you to construct something that when rotated does not appear identical to a reference frame rotated the by same amount.

Not really. If you do all your offsets based on a Facing (and Facing has a getOffset method) you don't even need to think about it. "This block is 1 forward" -> pos.offsetX(Facing.getX()).offsetZ(Facing.getZ()) "This block should be one to the right" -> pos.offsetZ(Facing.getX()).offsetX(Facing.getZ()) Then you just loop over the horizontal facing values.

https://github.com/RIS-Mods/RIS-Minimap/blob/master/src/main/java/com/deerangle/render/MinimapCacher.java#L93-L94 That doesn't look right. You should use << 4 Ditto here: https://github.com/RIS-Mods/RIS-Minimap/blob/master/src/main/java/com/deerangle/render/MinimapCacher.java#L107

I did not ask for a stack trace, as the fact that your code is invoking a chunk load event was already self evident. What I want is your code.

And why do you think that?