Minecraft Wiki
Don't have an account?
Register
Advertisement
Register
Minecraft Wiki
Minecraft Wiki
7,425
pages

Talk: Java Edition 18w19a

Back to page
Revision as of 22:36, 31 May 2018 by Pokechu22 (talk | contribs) (→‎Fluid tag information rearrangement: late reply, I'd say it'll depend on whether we get more changes or not)
Sign in to edit

Download site

The download site may have changed. The normal URLs do not seem to work

Not posting URLs - can't post due to not able to log in.

Anyone know where to download the files now? I would definitely like to get a-hold of the server client. I'm hoping this is just a mess up on Mojang and not that they are changing sites again. 70.100.103.14 03:55, 9 May 2018 (UTC)

The s3.amazonaws.com/Minecraft.Download links have been deprecated for a while now, and are now officially unsupported. You should use the version manifest instead. The launcher should contain a link to download the server. ‎Skylord wars is working on updating the links on the wiki, which probably should have happened a while back (it's something I meant to do for at least a year but never got around to). I've added the links to this article now though. --Pokechu22 (talk) 04:02, 9 May 2018 (UTC)

 Info For reference the server jar for this snapshot is here[1]. The manifest seems to place the jars at launcher.mojang.com/mc/game/(version / snapshot)/(client / server)/(jar sha1 here)/(client/server).jar jjlr (talk) 04:12, 9 May 2018 (UTC)

Mojang deprecated the old site a few days ago. The old links will be removed from Amazon's file service by the end of the year. We must quickly move all of the links to the new one. Though the new format now contains a code, to encrypt it. Skylord wars (talk) 04:44, 9 May 2018 (UTC)
skylord wars So should each page contain a direct link for the download? jjlr (talk) 05:08, 9 May 2018 (UTC)
They've added several new fields to {{Version nav}} that are used to construct the download link; the use of it there should be updated for those as per the version manifest. I feel like it's worth noting that it's not encrypted, just a hash (like with assets).
The one thing I'm not fully sure about is I don't particularly like the names for the fields (jar, json, and servercode). I think json (or maybe jsonid), clienthash (or maybe sha), and serverhash would probably be better; I don't like jar because it's ambiguous (both the client and server are JAR files) and servercode seems like a weird name. This is probably something to figure out before changing all the articles, since editing them a second time would be a giant pain. --Pokechu22 (talk) 05:14, 9 May 2018 (UTC)
Go ahead and change it. This download link change should be done by the end of the year. Skylord wars (talk) 05:21, 9 May 2018 (UTC)
I would agree with clientsha, serversha, and jsonsha, since they are somewhat clear on what they are and what they are relating to. jjlr (talk) 05:26, 9 May 2018 (UTC)
Thing is, the one for the JSON actually isn't a sha (since the JSON changes); it's just a random value (dinnerbone confirmed this, see #mcdevs log 110, ctrl+f 2017-02-08 09:50:30). The other ones are shas though. --Pokechu22 (talk) 05:32, 9 May 2018 (UTC)
That does explain why i keep getting the wrong value when i check the json's sha1. jjlr (talk) 05:50, 9 May 2018 (UTC)
I've updated the template to use the old site if the fields aren't specified, so that most links aren't broken for the moment. I've also created Category:Versions using legacy download site which contains all of those pages, so that they can be more easily swapped out. --Pokechu22 (talk) 06:32, 9 May 2018 (UTC)
18w19a shouldn't have been on that list though, it was already updated to include the hashes. jjlr (talk) 07:01, 9 May 2018 (UTC)

Shouldn't we just use version_manifest.json directly to put the JSON IDs in the infobox, and use a bot to do populate the game/server links? –Majr ᐸ Talk
Contribs 10:08, 10 May 2018 (UTC)

version_manifest.json does not include all the versions; for example, snapshots for older versions (like 1.12 currently) won't show up, and snapshots like 18w21a won't show up either if there was another snapshot that week (example: 18w21b).
All versions currently available in version_manifest.json are listed on this page on the German wiki: de:Minecraft Wiki:Versionsliste (requires a gadget). | violine1101(Talk) 11:38, 27 May 2018 (UTC)
Urgh not having some snapshots is really annoying. So we're just going to have to manually collect hashes forever to get all versions? –Majr ᐸ Talk
Contribs 12:11, 27 May 2018 (UTC)
As far as I can see, yes. I asked Dinnerbone about it on twitter, but he either didn't understand my question correctly or we all just can't find the complete list of JSON IDs. | violine1101(Talk) 16:35, 27 May 2018 (UTC)
DB has been asked about this, and a manifest that includes all versions is on the to-do list (#mcdevs log 152, ctrl+f 2018-03-11 10:40:56). In the mean time, yeah, we need to manually collect IDs. Multimc has been archiving the version manifest continuously, but it doesn't go back super far (I think partway into the 1.9 snapshots?). Some more snapshots can be found in there, but it's not perfect. I did grab a list of links from there using a rather awful bash pipeline (git log -p version_manifest.json | grep -e "^\\+" | grep url | sort | uniq | less), so that's a starting point. Note that we can still use the s3 JSON to get the correct jar hashes for old snapshots, just not the version JSON link. --Pokechu22 (talk) 17:16, 27 May 2018 (UTC)

Worlds from previous snapshots

In changes it states "Due to changes in world generation, worlds from previous snapshots will no longer work", and while that is true today it seems to have been a bug that will be fixed tomorrow[2], so it should probably be reworded so people don't mistake it for meaning pre-18w19a worlds will be unusable in 1.13. jjlr (talk) 05:17, 9 May 2018 (UTC)

 Support Skylord wars (talk) 05:23, 9 May 2018 (UTC)

Fluid tag information rearrangement

I think that the Fluids sub-header should be renamed to Command format, as Fluids is not a viable sub-header name as per the style guide, containing the added fluid tag. The information about the separated logic should be put under the Changes header. My idea for the split is: 

Additions
    Command format
    *Added two new fluid tags: minecraft:lava and minecraft:water.
Changes
    Blocks (possibly, something else may fit better to show fluid isn't a block)
    *Separated some of the logic for blocks and fluids.
        *Current fluids:
            *minecraft:empty
            *minecraft:flowing_water
            *minecraft:water
            *minecraft:flowing_lava
            *minecraft:lava
        *The fluid at a location is currently dependent on the block at the location; currently there still are water and lava blocks. 
        *This system is mostly internal; it cannot be directly interacted with yet. (I'm not sure whether this is about the tags or the logic, so I put it here)

--Incrazone (talk) 05:50, 19 May 2018 (UTC)

I don't like "blocks" as the heading for fluids since the main point of the recent changes is that they are different now. I do think it might make sense to have the tag grouped under command format since that's used for most tags (though it does feel like a strange category to be honest). I personally thing it'd be better to just dedicate "Fluids" to its own category (n.b. to be lawyery, the article says "should have the following subsections" but doesn't exactly restrict sections -- but that is a poor argument); it'd depend on how many other changes happen in later snapshots. But e.g. future changes to lava/water no longer make sense to group under blocks since the changes are actually to the fluid (in most cases I can think of) as well. --Pokechu22 (talk) 06:18, 19 May 2018 (UTC)
If "Command format" doesn't fit (and I agree, the relation is vague), and "Blocks" doesn't fit, then why not put it in "General"? – Jack McKalling [ User page Talk page Contributions ] 19:55, 21 May 2018 (UTC)
Super late reply, but, yeah, "General" seems reasonable. It depends on whether Dinnerbone's other fluid changes eventually make it in or not; they haven't happened in the following snapshots though (right now fluids are still dependent on the block state at a position via waterlogged), but we have gotten the recent F3 change in 18w22c. If we don't get another major change by the time the 1.13 prereleases start, probably we should switch back to "General" (but if we do then it might make sense to dedicate a fluids category). --Pokechu22 (talk) 22:36, 31 May 2018 (UTC)
Community content is available under CC BY-NC-SA unless otherwise noted.
More Fandoms
Advertisement