search

fluffymuffin27 / take10

P2P Tabletop RPG Engine
GNU Affero General Public License v3.0
3 stars 2 forks source link

UI Mockups for Character Generator Pages #3

Open fluffymuffin27 opened 8 years ago

fluffymuffin27 commented 8 years ago

Qt5 has pretty good support for Wizards that allow for page-by-page self-verifying object creation workflow.

We need our designer @IMPrager draw/make some UI diagrams/mockups for the Wizard.

Currently I have the following mockups for reference (not final!):

1 2 3 4 5

Critique/discuss!

hamiltonium commented 8 years ago

Suppose the player gets 10, 14, 12, 8, 13, 10. At that point, I think the player should have the ability to decide which score gets which roll. For example, with the numbers above, they could choose to have charisma be 8 instead of wisdom.

fluffymuffin27 commented 8 years ago

@hamiltonium Right now the UI doesn't really support score re-assignment. This complicates things because that means that there are essentially three workflows to score creation:

1) Assign the generated scores automatically 2) Assign the generated scores manually 3) Manually input the scores (e.g. if you already have an existing character)

IMPrager commented 8 years ago

ui 1 ui 2

Here are the UI mockups. I added pages for class and feat selection. I didn't draw up a "Conclusion" window, nor an "Introduction" one, as I felt like the current examples of both didn't need to be changed.

A clarification of meaning: when discussing feats and skill ranks, I note that if a player puts levels in a prestige class then any feats and skill ranks required as prerequisites for that class should be "reserved", i.e. from the player's pool of feats and skill ranks the minimum required for the prestige class should be allocated.

It's a bit tricky and perhaps unwieldy, but it's one of the side effects of working in a forced linear direction like this in character creation. Normally, after ability scores, the rest of character creation can be done in any order, and indeed is often best done by jumping around between the various attributes and choosing what's needed one selection at a time. Proceeding one step at a time like the current model thus naturally creates conflicts such as this.

That's all for now. Apologies for taking so long, I had a busy week. Let me know if my handwriting is hard to read anywhere or if you have questions. Cheers!

EDIT: photos were upside-down for some reason and were inexplicably fixed by a reupload.