Collectible Card Game Headquarters

Describe the Bug:
Invoke Prejudice is treated as a World Enchantment (whenever another World Enchantment or Invoke Prejudice is cast the first on is destroyed).

Which card did behave improperly ?
Invoke Prejudice

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
2014/02/18: Born of the Gods v2 - DUEL

What exactly should be the correct behavior/interaction ?
It isn't a World Enchantment.

Are any other cards possibly affected by this bug ?
-

It needs ct_all update as it is wrongly marked as world enchantment.But it also needs some code fix as even when I fixed the ct_all entry it got fixed only partly = it doesn't get destroyed by another Invoke Prejudice coming into play or a world enchantment come into play BUT if Invoke Prejudice comes to play will still destroy any world enchantment that is on the battlefield.

It isn't marked as a world enchantment in release or dev csvs. Fixed the spurious call to enchant_world() in cbd7620.

So does that fix it, or are you still investigating?

Korath wrote:
It isn't marked as a world enchantment in release or dev csvs

I am curious which value are you looking at?Because just rechecked and in v2 February the value is set and at my tests it did make a difference (I believe) if it was marked or not.

> grep 'Invoke Prejudice' magic_updater/manalink.csv
685;Invoke Prejudice;1;Invoke Prejudice;|U|U|U|U;100h;2;2;2;0;0;4;0;0;0;1;0h;0;0;0;0;0;0;0;1002h;-1;-1;-1;-1;-1;-1;211;211;0;Enchantment;Whenever an opponent casts a creature spell that doesn't share a color with a creature you control, counter that spell unless its controller pays |X, where X is its converted mana cost.;"";"";"";"";"";"";0;0;0;0;0;0;0;1;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;100;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;-;C;-;-;-;C;C;-;-;-;-;-;-;-;-;R;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;-;""

Enchant world is, variously, 16 (or 0xF) in Family, 205 in Subtype and Subtype 2, and/or 0x2004 in New Types; I don't remember which offhand that enchant_world() looks for. This has -1, 211 (none) and 211, and 0x1002 (Enchantment). Compare Concordant Crossroads. And yes, it's fixed.

The one set by Mok and was looked for was the family value in ct_all - 16 - .And in bngv2 ct_all.csv it is set in 16.You have pasted the values of Manalink.csv not of ct_all.csv.

Shouldn't make a difference either way with the function call gone, but I've marked it for update just to be sure.