- Astro 53.4%
- TypeScript 45.1%
- JavaScript 1.5%
| .vscode | ||
| public | ||
| src | ||
| .gitignore | ||
| astro.config.mjs | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
Scorimundi
World born from fire and ash
The Scorimundi Frontend is open source, because I think it is important that open systems are one way to get feedback in.
NOTE: This Project is the second iteration of scorimundi and far off from being usable. Currently I am finding new ways to represent data of character sheets without having to force users into the same template.
If you got the link to the Project or Forgejo from me
Hey. I am thankful that you are looking into my project(s).
Maybe you would like to know why this project is "fresh" or why the commits here are infrequent. This repository is the 4th attempt on building a system that will make dice at the D&D/Pathfinder Table obsolete, while the previous iterations weren't to my liking I think I have an idea on how to make a system that rivals every character sheet manager on the market. The commits here are infrequent because I really have to think here, this isn't some "make it once and throw it away" project, this is a project that requires an immense amount of planning to make a tool that can do everything while not introducing techinical debt.
There are already plans on monitization and growth up to a usage count of 5 active million users. Of course while keeping everything within europe to ensure GDPR compliance.
It will take approximately 6 months to a year to get to a point where the first character sheet is possible. My estimation that the tool ecosystem will be marketable in 2 years.
AI Tooling in this Project
I avoid using AI on this project, mostly because this project is too complex to comprehend for a usual developer and I cannot afford having code somewhere that I do not know by heart. Yes, this is a project where it is essential that I have knowledge of how everything works line by line because there isn't any refactoring budget. If this project needs to refactored it will be easier to scrap it entirely and start anew because it just takes too much time.
The only thing that AI can help with are boilerplating tasks at most, which are prompts like "I created a dummy with specific filename, create dummy files just like that". Which are tasks that AI saves time on, but I could just do them myself and save me the cents.
Saw the older version?
If you saw the older version of scorimundi, near none of the features will be the same on this version. It has architectural reasons why this version will be different.
The entire new scorimundi project bases on multiple domain specific languages, some visual and some text. If it reaches 1.0 there won't be any static structures left. That is exactly what makes this project difficult, because every line of code here will have multiple meanings in the long run.
The old version was only able to save a D&D character sheet without any additions.
How the Proto Design System works
The proto desing is based on the following interfaces, which define how the protocol works.
export interface BaseStatNode {
id: string;
slug: string;
title?: string;
type: NodeType;
leaves?: Array<StatNode> | Array<string>;
parentId?: string | null;
metadata?: Record<string, unknown>
}
export interface PrimitiveNode extends BaseStatNode {
title: string;
type: 'primitive';
value: any;
}
export interface ComponentNode extends BaseStatNode {
type: 'component';
leaves: Array<StatNode> | Array<string>;
metadata?: {
role?: ComponentRole
}
}
export type StatNode = PrimitiveNode | ComponentNode;
Basically there a primitives, which are directly or indirectly rendered on the UI and components that encapsulate other Nodes. A Node Based System. By default the system is meant in a way that Nodes are written recursive and parsed as a flat object.
The recursive set is what will be saved in a document storage, tho I haven't decided yet if I use MongoDB or CouchDB.
A recursive Node Character Sheet Set might look like that. (I left some stuff out so it's not that much too read.)
var characterPreload: CharacterView = {
name: "Paul the Paladin",
stats: [
// --- 1. COMBAT & VITALITY BLOCK ---
{
id: "vitality",
slug: "vitality",
title: "Combat & Vitality",
type: "component",
leaves: [
{
id: "vitality.hp_current",
slug: "hp_current",
title: "Current HP",
type: "primitive",
value: 28,
},
{
id: "vitality.hp_max",
slug: "hp_max",
title: "Max HP",
type: "primitive",
value: 32,
},
{
id: "vitality.temp_hp",
slug: "temp_hp",
title: "Temp HP",
type: "primitive",
value: 5,
},
{
id: "vitality.ac",
slug: "ac",
title: "Armor Class",
type: "primitive",
value: 18,
},
{
id: "vitality.speed",
slug: "speed",
title: "Speed (ft)",
type: "primitive",
value: 30,
},
{
id: "vitality.proficiency_bonus",
slug: "prof_bonus",
title: "Proficiency Bonus",
type: "primitive",
value: 2,
},
],
},
// --- 2. ABILITY SCORES BLOCK ---
{
id: "stats",
slug: "attributes",
title: "Ability Scores",
type: "component",
metadata: {
role: "stat_group",
},
leaves: [
// Strength Box
{
id: "stats.str",
slug: "str",
title: "Strength",
type: "component",
leaves: [
{
id: "stats.str.score",
slug: "score",
title: "Score",
type: "primitive",
value: 16,
},
{
id: "stats.str.mod",
slug: "mod",
title: "Modifier",
type: "primitive",
value: 3, // Calculated via DAG later: floor((score - 10) / 2)
},
],
},
// Dexterity Box
{
id: "stats.dex",
slug: "dex",
title: "Dexterity",
type: "component",
leaves: [
{
id: "stats.dex.score",
slug: "score",
title: "Score",
type: "primitive",
value: 10,
},
{
id: "stats.dex.mod",
slug: "mod",
title: "Modifier",
type: "primitive",
value: 0,
},
],
},
// Constitution Box
{
id: "stats.con",
slug: "con",
title: "Constitution",
type: "component",
leaves: [
{
id: "stats.con.score",
slug: "score",
title: "Score",
type: "primitive",
value: 14,
},
{
id: "stats.con.mod",
slug: "mod",
title: "Modifier",
type: "primitive",
value: 2,
},
],
},
// Charisma Box
{
id: "stats.cha",
slug: "cha",
title: "Charisma",
type: "component",
leaves: [
{
id: "stats.cha.score",
slug: "score",
title: "Score",
type: "primitive",
value: 15,
},
{
id: "stats.cha.mod",
slug: "mod",
title: "Modifier",
type: "primitive",
value: 2,
},
],
},
],
},
// --- 3. SKILLS BLOCK ---
{
id: "skills",
slug: "skills",
title: "Skills",
type: "component",
leaves: [
{
id: "skills.athletics",
slug: "athletics",
title: "Athletics (STR)",
type: "component",
leaves: [
{
id: "skills.athletics.proficient",
slug: "proficient",
title: "Proficient",
type: "primitive",
value: true,
},
{
id: "skills.athletics.total",
slug: "total",
title: "Total",
type: "primitive",
value: 5, // stats.str.mod (3) + prof_bonus (2)
},
],
},
{
id: "skills.perception",
slug: "perception",
title: "Perception (WIS)",
type: "component",
leaves: [
{
id: "skills.perception.proficient",
slug: "proficient",
title: "Proficient",
type: "primitive",
value: false,
},
{
id: "skills.perception.total",
slug: "total",
title: "Total",
type: "primitive",
value: 0,
},
],
},
],
},
],
};
The Project already shows that the system in itself would work for the purpose, tho there are still a lot of things I see as challanges along the road.
Maybe in a few days, I can show how a finished view looks like when rendered. Tho there are a lot of components and systems that have to be written yet to have basic use.
Math
I will use again math.js, because I found it to be quite reliable. Tho i will have to modify it a lot more.
Scripting
It is not yet planed that the fronend will have custom scripting, tho if it at some point does it will be based on lua.