spetznack
Assigned
Reported
Comments
You can start a "listen server" from your mine craft client; start a single player world, in options/settings you should be able to find "open to LAN". Press that and your kids should find you assuming you are in the same house. If that doesn't do it there is always the awesome bukkit project you can look into 🙂
Having that said, I agree that this issue has been out there long enough now..
the .exe in 13w37a worked, then it stopped working in 13w37b. If devs looks at what changed between those two versions they could probably find it out (more) easily?
I just tried the 1.7.2 version Ezekiel posted: https://s3.amazonaws.com/Minecraft.Download/versions/1.7.2/minecraft_server.1.7.2.exe
I can confirm that the issue is still happening in this version of the .exe file. (see attachement)
[media]comment 26/10-2013 15:10
confirmed in 13w42b but only for the .exe version of the server.
The latest working version was:
13w37a
The snapshot 13w37b is the first version I could find where the .exe version of the server file does not show any console text-output and additionally the server.log is not created. I tried creating a server.log and then starting the server, but I could still not see any text in the console and the server.log file did not change.
Sorry, didn't notice it before I replied.
11,11% of the lines in my log file consists of "[SEVERE] Reached end of stream for /xx.xx.xx.xx" It clugs up the log file and is very annoying, is this message really necessary to show in the logs?
I would highly appreciate it if there was at least an option to not show it in the logfile.
Hold on, so this is not being considered as an issue? 11,11% of the lines in my log file consists of "[SEVERE] Reached end of stream for /xx.xx.xx.xx" It clugs up the log file and is very annoying, is this message really necessary to show in the logs?
I would highly appreciate it if there was at least an option to not show it in the logfile.
in other words, @a will select ALL players on the server but if you add one of those arguments for example
@a[r=50]it will only select people within that radius in that world* right?
Alright. To make it completely clear, will horses only spawn WHEN the new chunks are generated or will they spawn more than once in the same chunks when players return to the biome?
Horses that are untamed has a chance to despawn so that means you HAVE to explore new areas to find any?
BTW is this the same case with the wolfs?
That was a lot of questions but I am really interested in hearing the answers of these 🙂
Thanks in advance
A official answer for this question would be very useful for us who want to know if we have to expand the server's world-border in order to get naturally spawned horses:
Seth Hoffman @seth6984 24 May
@jeb_ ok, I suspected that and focused my attention on the plains, do they only spawn in newly generated chunks? Thanks for the reply!
Most of the time we don't want to reset the world or expand world borders, but if we have to do it in order to get the new stuff that updates gives, it would be very nice to know about it ASAP! 🙂
Just tested for 1.4.7 and 1.5, the command blocks is still selecting players cross-dimentional.
Here is the setup: http://i.imgur.com/CE0q1Zb.jpg
One person stood right next to the command block in Overworld and pressed it while I was in nether (I also tried in The End, same result).
@Ryan Leach
Sorry for not being more specific, the problem is fixed for bukkit servers now. Here is the bug-tracker:https://bukkit.atlassian.net/plugins/servlet/mobile#issue/view/BUKKIT-3515
The problem exists in vanilla 1.4.7, I will try to start a 1.5 vanilla server and test it out with someone later today..
This problem is now fixed for craftbukkit. Commandblocks only selects players in the same world that the commandblock is in. Tested it yesterday and it works 🙂
the @?(search arguments) defines where the command block will search for players.
Basicly the "@?(search arguments)" will replace itself with the player(s) it found through the search parameter.
so for example:
/spawnpoint @a(0,100,0)
will look like this if the search only chooses one player: (in this case me)
/spawnpoint spetznack
adding a dimension parameter to the /command itself will not affect the way players are chosen 😉 At least that's what sounds logical to me ^^
That is a very good idea, although we would still want it to be default at the world the command block is in right? (not super important but it would make things easier ^^)
This is not only a problem with /tp commands, it's the general @p that is not world sensitive, tested it out with @r and @a, it's the same with them aswell.. :/
How to simply replicate:
1. Requires two players
2. Make a command block at coordinate 0 100 0 in overworld
3. Type in this: /tp @p 0 120 0
4. Get 2.nd player in creative and tp him to 0 100 0 in the nether.
5. 1.st player should stand a couple blocks away from the command block and the activate it.
What will happen:
Bascily the server will search the coordinates for the closest player to the search area, no matter what world he is in.
With this exact command it will tp the 2.nd player from 0 100 0 to 0 120 0 even if the command block is in another world than the 2.nd player..
Yes, I have the exact same issue with the_end, also on bukkit servers with multiverse (which enables us to create more worlds than the original 3 vanilla worlds) we are having the same problem there. :/ For me this is a BIG PROBLEM, it makes command blocks in a adventure world teleport people from survival world!!
I agree with "Tokes" and "Ano Nym". This is something that would make programming command blocks intensely easier in some cases.
In my opinion, it would be most natural and DEFINITELY most useful for the "~" to be related to the sender (cmd block for example).
If it is a suggestion or a bug does not really matter as long as a mojangster can look into it 🙂)
@Ano Nym
I have tried to find your suggestion in /r/minecraftsuggestions but I couldn't find it, can you share us a link please? 🙂