User talk:Kkkllleee

Show preview
Please use the show preview button to preview your changes rather than making many edits to a page. –Majr ᐸ Talk Contribs 08:19, 2 May 2015 (UTC)
 * There also may be a Preview tab. You can use it too, although it is more or less experimental. &mdash; Grid Command Block.png NickTheRed37 (talk&#124;contributions) 08:35, 2 May 2015 (UTC)
 * The preview tab works fine, and I use it all the time, although sometimes I miss click when I meant to show preview it saves the changes and it's so annoying.--Kkkllleee (talk) 14:56, 2 May 2015 (UTC)


 * Once again, a reminder to try and condense your edits (i.e. instead of doing 5 small edits, do a larger edit). –Goandgoo ᐸ Talk Contribs 11:03, 31 May 2015 (UTC)

Commas
Just a friendly note, only since I see it in some of your recent edits: Commas don't precede verbs, including helping verbs such as do, don't, could, would, etc. ...unless the comma is doing another special job like: – Sealbudsman (Aaron) t/c 03:03, 3 May 2015 (UTC)
 * for instance, not here: (dirt and gravel in a 2×2 checkered pattern, yields four coarse dirt)
 * and not here: (Block states of the block being looked at, will now be displayed on the F3 menu)
 * setting apart a clause along with another comma: (...a command block that, when placed, will automatically signal..)
 * creating a list of verbs: (...if the player jumps, falls, crouches or walks...)
 * preceding a command/instruction: (To use, press create new world then ‘world type: customized’)
 * Thank you for the tips, I for some reason always had trouble with the comas in english. Do you think I should keep trying to improve? Whart do you think of the changes so far?

--Kkkllleee (talk) 03:22, 3 May 2015 (UTC)
 * I like your changes so far, keep it up, definitely! Is your first language Spanish? It says Mexico City on your profile. Are commas used differently in Spanish, I guess? – Sealbudsman (Aaron) SealbudsmanFace.png t/c 13:18, 3 May 2015 (UTC)

Concerning Command/NBT Edits
Just need to clarify a few things.

The "xp" statistic tracks total experience points. The "level" statistic tracks the total experience level. They are two different methods of tracking experience gain.

CommandStats are a hefty and complicated mechanic. The only automated triggers are  and. is not automatically determined. If it can track something new, it is crucial to state that it can (and the same goes for  and  ). If there are exceptions to the automated triggers, then those exceptions should also be stated (none so far in 1.9 though).

The example for the CommandStat is correct. In the source, running that specific command returns a  value, which it would not have been automatically capable of doing like the automated triggers. It is not feasible to write a tutorial on the changelog about how to use CommandStats as it would be far too long. The example assumes the reader knows how to use CommandStats, especially since all information necessary has been given (the "QueryResult" phrase as well as the command to trigger said "QueryResult"). Please do not remove the example, because without it, the statement about CommandStats is useless. The statement is specifically referring to that command example.

The  tag in 1.8 is stored as a Short tag on all mobs including the player. The  tag was also stored as a Float. In 1.9,  is completely removed from the game while   has changed from a Short to a Float. is still applied to everything extending the "Living" class, which includes mobs and players. It is not exclusive to any particular entity nor was it an Integer tag.

The  is the entity that is created by the ender dragon when it breathes ender acid. There is no "ender acid" entity at all. I recommend looking at the Chunk Format page concerning the entity.

Skylinerw (talk) 05:54, 17 August 2015 (UTC)


 * OK I understand just a few things:


 * You have to explain briefly what we expect from your example, like I said it is both a change to CommandStats as well as an addition of QueryResults (if query results wasn't just added, then it shouldn't go in the addition section), so it must go both places, but worded differently.


 * We must explain the difference between level and xp in both the main article and in the snapshot article.


 * Other than that we are in agreement. Thank you. --Kkkllleee (talk) 06:09, 17 August 2015 (UTC)


 * For sorting the CommandStats, personally I'm not sure if it should be filed under Additions or Changes. The "QueryResult" trigger itself is not new, but the introduction of the "Tags" feature is. The "QueryResult" value returned from the new "Tags" feature is dependent on the newly added "Tags" feature itself; without that new feature, this particular value cannot be obtained.


 * It's honestly hard to explain how it's a newly added feature without describing CommandStats entirely. The "QueryResult" trigger itself has very few cases where we can obtain a scoreboard value (/xp, /worldborder, /time, and /gamerule, for example, are some of the few commands that have functions returning a "QueryResult" value).  is a new function where we can obtain a value for "QueryResult". I'll clarify the example for it on the relevant pages, though it can't really be expanded upon without becoming convoluted.


 * But the example is a very necessary example since it's how we are meant to obtain the value to begin with. Without providing the method of getting the "QueryResult" value, the statement of simply being able to get that value is unhelpful. It's a very specific function call to get that value, which is the case for all "QueryResult" usage. must be used to get that value, as it is the only way to get that value, and that is what the statement is referring to. Skylinerw (talk) 06:38, 17 August 2015 (UTC)


 * Based on what you said it is clearly a change, it is irrelevant if it's dependent on an addition, so I should make the relevant changes and marking the difference between level and xp. --Kkkllleee (talk) 06:55, 18 August 2015 (UTC)