"Cyber Su HERO (messy)" Deck 2017

Playing

There are two types of cyber elements, Dragonet and Cyber Gadget (Bitron is also a consideration if honeypot is adopted)
I felt that it was a good match because it was easy to drop the releaser and it was easy to deploy level 4.
Also, when negate Accesscode Talker, if the cost releaser target is absolute, it will be possible to negate one card while actively Samboling, so it seems to be strong (Konami feeling)

Strength

There are several patterns of movements that I have prepared, so I will introduce them.
Vion movement
Drop it on the Vion NS Mist GY and collect Diabo
《Fusion Recovery》excluding Mist
Deer Deadly in Vion
Dia 2 Unfold and Beato
send the releaser to her GY
You should save the third one for the link
Dragonet, level 4 ss (HERO etc.)
dragonet level 1 tuner ss
Nijikou is S level 4ss and Xyz etc.
Collect Clausolus, collect rebellion, and releaser crown (Aim after the above Vion)
It's better if you can aim for a honeypot
I'm using one link, but I can aim for the release circus Clausolus, who has gained a system for combat and targets (Is this going to become mainstream after Cyber ​​strengthening comes?)
crystal, darkrow
Cyber s Gadget NS level 1 tuner revive and botenkou
Refining Tokens (Level 2) with Gadget
Synchronize power tools to recover DDR
Special Summon Shadow Mist that was removed during Vion's move to Darklaw
Cybers Gadget, Split
Together until Botenkou Split Slime with Botenkou, Synchronize 8 Dark Dragons with Graydle (Level 3), then synchronize with Lihun
*Because it can also be used as a material for ABSO water, I thought it would be good and adopted it until the introduction.
De Accesscode Talker, Abso
The specific route is undecided, but if you put Abso on the link destination, you can negate once + destroy all opponents.

Weakness

It's still undecided on Cybers' search and various balances

Customize

I think that there are many improvements because it has not been released
As for 《Stumbling》, can I make Duro with Bubble 2 Tuner to protect the honeypot itself and aim to lock it when the honeypot is deployed? It's a remnant of what I thought