Trees vs Others

[Drguy ks]

Hey all, I'm doing a database for a game I play called Lego Dimensions. The game offers a wide variety of characters, each with their own powers. There are alternate costumes for some characters but not others. Here's where things get tricky: some characters have unique abilities, whereas others do not. To make matters more difficult, there is a finite number of powers that are programmed in. Also, two different characters alternate costumes can have the same ability. Example: Chase McCain (Miner) has Silver Lego Destroy & so does Mikey from the Goonies. However, Chase & Mikey CANNOT turn into each other. What’s the best way that I can represent their alternate costumes AND their abilities at the same time? I was thinking of using the tree field, but that may not be best.

[Er Mo]

Hallo

Ich würde ein " Link to entry " vorschlagen . In einer 2 Bibliothek die Fähikeiten ablegen und diese zum Karackter verlinken . So könnte man auch mehr Infos zu den Fähikeiten abspeichern .

Hello
I would suggest a "link to entry." Store the skills in a second library and link them to the character. This way, you could also store more information about the skills.

Ernst