A new C# framework for Unity with simple, single-file solutions.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Examples
Hunters
.gitignore
Examples.meta
Hunters.meta
LICENSE
LICENSE.meta
MAVERICK.cs
MAVERICK.cs.meta
README.md
README.md.meta

README.md

MAVERICK

A new C# framework for Unity with simple, single-file solutions.

BASIS

  1. Make everything accessible through a single variable: X (that is, MAVERICK.X).
    • This includes all MAVERICK classes, data, enums, interfaces, and methods (often via Core).
    • The only exceptions are MAVERICK.MAVERICK and MAVERICK.InternalExtensionMethods.
  2. Keep X as clean as possible for Extensions to use liberally.
    • Aside from Is(...) and MAVERICK_VERSION, restrict all built-in data/functionality to Core.
  3. Require the minimal amount of code to get from X to desired data/functionality.
    • Example: X.MAVERICK_VERSION X is a class (and not a namespace) so we can get to integer MAVERICK_VERSION.
    • Likewise, Extensions can make X contain fields and properties with data and object references.
  4. Allow an Extension or Hunter to be implemented using a single C# code file.

SETUP

  1. Add the MAVERICK component to a GameObject in your scene.
    • Preferably, put this in a scene that always loads at the beginning of the game/app.
  2. Add some Hunter prefabs to the MAVERICK's Hunter List.
    • A "Hunter" is simply a derived MonoBehaviour class.
  3. See MAVERICK_UseCase for usage examples.

ROADMAP

  • Add editor/menu controls for creating/adding different Hunters to MAVERICK.
  • Dictionaries (using string keys) for both Extensions and Hunters.
  • Assimilate KRG (https://github.com/KalebGrace/krg-for-unity) into MAVERICK.