Bge
D 59 completed
Other
infrastructure / csharp · small
407
Files
26,560
LOC
0
Frameworks
9
Languages
Pipeline State
completedRun ID
#1544067Phase
doneProgress
0%Started
2026-04-16 22:29:09Finished
2026-04-16 22:29:09LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
63.33Framework unique
—Isolation
—Last stage change
2026-05-10 03:34:51Deduplication group #61695
Member of a group with 2 similar repo(s) — canonical #557757 view group →
Provenance: Repobility (https://repobility.com) — every score reproducible from /scan/
🧪 Code Distillation
Browse all specs →AI Prompt
Create a simple, hobby-grade browser game engine using .NET 10 and Blazor WebAssembly for the Single-Page Application. The engine should support game properties where players have resources, assets, and units, and resources grow every game tick. The goal should be to maximize a primary resource and rank highly. For persistence, serialize the entire in-memory game state as a blob to storage, ideally on shutdown or periodically. The design should aim for simplicity over scalability and be generic enough for different game definitions.
csharp blazor dotnet webassembly game-engine browser-game hobby-project state-management
Generated by gemma4:latest
Catalog Information
Create a simple, hobby-grade browser game engine using .NET 10 and Blazor WebAssembly for the Single-Page Application. The engine should support game properties where players have resources, assets, and units, and resources grow every game tick. The goal should be to maximize a primary resource and rank highly. For persistence, serialize the entire in-memory game state as a blob to storage, ideally on shutdown or periodically. The design should aim for simplicity over scalability and be generic
Tags
csharp blazor dotnet webassembly game-engine browser-game hobby-project state-management
Quality Score
D
59.2/100
Structure
63
Code Quality
84
Documentation
50
Testing
15
Practices
62
Security
66
Dependencies
60
Strengths
- CI/CD pipeline configured (github_actions)
- Consistent naming conventions (PascalCase)
- Low average code complexity — well-structured code
- Containerized deployment (Docker)
- Properly licensed project
Weaknesses
- No tests found — high risk of regressions
- Potential hardcoded secrets in 1 files
- 1649 duplicate lines detected — consider DRY refactoring
- 1 'god files' with >500 LOC need decomposition
Recommendations
- Add a test suite — start with critical path integration tests
- Add a linter configuration to enforce code style consistency
- Move hardcoded secrets to environment variables or a secrets manager
- Address 28 TODO/FIXME items — consider tracking them as issues
Languages
Frameworks
None detected
Symbols
variable10
function3
Embed Badge
Add to your README:
