Talk:Vex

Redirect
This should probably not be a redirect. Firebastard (talk) 21:05, 28 September 2016 (UTC)

LifeTicks
Is there any testing which reveals the initial value of the LifeTicks tag when summoned by an evoker, and therefore how long before a vex dies? If no, I will do some testing. TinyGenius (talk) 14:07, 21 October 2016 (UTC)
 * My current testing indicates a random value between 700 and 2000 is chosen upon summoning. is there confirmation in the game code? TinyGenius (talk) 17:24, 21 October 2016 (UTC)

"Most blocks"
Do we know which blocks, if any, they can't pass through? Has this been tested or dug up from code? Aepokk (talk) 03:31, 26 October 2016 (UTC)
 * That's a good point. If anybody finds any such blocks, they can add it ... until then I'm just changing it to basically say 'all blocks'. –  Sealbudsman talk/contr 04:21, 26 October 2016 (UTC)

Vex or Vexes?
Ok, so there has been some debate about the plural of Vex. Some people say it is just Vex and some say Vexes. I personally Think it is Vexes, but i may be wrong. Does anyone know what the correct word is? –Preceding unsigned comment was added by RedRooey (talk • contribs) at 12:15, October 28, 2016 (UTC). Please sign your posts with
 * Until you brought it up just now, I was leaning towards "Vex" myself, but in blog posts  they've been using "Vexes".  I guess that's how it is.
 * Curious, where has this debate been, that you mention? – Sealbudsman talk/contr 16:54, 28 October 2016 (UTC)


 * References

UUID
An anonymous user mentioned on Chinese Minecraft Wiki how the "OwnerUUID" affects a vex's aggression behavior: "Vexes are defined with the OwnerUUIDMost and OwnerUUIDLeast tags upon being summoned, thus making them hostile towards villagers (because evokers are hostile towards villagers). However, vexes spawned from spawn eggs or monster spawners will be free, for they do not inherit hostility from evokers." We are unsure whether it is true or not. If anyone knows, please reply us. JackAlpha26 (talk) 05:38, 28 March 2017 (UTC)
 * It's true that they're only aggressive towards villagers when summoned by evokers -- but they don't have OwnerUUIDMost/Least tags -- none persisted to the save file, none evident by inspecting their, and let me check MCP 9.37 ... the MCP does not show any OwnerUUID tag either. The MCP reveals that a vex has a CopyOwnerTarget AI task, which is allowed to execute when it has an 'owner', though the owner is not exposed in the NBT, it's only set in-code when an evoker summons it.
 * Simply put, its targeting is commanded by its evoker, but it has nothing to do with an NBT tag.
 * Side note #1, I think because they have no NBT tag, this means they stop taking their orders from their evoker (becoming player-hostile only) when the world is quit and reloaded. This might be tricky to test, because one has to be very careful to see whether a particular vex among several is taking orders or not ...
 * Side note #2, the OwnerUUID tags are used by tamable mobs, evoker fangs and lingering potion clouds (so that damage by fangs or clouds are attributable to their owners), and llama spit (only spit owned by a llama will deal damage). – Sealbudsman talk/contr 17:01, 28 March 2017 (UTC)

Wow. Thanks for your reply. JackAlpha26 (talk) 15:07, 29 March 2017 (UTC)

Vex's sword drop
The part on the vex dropping its sword when looting is used turns out to be a bug, as seen with MC-2958, which appears to have been fixed in snapshot 19w37a. That section should be edited to reflect the resolution of the bug report. Stranded at sea (talk) 16:13, 25 October 2019 (UTC)
 * Thanks for letting me know! I removed that part, now it just says the Iron Sword can't drop and 5 xp is dropped. Yreyot25 (talk) 16:03, 13 August 2020 (UTC)

Defense Against Vexes???
Unable to figure out how to defend myself against them or to tell which direction they are coming from! Anyone have any clues? SFFrog (talk) 02:35, 1 February 2020 (UTC)


 * Well, they aren't invisible. Whack at them with your sword when they get close enough. Wear good armor too. ~ Amatulic (talk) 06:08, 1 February 2020 (UTC)


 * It occurs to me that one way to fight them is to force them to come at you from the front. I've done this with endermen. Build two walls that form a corner, with a block overhead. When you aggravate an enderman, run to the inside corner. This works especially well underground. It forces the enderman to approach you from the front, making it easier to attack. I never tried this with vexes. It may not work because vexes can pass through any solid block. Maybe the best way is to have friends join you to fight them off while you all stand back-to-back. Amatulic (talk) 17:26, 6 October 2021 (UTC)

why arent these guys bosses
i legit this morning used like two or three totems in a row because of these little pains. I mean i see why they are annoying ecause the word vex literaly means to irrate so of course they are gonna be annoying but idk whos more annoying vexes or my brother oh wait my brother is a vex and im an evoker LOL LMAO

Data Values and Behavior
I have a correction I have to make, but seeing as this is the first time I've made a correction I would like to present it beforehand to be confirmed.

In the behavior section it states "When idle, vexes wander within a 15×11×15 cuboid range centered on their evoker's position, unless summoned by a spawn egg or by the /summon command." In Data Values under Entity Data (Java Edition) it states, "BoundX: This central spot is the location of the evoker when it summoned the vex, or if an evoker was not involved, it is the location the vex first attempted to idly wander."

My testing has shown that when a vex is summoned via the summon command or via spawn egg the BoundX, BoundY, and BoundZ tags do not exist. When these nbt tags do not exist, the vex does not wander in a cuboid range; Instead, it wanders anywhere like a normal mob. The first quote indicates that its wandering would not be centered on an evoker if an evoker was not involved, but does not indicate that it would not be centered at any point at all in this case. The second quote indicates that if a Vex was not summoned by an evoker, then the Bound nbt tags would be set to where it first began to idly wander. This is incorrect. In this case, the Bound nbt tags do not exist.

The only cases other than the vex being summoned by an evoker that I have tested are summoning via spawn egg and the summon command. In the second quote it only says, "if an evoker was not involved." I would like to make sure that there are not other cases for summoning an evoker that need to be tested before making the change since it is ambiguous about the cases it refers to.

The tests were done in 1.17.1

Galdeveer (talk) 03:48, 8 October 2021 (UTC)


 * Changes you want to make based on your tests are reasonable. Just remember to describe your change in the edit summary before you submit it. Amatulic (talk) 03:50, 8 October 2021 (UTC)


 * The change has been made to the description of BoundX. I decided not to touch the first quote. It's ambiguous enough that it does not contradict the change that was made to the second quote. The ambiguity should be clarified in the future, but I can't think of a concise enough wording to justify making the change now.Galdeveer (talk) 04:51, 8 October 2021 (UTC)