So maybe something like this? Pack (when this enters the battlefield, reveal cards from top of library until you reveal a card that shares a creature type, put revealed card in hand and rest on bottom in random order)

Could be like amplify and not mention the creature type, but just use any "creature that shares a creature type with this".

Would depend on whether you'd want this on noncreature cards.

That way you wouldn't need to come up with a name for the mechanic that can incorporate the creature type though.

New idea for an ability. Wolfpack is a placeholder name as it would be a tribal ability so you could have Elfpack, Goblinpack, etc. Need to come up with a better name.

GUB Kraken commander for whelming wave style deck.

You are correct, the first -2 was ever really only there until I could think of something better.

I wouldn't give it two different mana abilities. That seems like a waste to me on a card that already took five colors to cast.

First draft of what's probably an impossible card - a five color planeswalker that isn't broken. Was going to make it useable as your commander as well, but theres enough text already. Also played around with giving 5 loyalty abilities but again, room.
Initial thoughts?

OK I think this is all formatted correctly now

The reason Dance of Many doesn't copy tokens is because the oldest wordings were very terrible and the errata/Oracle text reflects a reproduction of its function rather than its fundamental concept.

Design is form and function. Just reproducing the form without understanding the purpose is weak design. The form is a result of old rules/minds not handling it to well if a Dance of Many token becomes a copy of another Dance of Many token. Since this new design does explicitly aims to eliminate "token creation shenanigans" the whole reason "nontoken" would be introduced into the wording is gone.

It's now a form without purpose.

To avoid accidentally copy-pasting wrong cardnames it is advisable to use ~ rather than cardnames. The character is automatically replaced with the name of the current card in rules text.

You correctly put the enchantment type into the "except" clause of the copy-ability, because you realize copying would overwrite the card's types otherwise. You seem to miss that the copying also overwrites abilites.

The triggered ability defining the upkeep cost would be overwritten as this becomes a copy. It should also be moved into the "except"-clause.

Dance of Many can't copy token creatures, which I think is why Camruth left non-token on his version of the card ("Choose target creature card" infers that the Dance can only target things that are cards.)

I think what Camruth was trying to say is that he streamlined Dance of Many. Instead of DoM making a token creature that's a copy of something, and the enchantment or the token going away if their counterpart hit the bin, which meant that with the copy trigger on the stack that you could get a bonus creature with a well-timed Boomerang or Time Elemental activation... instead of that unintuitive madness, the enchantment becomes a copy of the creature. Which is pretty normal now, but cards changing types wasn't a thing in The Dark.

Though, for what it's worth, I'd probably get rid of non-token on Dance of Forms. I understand wanting to keep the enchantment as close to the original as possible, but this is just a clause that will trip people up for no clear advantage.

Two editing notes: "You" isn't capitalized. And the second paragraph reads "Dance of Many" instead of "Dance of Forms".