Close Menu
    Anime Manga News Reprints Rush Duel Yu-Gi-Oh! Go Rush

    “Voidvelg” Reprints! [RD/5TH1]

    NeoArkadiaBy 5 Comments

    An elite unit of Voidvelg marches forth.

    RD/5TH1-JP068 Voidvelg God Requiem (Reprint)

    RD/5TH1-JP069 Voidvelg Requiem (Reprint)

    RD/5TH1-JP070 Voidvelg Palerider (Reprint)

    RD/5TH1-JP094 Voidvelg Gigantomachia (Reprint)

    RD/5TH1-JP105 Voidvelg Chrysaor (Reprint)

    Source 1

    Source 2

    Share.

    NeoArkadia is the 2nd Number of "The Organization" and a primary article writer. They are also an administrator for the forum Neo Ark Cradle.

    Related Articles

    5 Comments

    1. Samurex on

      I hope these aren’t just reprints of popular/anime decks and we actually get support for these. Pandora getting printed to take a level 7 Galaxy would be fun, and support both Chaos Galaxy and Voidvelgr

      • N on

        Voidvelg/DARK Galaxy was a low tiered deck in mid-late 2022 iirc so it makes sense for them to be reprinted in here.
        With that said, I fully agree we will likely get a new card for them in here, just as we got for Excutie with its reprints.
        1-2, and 25-52 should be the new cards in the set. It’s going in order of Rush anime, Rush anime legacy, Gallop anime legacy, and Rush original, with all Fusions, then all Main Deck Effect, and then finally all Spells/Traps.
        There is room for 2 more Rush anime Fusions and 11 more anime Effect monsters in this set. Any of this could go for Voidvelg.

    2. Bruno Santo on

      While I don’t recall Voidvelg having as long-lasting an impact on the Meta as Excutie, Dragoncaster, or even Rush’s Gaia, judging by the Reprints, this seems to be a reference to the Zwijo’s Duel that occurred at the end of GO RUSH’s Season 1.

    3. Paradigm on

      Unrelated to the news post but is it just me or is Yugipedia a bit broken right now? The layout is busted and half the links don’t work.

      • Bruno Santo on

        Yugipedia seems to have been experiencing issues for the past four days.

        In those days, the Web Server would occasionally crash and not recover until hours later. The issue became more common as the days went by.

        I have no idea what the problem was: a technical issue or a Database problem?