These have been arround since beta 1.7, except those ones didn't use command blocks. (And they took several days, but still)...
Not a new concept.
-
- Pokechu22
- Curse Premium
-
Member for 12 years, 2 months, and 6 days
Last active Tue, Oct, 3 2023 12:07:47
- 14 Followers
- 615 Total Posts
- 129 Thanks
0
This looks like something to do with custom biomes (see issue 260). If you can use the 1.16.1 version of the mod instead, it should work properly (as that is from before a change in how biomes work), but you might not have that option.
As for updating... it's mainly a case of me not having time; there hasn't really been any progress there. Minecraft itself has changed a lot internally (e.g. data-driven biomes (the issue you're running into), then also the new world height change), and the build system (and automated test system) I use is also a giant mess that will be hard to update. I don't think there's too much that can be done to make it easier; the build system isn't really documented at all, and without fixing that it's not possible to update the mod.
0
No, not currently, and it's unclear if I'll ever have the time to update it. The newest supported version is 1.16.4.
0
That's correct. I don't think (but haven't heavily researched) that there would be anything too difficult about going from 1.18.x to 1.19.x once 1.18.x is done, but 1.16.x to 1.17.x/1.18.x/1.19.x is still difficult.
0
Unfortunately, no. I still want to do an update, but I've still been super busy and the technical challenges regarding 1.17/1.18 are still present.
0
Yes, as liteloader doesn't actually support 1.13 and newer. If you're asking about 1.17 or 1.18, though, that's a separate issue from liteloader support. 1.16 was handled by a forge build, and I want to do both fabric and forge builds for 1.17 and 1.18; I just haven't had the time to deal with build system issues and internal changes by those versions of Minecraft.
0
This is a known issue (#209) which will be fixed in the next update - unfortunately, I don't have an ETA for when that update will be released.
0
I'm still stuck in dealing with issues with the build system. The other issues (such as expanded world height, and the changes to the chunk format) haven't been investigated at all yet.
0
Regarding the recent security issue involving Log4j:
If you installed World Downloader as a base edit by creating a new launcher profile, the update Mojang pushed will not apply to that specific profile, and you will still be vulnerable. If you run the vanilla version once (so that its version JSON is updated), and then copy its version JSON and repeat the steps to edit it for World Downloader, you should be fine. (You do not need to repeat the process of editing the JAR file, only the JSON file, although there is no harm in replacing the JAR file with a clean one and patching it again.)
If you installed World Downloader using Liteloader, you will need to first launch the vanilla version once, and then re-run the Liteloader installer. That should result in Mojang's update being applied to the Liteloader installation. I believe you can update the existing Liteloader installation through this procedure, meaning you will not need to re-install the World Downloader litemod. If you installed Liteloader on top of a Forge installation, first run vanilla, then re-install Forge, then re-install Liteloader.
If you installed World Downloader using Forge, update to the most recent version of Forge, which uses an updated version of Log4j.
If you installed World Downloader using MultiMC, I think the patch MultiMC pushed should apply automatically. If you see log4j-core-2.15.0 in the library list, you are patched; if you see an older version, you are still vulnerable and may need to repeat the steps to install World Downloader with MultiMC.
I cannot guarantee that these steps are perfect in all situations; in the worst case, you may need to re-install from scratch. (Please do not discuss details of the security vulnerability here. I'm just giving this information since the patch process works differently.)
2
I don't have one, to avoid a conflict of interest. That said, if you want to send money to someone, please consider donating to the Internet Archive, since the work they do is fairly important. (Donations to them are tax-deductible in the United States, and they also have a matching program going on currently, so now's a great time to do it.)
0
Download the latest version from the downloads section in the main post (currently v4.1.1.0). Scroll down to the bottom to the "assets" section. Then download the version that matches your Minecraft version and loader (e.g. WorldDownloader-forge-4.1.1.0-mc1.16.4.jar). The installation section in the main post explains how to install the different versions.
(I now see a massive blob of code where the changelog should be; that seems to be a recent GitHub problem and is something I'll need to investigate. Proper release notes seem to show up in the main releases section and in this thread. I've created an issue to keep track of this. If that's what confused you, sorry about that; I only now noticed this.)
0
World Downloader can't get the server's seed, so it defaults to not generating any terrain at all to avoid mismatched terrain. If you know the server's seed, you can enter it in the world generator overrides in WDL's "..." menu and the world will generate normally (running /seed while downloading will automatically enter it).
1
See https://github.com/Pokechu22/WorldDownloader/issues/227 - this happens when backups are disabled due to me closing the old saveHandler only when backups are enabled. It'll be fixed in the next release (whenever that is), but for now you can work around it by enabling backups and then pressing esc to cancel the backup.
0
java.lang.RuntimeException: WorldDownloader: Couldn't get Field of type "class net.minecraft.util.text.CharacterManager" from object "com.hrznstudio.emojiful.render.EmojiFontRenderer@590a2a94" ! at wdl.ReflectionUtils.findAndGetPrivateField(ReflectionUtils.java:120) ~[?:?] {re:classloading} at wdl.gui.widget.ExtGuiScreen.func_231158_b_(ExtGuiScreen_1_16_2.java:64) ~[?:?] {re:classloading} at net.minecraft.client.Minecraft.func_147108_a(Minecraft.java:852) ~[?:?] {re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:classloading,pl:accesstransformer:B,pl:mixin:APP:abnormals_core.mixins.json:client.MinecraftMixin,pl:mixin:APP:immersiveengineering.mixins.json:accessors.client.MinecraftAccess,pl:mixin:APP:create.mixins.json:ShaderCloseMixin,pl:mixin:A,pl:runtimedistcleaner:A} at wdl.WDL.promptForInfoForSettings(WDL.java:353) ~[?:?] {re:classloading} at wdl.WDL.startDownload(WDL.java:422) ~[?:?] {re:classloading}This looks like a conflict with Emojiful caused by it replacing the font renderer, and some of WDL's multi-version GUI compatibility code not knowing what to do with that new font renderer. It can probably be fixed in WDL, but I think you can work around it by removing Emojiful temporarily while you use WDL.
1
Can you post the crash report? (Upload it to pastebin.com or a similar site and then post a link here.) I'd be able to determine if it's directly caused by the use of 1.16.4 on 1.16.5, or some other modded compatibility issue. (I can't guarantee that content from mods will be saved properly, but it's something I can still try to improve.)
1
There isn't currently a 1.16.5 version of the mod. However, 1.16.4 and 1.16.5 are protocol-compatible, so you should be able to use a 1.16.4 client with the 1.16.4 version of the mod to join 1.16.5 servers. There's also a chance that the 1.16.4 version will work on 1.16.5 (that message is just a warning, not a fatal error), but I can't guarantee it (if things don't crash, it'll probably be fine though).
Apologies for not having a 1.16.5 (or 1.17) version out yet; I've continued to be busy which has given me little time to work on this.