Bastion Remnant renders
Hello, I looked at your bastion remnants renders, and it seems they don't follow the Strandardized views rules, first of all - the lighting, it seems a bit off compared to in-game lighting, also - the camera rotation - it should be a view angle of 45° and 60° . If possible It would be amazing if you could reupload the images following the Standardized Views rules. Thanks Oakar567 (talk) 10:25, 17 April 2020 (UTC)
- I admit that it is not the lighting in game, but I am sure the view angle is 45°and 60°. However, I have no idea how to creat the renders of these 1.16' structures with the in-game light. --Chixvv (talk) 14:55, 17 April 2020 (UTC)
- I cloned them into 1.12 with textures, and captured using Mineshot. Do they look better now?--Chixvv (talk) 09:10, 18 April 2020 (UTC)
result of data modify
scoreboard objectives add test dummy
scoreboard objectives setdisplay sidebar test
data modify storage array array1 set value 
data modify storage array array2 set value [0,0]
execute store result score result test run data modify storage array array1 append from storage array array2
Tested in version 1.16.2
This adds 2 elements to the array, but the result is 1.
How did you test the result value?
220.127.116.11 14:59, 23 August 2020 (UTC)
- Alright, I was sloppy and made a mistake. It should be the number of lists or arrays to which new elements are added. For example, if array1 is [,], and array2 is , then
/data modify storage array array1 append from storage array array2returns 2.--Chixvv (talk) 16:26, 23 August 2020 (UTC)
Command permission levels
I saw that you reversed my reversal of your edit to the permission level of Commands/daylock, so I discovered the section you referred me to. But after reading it I was left to wonder how these levels, which for all I can tell are internal values, were determined or, more importantly, how an ordinary player is expected to make use of any of this.
In the first place, the common meaning of "permission" in English applies only to people, or at least sentient entities; you can't give permission to a command or a console. Clearly the reader is meant to understand the concept of giving permission to a thing as a shorthand way of saying requring a player to have a certain permission in order to use that thing. But the Commands#Permission_level section uses it both in the strict sense and as a shortcut by referring to permissions for both players and commands/other things with no distinction. Furthermore, this shortcut usage persists in every command subpage without explanation of any kind. I find it awkward to read even as a native English speaker, and I'm concerned that someone whose English comprehension is weaker wouldn't be able to make sense of it at all, or would at least be very confused about what "permission" means.
In the second place, how is a Bedrock player expected to know what commands are available to them, even if they can figure out when "permission" means "permission held" versus "permission required"? In the only place where a player's permission appears explicitly, it is divided into Guest/Member/Operator permission groups or a handful of individual Player Permission toggles reached via the in-game (so-called "pause") menu. If there is supposed to be some correlation between these groups and the command permissions, it certainly isn't explicit, which is why I initially reverted your edit changing "op" to "1". How is a player supposed to know their permission level, or change it? Are the permission levels documented on the Commands page and its subpages even related to these player permissions? Or are they something specific to BDS, in which case why aren't they identified as such in the command infoboxes, perhaps by referring to them as "BDS Permission Required"? And if so, shouldn't the required permissions as identified in the UI be provided as well, since they would be more relevant to the ordinary player?
I realize the questions above go far beyond the scope of the single edit we contended over. I don't necessarily expect authoritative answers from you, but your recent edits suggest to me that you're doing a sweeping cleanup of command pages, so I think you might be interested in bringing up these issues with the editing community or perhaps boldly editing to address them yourself. Speaking for myself, I currently limit my involvement to watching a bunch of pages for vandalism, accuracy, and wikignome work. Being a moderator on the bug tracker, I don't have a lot of time to participate in projects here on the wiki, at least not ones of this scope. — Auldrick (talk) 14:58, 7 February 2021 (UTC)
- I added some infomation into Commands#Permission_level to explain it, and changed it in the subpage to "Permission level required".
- The permission level held by players can be found in level.dat, in which there are "permission-level" and "player-permission-level". The latter is used to denote visitor/member/operator/custom, and the former is related to commands.
- I decompiled the Bedrock Edition for Android, the BDS, and Education Edition, and found the required permission levels for each command. And I got "permission level" held by players, command blocks, console, etc. by testing in the game. "Permission level" may not appropriate to a command blocks or a console, but I'm not a native English speaker, so I don't know which word is better. Maybe you could give me some advice.-- Chixvv (talk) 01:30, 8 February 2021 (UTC)