This Lineup Dominated [AzBxT3] Group A! Arizona Beyblade X Tournament#3

[@ENDEV]

You can now support my channel by joining as a member! For A minimum fee of 1$, you can gain access to members only perks! I will also be posting there snapshots of my database to keep you updated of the current meta based on statistics! Alternatively, you can also support the channel by simply liking this video and subscribe if you are new to the channel. Thanks for watching! Timestamps: 0:14 Match#1 1:04 Match#2 2:37 Match#3 3:48 Match#4 4:42 Match#5 6:35 Match#6 7:15 Match#7 8:04 Match#8 9:01 Match#9 10:25 Match#10

[@WinterGray8888]

That knightlance 3-60 HT combo makes me very happy, I’ve speculated for a while now that point and high taper could be used for defense combos cause of their high burst resistance whilst still being more tame than full attack combos, now I just wish someone would take this idea a little further. I think this might be able to make tall defense combos much stronger

[@ENDEV]

I feel that KnightLance is underrated. Hopefully more people use it.

[@nintendobl00d]

My current fave combo! Had decent results with it at my last tourney

[@YeetNation2006]

That tourney was quite fun, had a great time dominating the block lol

[@BeybladeXDash]

Wow looks really fun!!

[@Sharleen-p8u]

New vid yay 🎉

[@EG80]

Weird request here but instead of showing the top and then the bottom of the beyblade can you show the bottom first then the top, idk if it's just me but it would make it easier to keep track of who has what

[@XACE_BLADER]

Hello ENDEV, I have a question. Do we really need the deck case of BEYBLADE X or can any case just like the metal fight cases okay?

[@ENDEV]

You can use any deck case.

[@XACE_BLADER]

@@ENDEV Oh cool

[@ad_beyblade]

Knight shield GOAT

[@ENDEV]

Very good defense blade!

[@ad_beyblade]

Where's phoneix wing?

[@ENDEV]

PhoenixWing was just released during this tournament and most most of us didn't receivec it yet. I also have footage of our recent tournament and will be uploading it in a couple of weeks.

[@Chakramania]

when was this tournament? Why are there no phoenix wings?

[@ENDEV]

PhoenixWing was not yet released. I took a break that's why I got some catching up to do on editing/uploading.. 😅

[@jhaybz29]

hmmm I'm a tiny bit confuse with the burst priority rule, in our local rules we follow "first occurrence, first priority" 4:23 X-finish would have been ruled. But what do you guys think? should it be Burst Priority or first occurrence, first priority?

[@IronStaffTruther]

Burst priority is TT rules. Dunno about WBO

[@deos2768]

Burst priority is definitely just a burst era thing. In official japanese tournaments they do as you said and give the round to whatever happens first. In the case that it's too hard to tell they usually redo the same match or keep going as if the match didn't happen.

[@ENDEV]

Based on official Takara Tomy rules, it is burst priority. But take note that burst in X is slightly different, the parts need to seperate in order to consider it as burst.

[@jhaybz29]

this has always been up for debate in my community too, our recent tournaments (the private ones) we are following first occurrence. There is also a draw ruling where we had to re-do the match with same beys. Yes we also follow that parts need to completely separate to count as a burst if the bey is still sitting on top of its bit (which is usually the case) it will not count. This get confusing and blurry when it comes to burst priority because sometimes a burst can occur without bey contact and a few milliseconds after an over or x finish.

[@collinstaggs8239]

hey i’m looking into getting into it can you send me more information

[@blockchainoverdrive6090]

1:05 Group A Match#2 should've been a relaunch. No contact with other bey and straight to over finish zone. : /

[@ENDEV]

In our tournaments, we don't do relaunch for a player that makes a mistake. It's not a practice game so players are expected to be prepared during tournaments. We do relaunch if beys hit in mid air, launcher issue, or significant delayed/late launch.