Andrew Porter
- link_the_programmer
- link_the_programmer
- Europe/Stockholm
- Yes
- No
MC-22570
Same in Creative too(they should really add a both button).
you know how trees are very close to eachother? like 1 block away from each in most dense forests? its a pain to have to hack your way(physically) through another set of leaves when there is a clear opening 1 block wide X blocks high!
Picture 1: cant go through because the horse takes up4X2 blocks. recommend 1 width 2 high.
picture 2: cut one leaf still cant get through
picture 3:cut a second STILL CANT GET THROUGH
picture 4: cuts a third and finally gets through
it would be useless to show you in survival because the Entityhorse.class is unchanged. it would be exactly the same problem.Same in Creative too(they should really add a both button).
you know how trees are very close to each other? like 1 block away from each in most dense forests? its a pain to have to hack your way(physically) through another set of leaves when there is a clear opening 1 block wide X blocks high!
Picture 1: cant go through because the horse takes up 2X2 blocks(4 total in a cube). recommend 1 width 2 high.
picture 2: cut one leaf still cant get through
picture 3:cut a second STILL CANT GET THROUGH
picture 4: cuts a third and finally gets through
it would be useless to show you in survival because the Entityhorse.class is unchanged. it would be exactly the same problem.
when riding a horse it cant go through a 1 wide 'X' high block and requires 2 (width)blocks to go through!(narrow path)
Same in Creative too(they should really add a both button).
you know how trees are very close to each other? like 1 block away from each in most dense forests? its a pain to have to hack your way(physically) through another set of leaves when there is a clear opening 1 block wide X blocks high!
Picture 1: cant go through because the horse takes up 2X2 blocks(4 total in a cube). recommend 1 width 2 high.
picture 2: cut one leaf still cant get through
picture 3:cut a second STILL CANT GET THROUGH
picture 4: cuts a third and finally gets through
it would be useless to show you in survival because the Entityhorse.class is unchanged. it would be exactly the same problem.
a simple solution would be as is:
// where canMove() is a boolean field or something.public void inBetween() {
if (Entityhorse.getY() <= Block.getY()) {
//the can move through is just an idea of what the horse can do if it meets at this //point
canMove() = true;return canMove != null;
}
if (Entityhorse.getX() <= Block.getX()) {
canMove() = true;
return canMove() != null;
}
/* probably don't need this one */ if (Entityhorse.getZ() <= Block.getZ()) {
canMove() = true;
//end
}or something like that
Same in Creative too(they should really add a both button).
you know how trees are very close to each other? like 1 block away from each in most dense forests? its a pain to have to hack your way(physically) through another set of leaves when there is a clear opening 1 block wide X blocks high!
Picture 1: cant go through because the horse takes up 2X2 blocks(4 total in a cube). recommend 1 width 2 high.
picture 2: cut one leaf still cant get through
picture 3:cut a second STILL CANT GET THROUGH
picture 4: cuts a third and finally gets through
it would be useless to show you in survival because the Entityhorse.class is unchanged. it would be exactly the same problem.
a simple solution would be as is:
// where canMove() is a boolean field or something.public void inBetween() {
if (Entityhorse.getY() <= Block.getY()) {
//the can move through is just an idea of what the horse can do if it meets at this //point
canMove() = true;return canMove != null;
}
if (Entityhorse.getX() <= Block.getX()) {
canMove() = true;
return canMove() != null;
}
/* probably don't need this one */ if (Entityhorse.getZ() <= Block.getZ()) {
canMove() = true;
//end
}or something like that
Same in Creative too(they should really add a both button).
you know how trees are very close to each other? like 1 block away from each in most dense forests? its a pain to have to hack your way(physically) through another set of leaves when there is a clear opening 1 block wide X blocks high!
Picture 1: cant go through because the horse takes up 2X2 blocks(4 total in a cube). recommend 1 width 2 high.
picture 2: cut one leaf still cant get through
picture 3:cut a second STILL CANT GET THROUGH
picture 4: cuts a third and finally gets through
it would be useless to show you in survival because the Entityhorse.class is unchanged. it would be exactly the same problem.
a simple solution would be as is:
// where canMove() is a boolean field or something.public void inBetween() {
if (Entityhorse.getY() <= Block.getY()) {
//the can move through is just an idea of what the horse can do if it meets at this //pointcanMove() = true;
return canMove != null;
}
if (Entityhorse.getX() <= Block.getX()) {
canMove() = true;
return canMove() != null;
}
/* probably don't need this one */ if (Entityhorse.getZ() <= Block.getZ()) {
canMove() = true;
//end
}or something like that
Same in Creative too(they should really add a both button).
you know how trees are very close to each other? like 1 block away from each in most dense forests? its a pain to have to hack your way(physically) through another set of leaves when there is a clear opening 1 block wide X blocks high!
Picture 1: cant go through because the horse takes up 2X2 blocks(4 total in a cube). recommend 1 width 2 high.
picture 2: cut one leaf still cant get through
picture 3:cut a second STILL CANT GET THROUGH
picture 4: cuts a third and finally gets through
it would be useless to show you in survival because the Entityhorse.class is unchanged. it would be exactly the same problem.
a simple solution would be as is:
// where canMove() is a boolean field or something.public void inBetween() {
if (Entityhorse.getY() <= Block.getY()) {
//the can move through is just an idea of what the horse can do if it meets at this //pointcanMove() = true;
return canMove != null;
}
if (Entityhorse.getX() <= Block.getX()) {
canMove() = true;
return canMove() != null;
}
/* probably don't need this one */ if (Entityhorse.getZ() <= Block.getZ()) {
canMove() = true;
//end
}or something like that
Same in Creative too(they should really add a both button).
you know how trees are very close to each other? like 1 block away from each in most dense forests? its a pain to have to hack your way(physically) through another set of leaves when there is a clear opening 1 block wide X blocks high!
Picture 1: cant go through because the horse takes up 2X2 blocks(4 total in a cube). recommend 1 width 2 high.
picture 2: cut one leaf still cant get through
picture 3:cut a second STILL CANT GET THROUGH
picture 4: cuts a third and finally gets through
it would be useless to show you in survival because the Entityhorse.class is unchanged. it would be exactly the same problem.
a simple solution would be as is:
// where canMove() is a boolean field or something.public void inBetween() {
if (Entityhorse.getY() <= Block.getY()) {
//the can move through is just an idea of what the horse can do if it meets at this //pointcanMove() = true;
return canMove != null;
}
if (Entityhorse.getX() <= Block.getX()) {
canMove() = true;
return canMove() != null;
}
/* probably don't need this one */ if (Entityhorse.getZ() <= Block.getZ()) {
canMove() = true;
//end
}or something like that.
(csd is not generated cannot properly show you the syntax like this very well)
when you choose negative , a minor yet somewhat of a nuisance; the player's hand,when you punch, YOU FORGOT TO NEGATIZE THE OTHER HALF OF HIS HAND (hint hint); its going to stick out like a yellow apple among Granny Smiths if it isnt fixed.
EDIT: apparently the lower half of steve's arm on all the textures are affected even as seen in the 16-bit colors notice the bright blue on steves arm ? notice anything different on the bottom of his arm? in ANY of the following and future screenshots ?
when you choose negative , a minor yet somewhat of a nuisance; the player's hand,when you punch, YOU FORGOT TO NEGATIZE THE OTHER HALF OF HIS HAND (hint hint); its going to stick out like a yellow apple among Granny Smiths if it isnt fixed.
EDIT: apparently the lower half of steve's arm on all the textures are affected even as seen in the 16-bit colors notice the bright blue on steves arm ? notice anything different on the bottom of his arm? in ANY of the following and future screenshots ?
ok what the heck is going on in image 23.50.03.png now huh? its grey in a screen! at first i could at least see some green pixels. then i moved the camera around, and got this.
Hey, Jeb, this doesn't solve it. Here is some pseudo code because I care:public class Block{ public void render(){ if(!((getXOnScreen() - this.width <= 0) || (getXOnScreen() + this.width >= Minecraft.getWindow().getWidth()))){ ClassForRendering.render(this); } public void tick(){ ... render(); ... } } // You're Welcome :L *awkward moment*
Basically this is an attempt at efficient rendering, and it works well TO AN EXTENT. Checking for the actual x on screen is the top left corner (for all you non-programmers) of the image being drawn. Its a bit more complicated in 3D but still the same over all concept.Wow I just lectured a small audience in a bug tracker. Why do I waste my time debugging a game that isn't mine? (because you payed $20?)
about the image:
just look at that big, gaping hole in the bottom left. How pleasing to see the void underground. This picture turns me on. Things just got very weird.That's all folks!
just look at that big, gaping hole in the bottom left.
This happens when you don't consider the entirety of the image when rotated or not, going off the screen, and so it doesn't render correctly.
Even if there is one pixel still visible, that doesn't count as "offScreen = true".
Also before this edit, I was frustrated and my emotions poured out into this really weird bug report without the intent for rudeness.
Efficient RenderingFailEfficient Rendering Error
isnt going through the blocks on the horse a glitch? i sometimes make it a double as in an added suggestion that mojang doesnt necessarily have to do when they fix the bug, but at least its logical. just sayin'.
i think the titles vary by alot which is possibly the cause of so many duplicates and because so many people define a bug very differently than others. sigh...
I wish there was a sure way of knowing your bug has already been found instead of trying to search for it for a while just like that....
sorry
how did it happen?
and what were you doing?
are you sure this is a glitch? because i think your just trolling (BUSTED)
if your trolling, find somewhere else. I know these people (i have connections... 0_0). they are very hard workers and they dont need to deal with this. not to mention their mods here on atlassian dont need to deal with this. AND this just takes up more space which if i am correct this is probably 1 whole megabyte for a new issue. 1 megabyte more + 26,678 something more issues that mojang needs to fix or probably dupes. Not cool man, not cool.
are you sure about that!? this isnt fabricated man. it only captures what is on the screen. try punchin a cow. secondly , did you press super secret options... until it went to negative colors? (opposite colors) or is it normal textures ?
yeah, i don't know what kind of minecraft you have, but mine does indeed say snapshot 13w38c and Im punching with negative colors and the other half of his skin is not colored. also, dead exploit, mcp could decompile the game and you could make a mod to change the images instead of an image "randomizer" on a button labeled "Super Secret Settings..." . dun dun dun, next level minecraft prehack hype Kappa
you are probably one of the few, yet lucky people, to have a gaming computer. sadly, they work so fast that they can over heat. computer shuts down so that the motherboard doesnt fry from the heat (pure energy) generated by digital energy (electrical energy). all about conversion of energy. otherwise, all computers would be gaming computers because the cpus would be outrageously small (possibly even microscopic!).
that or you have an old computer and its been running for days non stop in a well insulated area and the fan cant keep up with it. turn on your air, or move it to another location in the house
your images don't show the exact frame Kumasasa. you need to focus on the frame with his hand punching. I for one don't have problems with frame perfect tricks which makes me the perfect speedrunner and the (one of) the greatest glitch performers. You don't have your bottom of the arm showing.
i just wanted to go fishing, but my line got caught on splotched brown, cows in water
notice more of the arm is noticeable in my screenshots. yours don't show the punch animation. i Probably should have made a video and linked it.
And now that i realize, Im starting to think that it isnt a glitch and that i did this for nothing
wow, it works as intended!? not to be rude, but, That just doesn't look right.and by works as intended as its supposed to latch onto the cow sure. but does it have to swing around off the cow's body like its a "fish". Because that's what it looks like to me:
public int isFish()
if (this.isEntity() && !this.isLivingEntitiy() or this.isEntity() == null) {
fishingrod.bobber.runAroundLikeCrazy(); // i think the name Mojang chose for this void is hilarious lol.
return true
}
//end
return true
wow. I made the same one and for Windows and its
MC-70313!!! I think...why can we mark a bug for something like 1.9 already when 1.8 is just being released!?
Technically, adding case-sensitivity is a way of sorting, which can be useful. Strings are case-sensitive by default. It just looks like Jeb forgot to put equalsIgnoreCase(str); and rather he put equals(str);
well then. that sucks. So much for efficiency. I have a great video card so I get high fps, except when it comes to processing when I have an AMD E1 2100 running at 1 GHz
Yeah... sorry about that. But I do know what I'm talking about. Also I "waste" my time debugging a game that isn't mine because I care. Sorry for the attitude. I feel the pain Jens and Dinnerbone and whoever else working on minecraft has right now when debugging. I had a problem when I was building this rasterizer in AWT. Took me three weeks to find an answer.
This edit should be better than the original report...
ok well I don't want this post to ruin my "rep" because of an attitude so dupe or not, it's at least better.