Skip to content

Document everything a proper game engine needs #73

Closed

Description

@Av3boy

With the currently known materials, gather every major piece as an issue so it can be prioritized.

This issue can be completed once all major sources have been verified and issues created.

Activity

  1. self-assigned this
    on Apr 13, 2025
  2. moved this to In Progress in A sharp planon Apr 13, 2025
  3. moved this from In Progress to Done in A sharp planon Apr 17, 2025
  4. reopened this on Apr 17, 2025
  5. Av3boy commented on Apr 17, 2025

    @Av3boy
    OwnerAuthor

    All the main components here should now be documented as issues
    https://www.gameenginebook.com/figures.html

    Core systems such as assertions, parsers or memory allocations will not be implemented since those should be handled by the .NET ecosystem and not the engine itself. Using tools built into IDEs and thrid party packages will be mostly relied on so we are not reinventing the wheel at this point. Once the engine has really been fleshed out we can revisit the idea of implementing such components ourselves.

  6. added
    documentationImprovements or additions to documentation
    editorChanges related to the Editor
    coreThe issue is related to the Core library.
    spikeSomething that needs investigation / needs an answer
    on Apr 17, 2025
  7. added 2 commits that reference this issue on Apr 17, 2025
  8. added 3 commits that reference this issue on Dec 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

coreThe issue is related to the Core library.documentationImprovements or additions to documentationeditorChanges related to the EditorspikeSomething that needs investigation / needs an answer

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions