Minecraft Wiki
Advertisement

Useless Edits[]

Your Edits Are Becoming Useless! 105.187.25.75 08:57, 27 April 2021 (UTC)

Stop Making Useless Edits! 105.187.25.75 11:56, 27 April 2021 (UTC)
They're not making useless edits, they're uploading images for version pages. NexaForX (𝓣𝓪𝓵𝓴|𝓒𝓸𝓷𝓽𝓻𝓲𝓫𝓼) 11:59, 27 April 2021 (UTC)
NexaForX I think that lil snip just wants to intimidate Anterdc99 because he just wants attention NOBUDOT (talk) 15:42, 27 April 2021 (UTC)

Tweaks for Fixes query[]

Hi, I have a suggestion to tweak the "Fixes" query in https://minecraft.fandom.com/wiki/Java_Edition_1.17#Fixes to eliminate development versions' fixes, so the query would return exactly the fixes from released versions before 1.17. The query currently returnes over 1000 bugs, because it includes the dev. fixes, but it would be enough to add following to the query:

... AND affectedVersion ~ "1.*" AND (NOT affectedVersion ~ "1.17*")

Please check it, it returns just 302 bugs. I don't know how to edit the query on the wiki page, because there is used a template. --TwoBlocksMC (talk) 20:15, 4 June 2021 (UTC)

I thought this problem before actually, but I don't have a suitable filter to do that.
But, if some bugs fixed between the final development release and the first stable release, this filter will not show up these bugs.
Should we consider this? Or just list "old" bugs fixed in all development versions?-- Anterdc99Face.png Anterdc99(T·C) 05:14, 5 June 2021 (UTC)
Anyhow, I added some parameters to make new filter possibile. Please view the updated template documentation.
You can add affectedmatch=1.* and notaffectedmatch=1.17* for example.-- Anterdc99Face.png Anterdc99(T·C) 07:04, 5 June 2021 (UTC)
I'm not sure if you understood my intention well; it might be so because of my different understanding of some terms.
So, as for me:
- Stable release is a release having a simple version number: 1.16, 1.16.5, 1.17 etc.
- Any other version/release/pre-release is a development or not-stable and as such is not interested for the end-user who uses only stable releases for playing, and consequently - he is interested in bugs that affected stable releases only, and then has been fixed.
If my understanding is wrong, correct me, please.
Also, explain me please, what you mean when saying: "development release", "final development release" and "stable release".
Having said that, I continue to explain what was my intention:
I wanted to get the result of the query which is exactly according to the title of the Wiki section:
"Fixes - From released versions before 1.17".
I assume that we consider stable releases only, because other releases are not interested for the end-user.
Generally, all the bugs that were fixed for a stable release should have been marked as affecting this release, but this rule is not always followed, as I saw in Jira, especially for bugs reported in minor releases (like 1.16.4).
So, we would like to list all the bugs that were fixed in any of 1.17 Snapshots/Pre/RC (up to 1.17 stable release) and that affected any stable release before 1.17 (exactly: up to 1.16.5)
and this is achived by the clause: affectedVersion ~ "1.*" .
The additional clause: (NOT affectedVersion ~ "1.17*") - would eliminate any bugs reported for "1.17 pre*" and "1.17 RC" (as not-stable).
--TwoBlocksMC (talk) 20:22, 5 June 2021 (UTC)
I understand what your mean. Maybe I don't express my meaning well.
My question is: If some bugs fixed on 1.17 itself, which contains some bugs from "dev" or "previous", should we list these "dev" and "previous" bugs in the fixes list of 1.17?
Obviously, if we need to include those bugs, the filter you mentioned above can not list them.
If we needn't include them, that filter will work well.-- Anterdc99Face.png Anterdc99(T·C) 11:44, 6 June 2021 (UTC)
Could you please give me an example (fake, abstract scenario) of what bugs you consider when you are asking:
If some bugs fixed on 1.17 itself, which contains some bugs from "dev" or "previous", should we list these "dev" and "previous" bugs in the fixes list of 1.17?
--TwoBlocksMC (talk) 16:42, 6 June 2021 (UTC)
Something like MC-148723 in Java Edition 1.14#fixes.-- Anterdc99Face.png Anterdc99(T·C) 17:00, 6 June 2021 (UTC)
OK, thanks, now I understand what you meant ;)
The bugs "From the previous development version" is another thing...
Of course, they should be listed there (in the bugs list of the final stable release), just to keep consistency with all the other Wiki pages.
However, the problem is that we have some inconsistency: the Wiki articles concerning any development version contain only the bugs fixed in just this one version, but the article of final release gathers all the fixed bugs "from released versions before..", which is (generally) a good idea, to summarize the work on the release, and also, as I said, because all these bugs might be of interest for an end-user who considers stable releases only.
To solve this inconsistency there should have been two separate lists of fixed bugs:
1. regular list: bugs fixed only in the final release (including the "dev" and "previous" versions),
2. separate list of all fixed bugs that were reported in earlier released versions.
However, I think that all the problem is not so important and not worth of so much work and redesign,
so I would leave this as it is now - it's really OK ;)
What could be considered is - if we had separate Jira links in each subsection of "Fixes" section,
so that they had separate URLs containing more specific clauses (then we could implement my suggestion, as well).
However, again I don't know if it's worth of work.
I leave all the thing as a suggestion only (for you or for anyone on the Wiki who likes such improvements).
--TwoBlocksMC (talk) 18:25, 6 June 2021 (UTC)

Please explain your revert better[]

Have you actually tried getting the advancement the right way? I did, and it made the new advancement show up. So, perhaps the /advancement command is broken? SirDaddicus (talk) 18:07, 5 August 2021 (UTC)

I replied at Talk:Advancement-- Anterdc99Face.png Anterdc99(T·C) 02:04, 6 August 2021 (UTC)

Kumi Tanioka redirect[]

Whoops! I was testing redirects to Wikipedia, and I meant to replace Netflix with Kumi Tanioka. Thank you for putting in the soft redirect.Minermatt122514 (talk) 15:01, 30 October 2021 (UTC)

New snapshots, pre-releases pages[]

While creating snapshots or pre-releases, don't use "which fixed", but rather "which fixes" instead. This is gramatically correct, as the sentence is in present tense. Have a good day! Spectrogram (talk) 14:11, 18 November 2021 (UTC)

OK, thanks for your reminding.-- Anterdc99Face.png Anterdc99(T·C) 14:19, 18 November 2021 (UTC)

1.18 panorama[]

1.18 panorama was added in 21w41a, you can check in the article page. And you reverted my edit, that I fixed it. It was 21w37a (wrong version) and then I fixed to 21w41a. LucasGameszYT (talk)

Because the panorama is distributed by assets index, so the previous snapshots in the same developing series also received the new panorama.
So, if you currently open an instance of 18w43a, 19w34a, 20w06a, 20w45a, or 21w37a, it will shown 1.14, 1.15, 1.16, 1.17, or 1.18 panorama respectively, even though they are not show the updated panorama at that time.
Now the current statements is respecting both their historys and their current situation.
For previous panoramas, when describing versions which was used them, are seperated into two parts, the major part is located at the section of the panorama which is describing (section of C&C P2), before your edit, it says 21w37a+. The minor part was written in the section of the previous panorama (section of C&C P1), it say the previous one is used in 21w37a-21w40a at that time. So the major part respects the current one, and the minor part respects the historical one.
Previous instances:
Panorama major part minor part
Update Aquatic 1.13-pre1~1.13.2 18w43a~18w47b(1.14's snapshots)
Village & Pillage 18w43a~1.14.4 19w34a~19w40a(1.15's snapshots)
Buzzy Bees 19w34a~1.15.2 20w06a~20w13b(1.16's snapshots)
Nether Update 20w06a~1.16.5 20w45a~21w14a(1.17's snapshots)
Cave & Cliffs: Part I 20w45a~1.18-exp7 21w37a~21w40a(1.18's snapshots)
But honestly, the current statements are confusing a lot of people, it should have a better format to achieve the goal mentioned above. But currently, only change the statement of C&C P2 is breaking the consistency, so thats the reason I reverted your edit.-- Anterdc99Face.png Anterdc99(T·C) 16:41, 27 November 2021 (UTC)
Advertisement