Timeline for How do I select all but two types of entities in Minecraft with the type selector?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 11, 2016 at 8:41 | comment | added | Egor Hans | @Skylinerw It does make sense up to some point. However, it's quite obvious that implementing it like this is not actually a good idea. If you have multiple occurrences of one key, you would expect both to have some impact. | |
| Jun 27, 2016 at 13:49 | comment | added | Skylinerw |
@EgorHans Selector parameters are mapped as a basic associative array, where key names must be unique. It'd be the same as trying to declare the array ["key1" => "a", "key1" => "b"] in that "key1" has been duplicated and thus overwritten.
|
|
| Jun 27, 2016 at 12:44 | comment | added | Egor Hans | It would interest me, by the way, to anyone who clicked the link: Did you observe that level of nonsense in any MineCraft stuff? Because sure, restriction handling is unlogical, but not to the extreme degree of the examples in the video. | |
| Jun 27, 2016 at 12:38 | history | edited | Egor Hans | CC BY-SA 3.0 |
improved wording
|
| Jun 17, 2016 at 9:48 | comment | added | Egor Hans | @MrLemon I used the different operator to clarify it's pseudo code. If Villager owerwrites Player, then, of course, wat. | |
| Jun 14, 2016 at 15:05 | comment | added | MrLemon |
Except that this completely wrong. When parsing [type=Player,type=Villager], the game simply forgets about Player, the type variable is just overwritten. Also, not equals is =! in Minecraft because of argument=value parsing, where the equals sign is fixed, and the value is negated by the !.
|
|
| Jun 14, 2016 at 14:19 | review | Late answers | |||
| Jun 14, 2016 at 14:57 | |||||
| Jun 14, 2016 at 13:58 | history | answered | Egor Hans | CC BY-SA 3.0 |