mojira.dev

RAM

Assigned

No issues.

Reported

MC-240154 Villages created in problematic terrain Duplicate MC-225684 Trees on slopes often expose dirt Invalid MC-196456 Chains do not connect across orientations Invalid MC-190714 Feature request: Farm plot polyculture Invalid MC-175411 Banners patterns applied to shields do not respect resourcepacks Invalid MC-152042 Snow layers do not flow around flowers and plants Invalid MC-142453 Floating village components Duplicate MC-136958 Profile names ever recycled? Invalid MC-132089 Custom world creation; current custom worlds cannot be opened Duplicate MC-110134 Loading small resourcepack causes unexpected delay Invalid

Comments

Please share the "intended" part of WAI. I interpret it as "works the way it does, and we have no intention to change it."

"Works as intended" means "unintended consequence but too much work to design and implement a fix." There have always been bizarre villages, but 1.18 pushes the problem to new limits. Sad. It would be so simple to limit village generation to a reasonable ∆Y from the village center. How about a configuration option?

Apologies. I considered it a bug.

If not, several workarounds have been documented above. It took me about 30 minutes to clear the issue on my servers. YMMV.

Concur with James. I was able to identify three regions in our default world that had this issue, by looking for villages in our ServerTutorialPlus tours. After verifying that no other player content existed in those areas (they were intentionally outside the usual player areas), I deleted the relevant region and poi files and restarted the server to regenerate them. I then visited them to reestablish the tutorial points. In one of them, the terrain had been altered subtly, but otherwise the process was unproblematic. The errors no longer occur. As noted above, if you have player content in the affected areas, more nuanced decisions may need to be made.

Doh! I should have realized that. Thanks.

Oh, right. Thanks. Mea culpa.

The 1.13.2 example above is vanilla. So it just happened to work prior to 1.14.x?

Still present in 1.13 full release. Is there anything for the server operator to do to resolve it?

And (at present, at least) "BUFFET" is a misnomer. At a buffet, one can select multiple items.

"works as intended"... So is that what you are saying?

Please add that the issue continues through 1.13-pre4. And it is not resolved.

So are you explicitly saying that Custom world creation will not be available henceforth?

125172 lists only 18w06a. Please add that the issue continues through 1.13-pre4. And it is not resolved, unless you are saying that Custom world creation will not be available henceforth.

I appreciate that. However, the (admittedly ambiguous) implication was that they would be supported at some future point. If absolutely necessary, I can live without backwards compatibility. HOWEVER...

One cannot create a custom world, currently.

(IMHO: A single biome does not equal custom, so Buffet and Superflat do not qualify as custom, compared with what was available prior to 1.13.)

"... don't work in this snapshot. Sorry. We have plans to re-add them in a much more extendible way, but unfortunately we were not able to have that ready yet. You will be unable to open any world of type "customized" in this snapshot, it will tell you to revert to an old version to play in those worlds."

is hardly equivalent to "working as intended." This is still a bug, still present in 1.13-pre4.

Based on what information do you say "It will work later on" ?

Confirmed. Launcher did not update earlier, even on restart. Now on 2.0.1051, all better. Thanks.

Snapshot 18w19a
MacOS 10.13.4 (17E202)
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)

Enabling resolution no longer crashes, but it does not use the resolution settings (1708x960). Game is still 854x480.

Abd 18w16a

And 18w08b