docs: correct spikersoft-angular in the beta README
spikersoft-angular@master projects/spikersoft/src/routes.ts:406 Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
1 parent
ee703e41ab
commit
ad7375c761
1 file changed
+8
-4
@@ -183,7 +183,7 @@ SpikerSoft.GameServer/ # Game server executable
|
|||||||
|
|
||||||
## Integrated Game Ecosystem
|
## Integrated Game Ecosystem
|
||||||
|
|
||||||
Three Angular game components share the same `SpikerSoft.GameServer` backend and form a single interconnected web-based MMO. Players transition seamlessly between experiences -- orbiting in space, terraforming planets with voxel blocks, and defending strongholds in dungeon combat -- all tied together through shared characters, resources, and progression.
|
Three Angular game components share the same `SpikerSoft.GameServer` backend and form a single interconnected web-based MMO. Players transition seamlessly between experiences -- orbiting in space, terraforming planets with voxel blocks, and defending strongholds in dungeon combat -- all tied together through shared characters, resources, and progression. The signed-in three.js routes are `/space-game`, `/wasm-voxel-game`, and `/rpg-game`. `/game` is the Godot client in the browser: the landing is public, and the page shows the game only to a signed-in player.
|
||||||
|
|
||||||
```
|
```
|
||||||
┌────────────────┐ ┌──────────────────┐ ┌────────────────────┐
|
┌────────────────┐ ┌──────────────────┐ ┌────────────────────┐
|
||||||
@@ -246,7 +246,7 @@ The three MMO games are not the whole games surface:
|
|||||||
|
|
||||||
- **Hex Tower Defence** — server-authoritative multiplayer tower defence. The TypeScript game reducer is ported to C# (`spikersoft-backend/SpikerSoft.Games.HexTowerDefence/`) and compiled into the API, with its own SignalR hub at `/hubs/hex-tower-defence` (it does **not** use the GameServer). Frontend lib: `spikersoft-angular/libraries/game/hex-tower-defence/`. Its buildings and enemies can be reskinned with Art Studio assets ([Asset-to-Game Integration](#asset-to-game-integration)).
|
- **Hex Tower Defence** — server-authoritative multiplayer tower defence. The TypeScript game reducer is ported to C# (`spikersoft-backend/SpikerSoft.Games.HexTowerDefence/`) and compiled into the API, with its own SignalR hub at `/hubs/hex-tower-defence` (it does **not** use the GameServer). Frontend lib: `spikersoft-angular/libraries/game/hex-tower-defence/`. Its buildings and enemies can be reskinned with Art Studio assets ([Asset-to-Game Integration](#asset-to-game-integration)).
|
||||||
- **Chess** — see [Chess Game](#chess-game); pieces can be Art-Studio-generated sets.
|
- **Chess** — see [Chess Game](#chess-game); pieces can be Art-Studio-generated sets.
|
||||||
- **Routed mini-games** — `/deploy-defender`, `/github-sweeper`, `/snake-scroller`, `/commit-snake`, `/duality-game`, `/hexatile-game`, and `/perfidy` (an alias of the snake game). Registered in `projects/spikersoft/src/routes.ts`.
|
- **Routed mini-games** — `/deploy-defender`, `/github-sweeper`, `/github-snake`, `/snake-game`, `/snake-scroller`, `/commit-snake`, `/duality-game`, `/hexatile-game`, `/clue-for-sql`, and `/perfidy` (an alias of `/snake-game`). Registered in `projects/spikersoft/src/routes.ts`.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
@@ -1364,6 +1364,10 @@ Staff sees badge → opens System Issues page
|
|||||||
|
|
||||||
All endpoints require authentication and an `Admin` or `Staff` role.
|
All endpoints require authentication and an `Admin` or `Staff` role.
|
||||||
|
|
||||||
|
### Scheduled Tasks
|
||||||
|
|
||||||
|
The same page has a **Scheduled Tasks** tab. Staff create, edit, pause, resume, trigger, and delete recurring or one-time tasks through `api/admin/scheduled-tasks`. The tab also downloads the GeoIP database when it is not already available.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Profile & Travel
|
## Profile & Travel
|
||||||
@@ -1668,7 +1672,7 @@ Chess pieces can be replaced with **Art-Studio-generated 3D sets**: a chess-set
|
|||||||
The `/team` route displays profiles of enabled Keycloak users in the `staff`, `admin`, and `guide` realm roles (E2E test personas are excluded). Profiles are fetched from those roles, then merged with MongoDB `UserProfile` data (avatar, handle, bio).
|
The `/team` route displays profiles of enabled Keycloak users in the `staff`, `admin`, and `guide` realm roles (E2E test personas are excluded). Profiles are fetched from those roles, then merged with MongoDB `UserProfile` data (avatar, handle, bio).
|
||||||
|
|
||||||
- **Backend**: `TeamController` (`GET /api/team`) calls `KeycloakAdminService.GetRoleMembersAsync()` to list role members, then joins with the `user-profiles` collection.
|
- **Backend**: `TeamController` (`GET /api/team`) calls `KeycloakAdminService.GetRoleMembersAsync()` to list role members, then joins with the `user-profiles` collection.
|
||||||
- **Frontend**: `TeamComponent` uses `TeamService` to load members and displays them in a responsive glassmorphic card grid. Each card shows an avatar (or generated initials), name, handle, and bio excerpt.
|
- **Frontend**: `TeamComponent` uses `TeamService` to load members and displays them in a responsive glassmorphic card grid. Each card shows an avatar (or generated initials), name, handle, bio excerpt, and position badges when the profile has positions.
|
||||||
|
|
||||||
| File | Purpose |
|
| File | Purpose |
|
||||||
|------|---------|
|
|------|---------|
|
||||||
@@ -2146,7 +2150,7 @@ All endpoints require authentication.
|
|||||||
|
|
||||||
## Blog System
|
## Blog System
|
||||||
|
|
||||||
Members create travel and learning blog posts that can link to a geographic fact. A draft stays a draft. Verified adults, and minors whose parent pre-approves posts, publish immediately. Other minors, and authors with no profile, wait for staff review. Uploaded media passes through an async processing pipeline.
|
Members create travel and learning blog posts that can link to a geographic fact or to a book. A draft stays a draft. Verified adults, and minors whose parent pre-approves posts, publish immediately. Other minors, and authors with no profile, wait for staff review. A post can also be archived or hidden. Staff hide a post and can unhide it, which restores the status it had before. Uploaded media passes through an async processing pipeline.
|
||||||
|
|
||||||
### Moderation Workflow
|
### Moderation Workflow
|
||||||
|
|
||||||
|
|||||||
Reference in new issue
Block a user