natty
/
plutoengine
1
0
Fork 0
Code Issues 11 Pull Requests Packages Projects Releases 19 Wiki Activity
My hobby game engine.
86 Commits 3 Branches 19 Tags 6.2 MiB
Java 92.7%
GLSL 5.8%
Kotlin 1.5%
Go to file
Natty d0f250752e
Fixed a bug in a demo's build.gradle.kts 		2022-04-06 14:41:12 +02:00
.github/workflows Updated publish workflow 2022-04-06 14:06:14 +02:00
buildSrc Fixed Maven and version bump 2022-04-06 14:29:35 +02:00
engine-core Fixed Maven and version bump 2022-04-06 14:29:35 +02:00
engine-demo Fixed a bug in a demo's build.gradle.kts 2022-04-06 14:41:12 +02:00
gradle/wrapper Fixed Gradle wrapper 2022-04-06 14:01:46 +02:00
.gitattributes SDK restructure, package reorganization, new ModLoader, new resource system 2022-04-06 11:04:32 +02:00
.gitignore SDK restructure, package reorganization, new ModLoader, new resource system 2022-04-06 11:04:32 +02:00
LICENSE SDK restructure, package reorganization, new ModLoader, new resource system 2022-04-06 11:04:32 +02:00
NEXT_RELEASE_DRAFT.md Fixed Maven and version bump 2022-04-06 14:29:35 +02:00
README.md Updated priorities 2022-04-06 11:04:32 +02:00
UPDATE_NOTES.md Fixed Maven and version bump 2022-04-06 14:29:35 +02:00
build.gradle.kts Fixed Maven and version bump 2022-04-06 14:29:35 +02:00
gradlew Fixed Gradle wrapper 2022-04-06 14:01:46 +02:00
gradlew.bat Fixed Gradle wrapper 2022-04-06 14:01:46 +02:00
settings.gradle.kts SDK restructure, package reorganization, new ModLoader, new resource system 2022-04-06 11:04:32 +02:00

README.md

plutoengine

My hobby game engine. This repository unifies all my previous Pluto repositories.

Versioning

All submodules share a version number for simplicity reasons.

Since version 20.2.0.0-alpha.0, PlutoEngine uses a combined version of semantic versioning and calendar versioning, the first number denotes the year.

Therefore, the version format is always YY.MAJOR.MINOR.PATCH-prerelease.

Only major and year version changes will bring breaking API changes, except for pre-release versions, which may introduce breaking changes at any time. Pre-release versions will never increment the minor or patch version numbers.

Usability status of submodules

Safe submodules

  • PlutoCore - Stable
  • PlutoFramebuffer - Stable
  • PlutoGUI - Stable, awaiting a rewrite
  • PlutoMesher - Stable
  • PlutoShader - Stable
  • PlutoTexture - Stable
  • PlutoSpriteSheet - Stable, some features are unfinished
  • PlutoDisplay - Stable, collision API nowhere near completion
  • PlutoUSS2 - Stable
  • PlutoLib - Mostly stable

Unstable submodules

  • PlutoRuntime - Somewhat tentative, the module API has been rewritten and might contain bugs
  • PlutoAudio - Somewhat usable, unfinished

Current priorities

See NEXT_RELEASE_DRAFT.md for details.

Very high priority

[ Implemented in the current release. ]

  • Streamline PlutoLib, remove bad APIs and improve code quality
    • Improve image loading capabilities, possibly rewrite PlutoLib#TPL
  • The stage system and automated asset loading
  • Rewrite PlutoGUI

High priority

[ Implemented in the next release. ]

  • Finish PlutoAudio
    • Depends on the stage system

Normal priority

[ Planned for an upcoming release. ]

  • The collision system for PlutoStatic

Low priority

[ Items not required immediately, planned to be implemented eventually. ]

  • Allow multiple running instances of Pluto
    • Alternatively, if this deems too difficult to implement, prohibit the creation of more than one instance per JVM to avoid issues
  • A networking API
  • Re-add support for external mod jars to the ModLoader
    • This feature requires a full rewrite and possibly a complete overhaul
    • Mods should have limited execution levels, for example restricted file access or disabled native library loading (this is probably not possible)
  • Expand upon the Color API
    • Color mixing and blending
    • Color transformation
    • High-performance serialization