I’ve been on a hiatus whilst dealing with some ongoing personal matters. I’m returning to work on Fate Looms, and I’ll still be posting here from time to time.
In some ways, Fate Looms is inspired by the neatly executed Power2ool, which is a monster, item and power card editor for Dungeons & Dragons 4th edition. Its minimal-obstacle editing method is one particular influence on the design of Fate Looms: one only needs to shift+click on a card in Power2ool to bring up a full editor of its contents. The demo video starts discussing that at 2:50.
It wouldn’t be as effective for the cards in Fate Looms to be edited exactly the same way, but the shift+click is useful. Consider the following card for Vince Noir:
It doesn’t look all that pretty at this point, but that’s further down the line.
When dealing with this card during the course of the game, most of your editing will be of single disparate sections here and there. This, you can do by shift+clicking on any portion of the character card:
Having a shift+click rather than just any click is necessary, otherwise it’d make it pretty hard to highlight or copy and paste stuff properly.
Aspects are a little different. You don’t edit just one part of them:
You edit the whole line at once. Anything before the first colon becomes bolded, and thus you can adjust the name or aspect type* at once. This Aspect is more of a High Concept, so let’s make it that:
and hit enter to save it (escape cancels).
If you’d rather not give the aspect a type, you can leave out the colon altogether and no part of the line will be bolded, leaving it just as: “Fashionable Prince of Nothing”.
If there’s multiple colons, only the first is treated in a special way and only the words before it are bolded: “Specialty: Power Word: Dance!”
* If there’s an official term for “Aspect”, “Trouble”, “High Concept” and so on, please let me know!
In terms of programming, this used a wonderful trick in Knockout’s features: it works with a custom data binding. It was tricky to work out how to handle approaches, until the obvious solution hit me a couple of weeks down the line. I’ll talk about the programming side more in another post.
Lesson learned: if I’m having trouble, focus on some other part of the project for a while rather than letting one part get bogged down and the whole thing have little progress. Whilst I’m busy doing that, the solution for another challenge might just occur to me out of nowhere, and the project’s still moving ahead even if it doesn’t.