[fixed]Lodestone Bauble: nothing happens, multiple ways

[Korath]

Describe the Bug:

1. Lodestone Bauble can't be activated unless at least one player has at least one basic land in his graveyard.
2. If you try to target fewer than four basic lands (including if there aren't that many), activation is cancelled.
3. If you do target four basic lands, nothing happens at resolution.

(For both B and C, I only tried with basic lands in my own graveyard, though I can't imagine it makes a difference.)fixed

Which card behaved improperly?
Lodestone Bauble.

Which update are you using? (date, name)Which type? (duel, gauntlet, sealed deck)
Dev master head, 183dd0e.

What exactly should be the correct behavior/interaction?

1. Zero is "up to four".
2. One, two, and three are also "up to four".
3. Any targeted lands that are valid at resolution are put on top of the player's library, and unless at least one was targeted and none was valid, that player slowtrips.

Are any other cards possibly affected by this bug?
What I was actually trying to test, and couldn't, was this appalling ruling:
10/1/2008: "Up to four" means zero, one, two, three, or four. If you choose zero targets, you still choose a player. That player will draw a card at the beginning of the next turn's upkeep.

I can't think of any other card that depends on the properties of targets that were never even chosen.

[Aswan jaguar]

Fixed all the above in commit 2459b38e.
It still has another bug that even if you target opponent's graveyard it opens your own graveyard and also you get to draw a card and not target opponent. It works fine if controller targets himself.

EDIT: isn't Footbottom Feast and co the same (with similar ruling)- Put any number of target creature cards from your graveyard on top of your library?
10/1/2007 You can cast this with zero targets. If you do, you’ll get to draw a card. However, if you cast this with at least one target and all of those targets become illegal, the spell won’t resolve and you won’t get to draw a card.

[Aswan jaguar]

Fixed two last bugs above in commit 5c4fe52.