Thanks for doing this, I appreciate your efforts. I'm surprised there's not a donation link. Or did I just miss it?
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.)
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.)
I understand. I will donate to the internet archive in your name.
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.)
No update on 1.17 / 1.18 version yet ??
Even an update like - 'currently bug testing' or ' problems with new world generation that needs sorting out' would be appreciated
No update on 1.17 / 1.18 version yet ??
Even an update like - 'currently bug testing' or ' problems with new world generation that needs sorting out' would be appreciated
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.
I've noticed that when using WDL 1.16.4 on a 1.16.5 server, opening the saved chunks screen immediately causes a CTD. This happened when using the MultiMC version, and the Forge version. Crash Report : https://pastebin.com/fknVPjNG
I've noticed that when using WDL 1.16.4 on a 1.16.5 server, opening the saved chunks screen immediately causes a CTD. This happened when using the MultiMC version, and the Forge version. Crash Report : https://pastebin.com/fknVPjNG
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.
Will this mod be able to update to versions of mc liteloader doesn't support?
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.
it does warn of this in the Disclaimer
Thanks for doing this, I appreciate your efforts. I'm surprised there's not a donation link. Or did I just miss it?
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.)
1.8 / 1.9 / 1.10 / 1.11 / 1.12 / 1.13 / 1.14 / 1.15 / 1.16 World Downloader mod maintainer
Moderator on the mojang bugtracker, and also pretty deeply involved with the protocol documentation on wiki.vg.
I understand. I will donate to the internet archive in your name.
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.)
1.8 / 1.9 / 1.10 / 1.11 / 1.12 / 1.13 / 1.14 / 1.15 / 1.16 World Downloader mod maintainer
Moderator on the mojang bugtracker, and also pretty deeply involved with the protocol documentation on wiki.vg.
No update on 1.17 / 1.18 version yet ??
Even an update like - 'currently bug testing' or ' problems with new world generation that needs sorting out' would be appreciated
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.
1.8 / 1.9 / 1.10 / 1.11 / 1.12 / 1.13 / 1.14 / 1.15 / 1.16 World Downloader mod maintainer
Moderator on the mojang bugtracker, and also pretty deeply involved with the protocol documentation on wiki.vg.
I've noticed that when using WDL 1.16.4 on a 1.16.5 server, opening the saved chunks screen immediately causes a CTD. This happened when using the MultiMC version, and the Forge version. Crash Report : https://pastebin.com/fknVPjNG
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.
1.8 / 1.9 / 1.10 / 1.11 / 1.12 / 1.13 / 1.14 / 1.15 / 1.16 World Downloader mod maintainer
Moderator on the mojang bugtracker, and also pretty deeply involved with the protocol documentation on wiki.vg.
Will this mod be able to update to versions of mc liteloader doesn't support?
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.
1.8 / 1.9 / 1.10 / 1.11 / 1.12 / 1.13 / 1.14 / 1.15 / 1.16 World Downloader mod maintainer
Moderator on the mojang bugtracker, and also pretty deeply involved with the protocol documentation on wiki.vg.
Any updates on 1.17/1.18? This would be super useful for Hypixel SMPs, but ours is using 1.18.2 atm.
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.
1.8 / 1.9 / 1.10 / 1.11 / 1.12 / 1.13 / 1.14 / 1.15 / 1.16 World Downloader mod maintainer
Moderator on the mojang bugtracker, and also pretty deeply involved with the protocol documentation on wiki.vg.