phoenox/dorc

D'Orc

Have a look at it here: https://phoenox.github.io/dorc/

Running it locally

Execute the following steps:

1. git clone this repo
2. cd client
3. dotnet watch run

A new browser window should now have opened, presenting you with either a security warning or the d'Orc start page.

dorc's Issues

Make FATE-esque Character Sheet Components Reusable

As a developer maintaining the application,
In order to make all FATE-based character sheets benefit from improvements to the Core components,
I need a way to reuse those components in derivative FATE-based character sheets.

NOTE: This is about the web UI, not the underlying character model.

Character: Delete Buttons

As a RPG player, I'd like to be able to delete a selected character (maybe a small red button next to "open"), and to delete all characters.

Character: Improved Picture Functionality

As an RPG player, I'd like to add more than one picture.

As a developer, I'd bet by left mouse button we have something like a picture gallery available in MUD Blazor. :)

Character: Add Image

Lazy load assemblies

Slowly but steadily, we get more and more modules, and I'm also planning a dedicated module for the GM.
However, not every user will need this functionality.
Currently, we download all assemblies for the user, which means increased loading time and required space for our application. It would be better if the initial application is rather small, and loads modules only if requested by the user.
For this, we probably need some settings where one can configure which modules and which systems one needs.
(In the future, I could also imagine a system that detects which module is required and asks the user if it should be downloaded.)

Information about lazy loading in Blazor WASM can be found here: https://docs.microsoft.com/en-us/aspnet/core/blazor/webassembly-lazy-load-assemblies

Fate Core System: Add Default Skills on Character Creation

It would make sense to have the standard set of FATE Core skills added upon character creation.

Discuss: Do We Want To Support Other Entities Than Characters?

As a GM, I'd like to create stats for entities like planets, magic items, or societies.

Conceptually, it's nothing more than a character with a varying amount of aspects and without stress bars. So for the time being, we can use the character module for this.

I'm just leaving the ticket here to think about this for a while. :)

Character: Export/Import Option

As a player or GM, I'd like to "pack up" a character and send it over to somebody else to import it, to facilitate the exchange of ideas.

As a developer, I see the following options:

1. "Export" Button -> display JSON -> "Import Button" -> "Import" Dialog opens -> copy JSON into dialog -> Click "Accept".
2. The current character URL could be enriched with parameters representing the state of the character. Saving a character would be a simple bookmark action in the browser, and sharing a character would be as simple as copying the url. This could be combined with the current browser storage implementation by treating characters not present in the browser storage as non-permanent (maybe offering a save button).
3. The classic user account backend storage stuff with share functionality.

Character: Generate Print View

I'd really like a print(able) view for generated characters.

For the initial version, nicely-formatted HTML would be fine. That can then be printed on paper, or put through a PDF printer.

PDF creation would be really awesome, but that'd be step 2.

FATE: Support custom stress bars

Example: Heat stress for Mechs in Mechwarrior

Not sure if this will go into the fate system or a separate system. Code-wise, ome kind of mixin might be nice. E.g. a Mechwarrior-Character inheriting from the fate character and adding (through composition) a custom stress "module" (object, struct, whatever gets the job done well).

CoreWarrior System and Character

As an RPG player, I'd like to play a homebrewn addition to FATE Core based on the BattleTech universe, in which the MechWarrior RPGs take place.

Follow-Up ticket to #6