need guideline for double sided cards

[mmougy]

Main scheme are double sided.
Some of them are described in the code as 2 different card (i mean 2 json objects)
but the display is not great, see Protect the Planet

Currently the display is much better when both sides are described in the same json object
seeThe Sentinel Factory - 1A

What is the correct guideline for main scheme?
and more generally What is the correct guideline for double sided cards?

Protect the Planet

The Sentinel Factory - 1A

this is linked to #464

[Kamalisk]

So the double_sided flag is when a card has the same type on both sides (and is the old original way we did scenario cards in arkham), when you use the double_sided flag, you also put the back_ fields into the json for the other side.

This worked great but did not for cards where the two sides were different card types entirely, so for those instead of using the double_sided flag, you instread create 2 entirely seperate cards (usually a and b), then link them to each other using back_link.

The issue is that people often put the double_sided flag and also use the back_link, this causes it to not display correctly at all.
Its entirely my fault for not documenting it.

as for the schemes, the "front" is A, and that is the side with the setup, and the "back" has the threat values. So I think the code is designed to flip that around, but the image names are often not the correct way around either, and it leads to a bit of a mess.

Either method is probably fine (I would stick to the double_sided method and not use back_link unless the back of the scheme is an upgrade or something).

[mmougy]

Thanks for the explanation

So the easy part is to clean up the code, removing double_sided property when using back_link : #550

[mmougy]

Regarding the inversions that happen often, here is what I noticed to help debug:

Most of main scheme use the double_sided method, and 100% of them use the "front" to describe the B face.
ex. Stalked by Sabretooth - 1A

Some main scheme use the back_link method, and use the "front" to describe the A face
ex. Terrestrial Invasion - 1A

I've found one card perfectly displayed: Formidable Foe
it uses the double_sided method, and use the "front" to describe the A face.
it is an environment type, maybe it explains something?

let me know if i can help

[Kamalisk]

It might be that it has always been the wrong way round.

[Kamalisk]

https://marvelcdb.com/card/01097 is displayed correctly, but that is because the side that should be A, has the image named B, so it stemmed from that I imagine, and images after the core set are named more correctly.

[mmougy]

I can invert front and back, for all side schemes using double_sided method

[mmougy]

The inversion behaviour is specific to main scheme type:

https://github.com/zzorba/marvelsdb/blob/e4cc2ca74fc5358c800d68112fcfe03a242c8382/src/AppBundle/Resources/views/Search/display-card.html.twig#L18

It is easy to fix on marvelsdb
but it will impact most pack files marvelsdb-json-data, and translation files

[mmougy]

I can invert front and back, for all side schemes using double_sided method

in fact it is a bad idea because the double_sided method does not support many properties:

• escalation_threat
• base_threat
• base_threat_fixed
  ...

The best solution is to use back_link method on all main schemes

• all properties could be supported for both sides
• the fix on marvelsdb: Remove main-scheme inversion marvelsdb#264
• the modification on marvelsdb-json-data is heavy and touches pack and translations use back_link on all main schemes #551
• 73 images should be to renamed (ex: 26002.jpg -> 26002a.jpg) ping me for the list if needed