Brock Lievsay
- Brlievsay
- brlievsay
- America/Chicago
- Yes
- No
MC-121478![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
When a Phantom is summoned from a command block with specified NBT data, the phantom will fly straight at the direction 45.0 (Southwest) unless you are able to "disturb" the phantom and then which he will attack you if you are in survival/adventure mode.
When the Phantom is summoned without NBT tags, the Phantom will nose into the ground, like normal (due to
the established bug that causes that.)How to Reproduce:
in a command block:/summon phantom ~ ~1 ~ {CustomName:"{\"text\":\"hawk\"}",Invulnerable:1}Compare with a phantom without the NBT data.
This is probably related to MC125252
When a Phantom is summoned from a command block with specified NBT data, the phantom will fly straight at the direction 45.0 (Southwest) unless you are able to "disturb" the phantom and then which he will attack you if you are in survival/adventure mode.When the Phantom is summoned without NBT tags, the Phantom will nose into the ground, like normal (due to MC125252)
How to Reproduce:
in a command block:/summon phantom ~ ~1 ~ {CustomName:"{\"text\":\"hawk\"}",Invulnerable:1}Compare with a phantom without the NBT data.
Holy mother of Salmon!! I enabled doMobSpawning when the story is completed and on my test run, the waterways are absolutely overrun with schools of salmon. There are so many, that it is causing a considerable fps drop when near the water. (looks like Silvermist has her work cut out for her)
Not sure if this is already posted, I searched, but couldn't find a clearly labeled issue about this.
Holy mother of Salmon!! I enabled doMobSpawning when the story is completed and on my test run, the waterways are absolutely overrun with schools of salmon. There are so many, that it is causing a considerable fps drop when near the water. (looks like Silvermist has her work cut out for her)
Not sure if this is already posted, I searched, but couldn't find a clearly labeled issue about this.
Edit: Look at the total number of entities, around 1,000
Lightrecalculation errors when converting world from 18w16a or earlierLighting anomalies when converting world from 18w16a or earlier
I just tried out 18w22c today and seem to be having major issues with block lighting.
I first noticed it on my server (was an 18w14b world). I added a roof to the top of a wastewater screening/liftpump building and the lighting on the floor remained at 15, even with the room sealed off( no half slabs). This persisted until I lowered the level of the floor down around 10 blocks to reach the sewer depth. Very strangely, digging a block or two out sideways from the below grade room, and light could be found again. (There is an aeration basin at surface level next to the building though since water seems to be causing some anomalies)
I also noticed the city water line tunnels, which is normally as dark as it can get, had abrupt patches of complete light.
Next is my 18w16a map: Almost no shadows in the forests composed of big trees, and I mean big as in custom built tree models painted there with world painter. I sealed myself inside a tree, and same story, It is completely lit.
I just tried out 18w22c today and seem to be having major issues with block lighting.
I first noticed it on my server (was an 18w14b world). I added a roof to the top of a wastewater screening/liftpump building and the lighting on the floor remained at 15, even with the room sealed off( no half slabs). This persisted until I lowered the level of the floor down around 10 blocks to reach the sewer depth. Very strangely, digging a block or two out sideways from the below grade room, and light could be found again. (There is an aeration basin at surface level next to the building though since water seems to be causing some anomalies)
I also noticed the city water line tunnels, which is normally as dark as it can get, had abrupt patches of complete light.
Next is my 18w16a map: Almost no shadows in the forests composed of big trees, and I mean big as in custom built tree models painted there with world painter. I sealed myself inside a tree, and same story, It is completely lit.
Edit: The blocks themselves are giving off level 15 light. This is almost like using the applyblocklighting filter in mcedit, except it's everywhere and without choice.
Also effects custom models for the stairs I know. For me, It's like only the up faces are lighted properly, and since the sides of my models don't extend to the side of the block, they are dark as well
I'm getting this crash report, when I load a copy of a particular 18w05a world of mine in 18w07a. I suspect This too, is related to something invalid in the datapack. I generated a new world in 18w05a and loaded it just fine in 18w07a, to eliminate a few possibilities.
The Customizable features are not supported as of yet. This was also the case in 18w06a, I believe. It will work later on.
I've been trying to figure this one out, and I think I may know the cause finally through some experimentation.
This occurs (for me anyway) whenever I have a world with an endless water border.
How to recreate:
1. Open up World Painter and create a quick world.
2. In the World export options, under world border, select water and select endless. (I also normally have the map's water height at 20, and the type should switch to a Superflat world)
3. Export the world, and attempt to load in 18w07b
4. Check the launcher log and crash report when the game hangs on "Loading World". You will need to exit the game via the task manager.
Other worlds created will still work fine, if they don't have an endless superflat border. Maybe some borders might work, but not the settings I've been using.
Seems to be working alright now in 18w10a or b with the new phantom behavior.
The color among the whole game is off for me. I want to say many blocks look like they are in 8 bit color, stone looks like concrete, redstone blocks are more like orangestone blocks, and the menu UI looks terrible. The tunnel vision effect in less light is not blurred at all.
another possible fix I'm about to test out of curiosity just in case they don't fix it to load 18w16a worlds: load your 18w16a world in 18w15a. I did so on a copy of my map, and thus far, I do not see anything missing or broken ( at least for the blocks that are in my map anyways) . I will check the whole map, travel the entire map, to resave all chunks and attempt to load the world in 18w19b. I'll update when I've tested this out.
Edit: Pretty promising results! only one area that must not have gotten saved in 18w15a or for whatever reason didn't load in 18w19b. Way way way better than what I got when I originally loaded the 18w16a world in 18w19b
This is the only area of missing chunks that I've found with a brief search.
I remember flying very fast over this area, faster than minecraft could load the chunks at times.
Its probable that minecraft didn't load these chunks in time. But honestly, If this is all I'm missing, It would be pretty easy to /fill it back in since it was water anyways. I should try manually updating those chunks in 18w15a again and see if it changes anything with those chunks.
@Linda A. Wingfield Hmm.. that's strange. I just tried again with my world, and I cannot see any missing chunks at all in my map. Is your world type default or something? My world type is a superflat ocean world with custom terrain that I painted in world painter back in 1.11.2, in which the world size is 266 MB (It's a huge land mass). Keep in mind that minecraft only rewrites chunks of the world that have been loaded in game. Basically when I loaded my world in 18w15a, I set my render distance to 16 chunks and flew across the map back and forth working my way north with an elytra with the goal to have minecraft load every chunk in my world, which did the trick for me. On my second attempt, I manually placed a few blocks in the chunks that didn't load on my first attempt of conversion just in case. They are there now. Don't know if the world type has anything to do with this though. I think I might generate a new 18w16a default type world, blow some craters, and see if I can get it to load in 18w19b
Hey Everyone, I know how to fix the resetting inventory/position issue!
First, back up your world, (obviously)
Open your world in NBT Explorer
Go to the level.dat -> Data ->
And delete the entire "Player" Compound tag that you will see.
Your inventory and position will now stay changed the next time you log in!
It looks like the new format that 18w19 is using solely the external playerdata folder in the saves now, and having the outdated Player compound tag in the level.dat causes the playerdata data to be overwritten with the outdated data that is in the level.dat
You may wish to make a backup of the level.dat just in case they decide to use it again.
Yeah, It looks like my work around still works in default world types, but just not as well..(Unless I just got lucky with my superflat map) It took me a few tries to get all of the built chunks in a default world type to convert. Basically I hovered/ flew over everything once in 18w15a, and then made a copy of that save. Loaded the copy in 18w19b and made note of what chunks have been reset. I then went back into the original reverted save and revisited the noted chunks with special emphasis. Upon loading a new copy of that in 19b, The revisited chunks have always been there. Repeat as many times as necessary. Or, to guarantee your chunk to convert, place a block and break it or use a command block or function to do this for you faster.
I was just testing the waters of upgrading my world to pre3 from 18w16a, which is the most previous, somewhat stable snapshot. MC 129725 seems to not be effecting my world in pre 3, even though it has never been marked as fixed, but my command/ function central computer was absolutely going haywire! (It's a high tech command based adventure map all controlled by a central computer room.
With some investigation I have stumbled upon this being the cause of the problem. Everywhere I use /execute if entity @a[then whatever here] to use as a /testfor is always testing positive. Guess I'll stick with 18w16a until the official release. This would be a huge setback for me if it makes it into the final release. Sure hope they fix this! Voted.
I just tried a copy of my 18w16a world in 1.13 pre 3, and I have not noticed this issue anywhere in my map thus far. I was having this issue in 1.13 pre1 in almost every block when I tried that release so maybe it's fixed? That or there is something special with my world.
It is so strange that some people are still experiencing this issue, Hmm.. My 18w16a world works perfectly after being updated to 1.13. Don't know what would cause a difference with some worlds vs others, perhaps world type or generator options maybe?
I'm having an issue with structure blocks freezing my singleplayer and multiplayer worlds just for loading a structure of the maximum size.
Basically almost everything quits working (mobs, chunk loading, etc). Even tested on my own personal server, and I timed out and could not reconnect for like a minute until the server finally caught back up.
edit: hmm, It almost seems like it may be because the structures might not be up to date. I last updated them just after the flattening in the snapshots. Once I manage to load a particular one, loading it again is much more normal.