Collectible Card Game Headquarters

Describe the Bug:
City in a Bottle is affected by itself

Which card did behave improperly ?
City in a Bottle

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
Jan 01, 2014 : Commanding the revision of Ice Age v2 - DUEL

What exactly should be the correct behavior/interaction ?
City in a Bottle is not affected by itself

Are any other cards possibly affected by this bug ?
-

The bug is confirmed.
I may be wrong but from the words phrasing I understand that only one can be on the battlefield so it is correct not to allow other City in a Bottle to be cast as itself belongs to Arabian Nights set.(maybe it is coded like this but can't test since even the first goes straight to the graveyard when cast.

I'm not sure what the correct behavior is, but right now it looks like the second city stays in play.

This also affects tokens and doesn't affect Brass Man or Dancing Scimitar. (all three fixed in 4246e36)

It's also supposed to be a continuous effect, but is only checked as it comes into play. There isn't really a good time to check this; the usual comes-into-play trigger is inappropriate, since it still has to kill e.g. a Kird Ape that was temporarily a copy of something else (say, via Cytoshape) when the City came into play and did its initial check. Maybe when there's a framework for making auras fall off correctly.

Golgothian Sylex hits tokens too, and isn't affected by ability cost modifiers, but is otherwise ok. (both fixed in df4a7a6)

Static effect added in f62a725.

City in a Bottle is now affected by itself and static effect works, and Brass Man, Dancing Scimitar and tokens work right.

But, it doesn't prevent cards from being played. You can cast spells from Arabian Nights, they just immediately get sac'd.

Missing Flags:Play Cost in ct_all.csv.

Csv update has been made and verified (and, in general, these don't need to be left open; we put an entry in our make-sure-this-gets-edited-before-next-release file in this sort of case).