Galaxy Prism
- Galaxy_Prism
- galaxy_prism
- America/Los_Angeles
- Yes
- No
typing in /particle magicCrit ~ ~ ~ 0 20 0 0 1000 normal @pisnot centeredtyping in /particle magicCrit ~ ~ ~ 0 20 0 0 1000 normal @p makes particle not centered to player
when I type in "/particle magicCrit ~ ~ ~ 0 20 0 0 1000 normal @p" (without "), it makes it so that the particle(s) is not centered to the player. Instead, it is centered to the corner of the block. Please help. This is also in Multiplayer, I dont know if this happens in singleplayer
Unknown
Multiplayer Minecraft
I don't see anything wrong with this.
Confirmed for 20w17a
It is possible that this is intended behavior:
The new transfer command intended to transfer players between servers is only able to be used by players, which, in my opinion, makes it very slightly pointless. So far, I have only tested it with command blocks and signs, but I am under the impression that itworks similarly to other server exclusive commands.It is possible that this is intended behavior:
The new transfer command intended to transfer players between servers is only able to be used by players, which, in my opinion, makes it very slightly pointless. So far, I have only tested it with command blocks and signs, but I am under the impression that it has a permission level higher than what a command block can access.
It is possible that this is intended behavior:
The new transfer command intended to transfer players between servers is only able to be used by players, which, in my opinion, makes it very slightly pointless. So far, I have only tested it with command blocks and signs, but I am under the impression that it has a permission level higher thanwhat a command block can access.It is possible that this is intended behavior:
The new transfer command intended to transfer players between servers is only able to be used by players, which, in my opinion, makes it very slightly pointless. So far, I have only tested it with command blocks and signs, but I am under the impression that it has a permission level higher than 2.
The armor texture model does not support translucency despite supporting full transparency. Does not work when using custom armor textures either. This was last supported in 1.14
,and earlier for standard armor retexturing.
When trying to do 'execute if/unless blocks x1 y1 z1 dx dy dz x2 y2 z2 all run say something', everything following 'all' is highlighted red, stating 'Incorrect argument for command at position ... all <--[HERE] '.
There are no issues when attempting to run the command; however, all autocomplete is terminated.
How it looks:
As stated, it does still properly execute, and is only an issue with the display.
@Galaxy Prism I think you should create a new ticket for this, and mention this new ticket here in a comment. If you can attach a demonstration video that would be great!










I died but nothing happened except for dropping my things. then I respawned
This has been happening to me as well
are you sure that this is a bug
Seems the new snapshot managed to fix it
...
this was still water
It says instead "[Player] has been killed by Ender Dragon using Magic"
I used numbers instead of commands, but it does this on both.
Still in 1.14.3. Is very annoying. Please fix soon.
I have seen this as a problem with at least normal overworld type worlds. Floating Island (not main end island type) worlds and superflat worlds do not seem to have a problem, but I cannot guarantee this will happen or not happen to someone else.
The problem is the dimension type. Custom dimension types have been updated, and so dimension with a custom dimension type may or may not work and if it does not work, it will "cut off" the rest of the worlds from loading (If the first dimension in your first namespace folder uses a custom dimension type, no custom dimensions will work). This indeed is not a bug, there are just some new things needed in the dimension_type file
I had a similar problem on amplified worlds, and it would only occur if blocks generated above y=255
I have found that this is a problem in 1.17.1, but it happens for me even when structures are in the world. Attempting to close the game by saving and quitting cause it to save the world for an extended period of time, and pressing alt+f4 causes the screen to go black without it actually closing
edit: And it only seems to happen when locating mansions
I had tested it with signs, yes. I was not able to make it work. The click event seemed to have a consistent permission level, even after deopping the player. Anyways, I have realized my oversight.
This may be a duplicate of or related to MC-98308