Martmists-GH / Martmists-GH/GameEngine

Consider modularization

Open
#15 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

This might be unnecessary, but the idea is to have modules for:

  • Core
  • 3D physics extension
  • 2D physics extension
  • Networking (?)
  • Any other extensions that might be too big for most games that don't need it
  • Editor Application
  • Samples

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reviewing the repository structure and current module boundaries, then determine which proposed extensions belong in separate modules. Done would require an agreed modularization scope and boundaries for Core, physics, networking, the editor, and samples.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
game-dev
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.