search

Melindrea / exalted-platform

Discussions about functionality for an exalted platform. Both somewhat technical discussions and just "good to have"
0 stars 0 forks source link

Back End Database Modeling #1

Open dblmagus opened 11 years ago

dblmagus commented 11 years ago

I'd suggest utilizing Django to create the objects, just due to the transferability of design. It doesn't matter which database you use, or if you are using the new and fancy memcache d stuff (ooh fancy), you can just change it over by modifying a settings file then calling syncdb.On the plus side you can also use Django for the webpages, but its really not necessary at all.

Models that we'll probably need:

Character Attribute Abilities Charm Sorcery (assuming its not too different in 3rd edition) Merits (they replaced backgrounds with them in 3rd edition after all) Flaws (maybe? am assuming still around) Mutations (also still assuming they are around) Equipment (armor, weapon (close), weapon (ranged)) [Not sure if we want to separate out artifact from mundane]

Most other things about a character would be general note fields in the Character section. We will however need things to depend on Exalt Type (for example, favored/unfavored abilities vs attributes).

Additionally, we'll want to make a system where it is Easy to add in Customs, or at the very least, able to add in new things as charms are released in new books. I'd suggest creating an auto script that you can just fill out the fields and run it.

Melindrea commented 11 years ago

One thing that I'm finding important is to be able to use the system to import/export Anathema characters. We'll still need actual character changing/viewing, but Anathema is a good system.

dblmagus commented 11 years ago

So we'll need a Parser written first thing then (import being more important than export first). Once you have the parser, export tends to be pretty simple.