We have an abstract input system which should allow us to easily add more than one mechanism for input handling and easily switch between them.

Previously all of our input handling happened in the same class. The input handling code grew huge and ugly.

We refactored the old class into separate input handlers classes. Each input handler is responsible of handling one or many actions. In the base class of each input handler, we have events that notify other classes about any major activity that occurs in that input handler.

All the handlers live a control mechanism that handles the relation between the handlers and other classes that are interested in any info from those handlers.

Each control mechanism also has a control mechanism assistant which displays text and images to assist the player through the mechanism.

We can have more than one control mechanism, each would have a list of handlers, assigned from the inspector.

  • For creating a new handler, we should derive the handler from the action specified InputHandler class.
  • For creating a new mechanism assistant, derive your assistant from ControlMechanismAssistant.
  • For creating a new control mechanism, create a new game object, attach the ControlMechanism script and then assign the input handlers into the control mechanism’s handlers list and assistant in the assistant field.



Author PKaram
Views 48
War to the Core

Recent Comments

Latest Updates

  • Solo missions

    Solo missions

    Hey guys, here are the specifics of the first two solo missions, those are sketches of the first two missions. First mission: A harvester is placed near the ship, generating supply caches. The player collects energy caches and escapes a ring of mines. No supply links allowed. The sensor component is introduced by one of […]Read More »
  • We made it to the Top 100!

    We made it to the Top 100!

    We are stoked that we managed to land on IndieDB’s Indie of the Year’s Top 100 list! We are also the only MOBA that made it to the list! The support we got from the community was overwhelming, and we would like to thank each and every person that helped us get this far. Whether […]Read More »
  • Full Campaign Series, Version 3

    Full Campaign Series, Version 3

    Characters: Daniel Blaze. Protagonist, player-character. Headstrong and rebellious. Ambiguous loyalty to the Shepherd Coalition. Joseph Blaze. Father of Daniel Blaze. Commander of the Leviathan mothership until executed for treason by the Shepherd Coalition. Sylvia. AI assistant. Provides intel, advice, mission objectives. Captain Zhukov. Cyborg commander assigned to hunt down player during the first several missions. […]Read More »
  • Story: Episode 1, Version 2

    Story: Episode 1, Version 2

    The Blaze family had long been controversial. They supported the Shepherds, but continually frustrated the Orthodox elements of their faction. Joseph Blaze was especially known for his tolerance of the weakling families that used genetic engineering to alleviate the sicknesses that exposure to the Earth’s surface had inflicted on them. Such tensions between orthodoxy and […]Read More »
  • Story: Episode 1

    Story: Episode 1

    Location: The Pole Base. When Daniel Blaze passed his final test and became the primary candidate to pilot the Leviathan, the Shepherds’ newest ship, he caused a quite a stir. Not because he’s the youngest member of the Pole fleet to be nominated for admiralship, the faction had already made peace with this as a […]Read More »
Skip to toolbar