Minecraft Forums

Thank you.

I seem to have encountered a bug. Not quite sure if it's a bug, so I'm posting here before it goes to the bug tracker.

In the new snapshots, in addition to a spherical selection area, you can select a cubical area! That's awesome. However, in the newest snapshot, it doesn't seem to work correctly. This is the command I used.

testfor @a[x=100,y=60,z=100,dx=110,dy=70,dz=110]

I'd expect this to search a 10x10x10 area, but the search area is much larger than that. The first set of coordinates are correct, but the second set, no matter what it is, is invalid. In the world I found this in, the coordinates for the second coordinate were the same.

Can anyone else replicate this? Am I doing it wrong?

I know it's a snapshot, so I don't expect everything to be all shiny and polished and clean, but I just can't try things out due to what's happening.

For me, all the 1.8 snapshots have a very slow update speed. Things like TNT, redstone, mobs, other players, beacon effects, movement, and anything else that communicates with the server or internal singleplayer server are not working correctly. I've tried using the bug reporter, but I couldn't quite get out what I needed to say. I believe the server updates things according to a timer referred to by "tick," and if that's the case, then the tick is way off. A redstone pulse takes about 4 seconds to update, beacons take 12 seconds to cycle through, tnt takes a loooong time to actually blow up, chat is so slow that tabbing with commands doesn't work, movement is impeded every now and then if you run into a block, etc.

All of the features in the snapshot sound great to me, and I know they're just development progress checks, but this has been a problem for me in every 1.8 snapshot so far. Is there something I'm missing? Are my drivers broken? Will the finished product be like this? And finally, is this just me?

Sorry for wall of text, but the new launcher puts me so close to the new snapshots, and yet I'm so far away. pls halp

I have a non-existent player that I'm using to keep scores consistent on servers. I can set the score of "player," but I cannot test for that player. For example,

/scoreboard players set fakeplayer testobjective 1234

works, but

/testfor fakeplayer[score_testobjective=1234]

does not. Using the @a selector if only fakeplayer has an entry will always turn the comparator on, no matter what the score actually is. If another player has an entry, then that player will be examined instead, as the fakeplayer is not online.

I heard of using * to select all players, but that causes massive lag for me. The new snapshot says something about using #fakeplayer to denote a fake player, but I can't figure out how it works.

Basically, I'm trying to create a variable that will work no matter who is online, as people logging in and out will produce inconsistencies in scoreboard entries. I'm trying to testfor a specific player and a specific score, even if said player is offline.

Wow, thanks for replying so quickly with a good post.

I have a room. I need to have a pulse when over 4 people are in the room, and have that pulse be off if there are less than 4 people in the room.

I thought of using scoreboard to mark each player seperately, but that's not very accurate, as people moving in and out would easily confuse the system. There's got to be something I don't know about here. I'd prefer the thing be solid state, using command blocks and whatnot.

Thanks for helping, I apologize if I've done something wrong, I'm new here.

Heyalo! I'm having problems with Optifine. My computer has been degrading in performance since october, many things have stopped working. I've been getting a lower framerate each month, but things were still okay until yesterday, after logging in to a server, nothing was visible except chests, signs, wireframes of blocks, etc. The ground looks invisible. This has shown up on all worlds until I removed Optifine. I upgraded from 1.4.5 to 1.4.6, and upgraded Optifine. I am still getting the same thing. Anyone else?