Do they both die?

[PatientZero]

Parrelel lives and séance
Do both copies get removed because séance says "it" ?

[Poof]

If u had put the card in brackets I could read it but since I can't when I used to run parallel lives with mimic vat the copy made by parallel lives would stay while the other would get exiled.

[PatientZero]

 {Séance}

[PatientZero]

I know I get two copies but unsure if they both die at the end phase or just 1

[Silent1236]

I know I get two copies but unsure if they both die at the end phase or just 1

Yeah just realized I read the question wrong and I don't have an answer to the actual question .

[PatientZero]

No worries mate I don't either, that's why it's here.

[Redrighthand]

 {Séance} only kills the token that it creates. Any copies created by  {Parallel Lives} or by other token copying means, such as populate, would stay on the battlefield. There is another thread on here that talks about this scenario.

[PatientZero]

Thanks mate, only been playing for 8 months and the new mechanics are giving me some trouble with rulings.

[Gorzo]

Unfortunately Parallel Lives is different from populate. It causes the initial token creation effect to create additional identical tokens, including their additional clauses like exiling at the end step. Confirmed by the card rulings of parallel lives.

Populate gets around this by selecting a token in play and creating a brand new copy token of a different source (the populate card) that does not have this clause.

[Greg54js]

Unfortunately Parallel Lives is different from populate. It causes the initial token creation effect to create additional identical tokens, including their additional clauses like exiling at the end step. Confirmed by the card rulings of parallel lives.

Populate gets around this by selecting a token in play and creating a brand new copy token of a different source (the populate card) that does not have this clause.

Gorzo the only issue is the tokens themselves don't have that clause. Seance does.. Or at least that's how I read seance

[Fenster]

The ruling on {Parallel lives} specificly says that if something would happen to the token later ie exiled at eot the same happens to the additional token.
Case specific maybe but thats what it says.

[Greg54js]

The ruling on {Parallel lives} specificly says that if something would happen to the token later ie exiled at eot the same happens to the additional token.
Case specific maybe but thats what it says.

Ah might've helped if I still had my rules add on :( but it makes sense

[Gorzo]

The reason it works that way for parallel lives is that unlike populate and other copy mechanics, {Parallel Lives} itself does not actually create anything. Rather, it causes the original source of the token (in this case, {Seance}) to enter a state of overdrive, producing twice as many. Both tokens are being created by seance, thus both are subject to Seance's rules (exile at end step)

Populate creates a new body, however, that is in no way connected to the original source (the seance) so it is not stamped with the exile clause.

Hope that helps clear things up.

[PatientZero]

Ok so they both get poped, guess I'll just run 2 instead. Thanks guys.