Green Cloak Games
Roadmap
This page is here to give you a clear picture of what already works, what I am focused on next, and what I want these tools to grow into over time. I am not attaching fake dates to everything. Features move forward when they are ready and when they make sense for the framework.
Tile Tick Movement
Tile Tick Movement is already a complete deterministic movement package. Future updates are about improving the foundation, covering more project types, and fixing real problems found by people using it.
The same tick driven foundation can support more than RPG characters. I want to make it easier to use for other genres that benefit from predictable movement and clear simulation rules.
Smaller updates will continue to improve setup, performance, documentation, examples, and edge cases as the package is used in more real projects.
Tile Tick Core RPG
Core RPG already includes the major systems needed to start building a classic tile based RPG. The next stages are about making worlds larger, adding more gameplay depth, improving workflows, and preparing the framework for bigger projects.
Current direction
The framework has grown faster than the demo. My current focus is building a better example world that shows how the systems work together and gives new users a much clearer starting point.
I want building a world to feel as straightforward as placing the content inside it. The next world focused updates will connect spaces together more cleanly and reduce the amount of custom setup needed for common RPG interactions.
The combat triangle is already in place. Future combat work will focus on giving developers more ways to create interesting enemies, builds, weapons, and encounters.
The existing skill systems are built to be expanded. New skills will be added as full examples that developers can use, study, and adapt instead of as disconnected one off scripts.
NPCs should do more than stand in one place waiting for the player. Future AI work will focus on making towns, enemies, and other characters feel more alive while keeping their behavior understandable and configurable.
Larger worlds
The long term goal is to support worlds that can grow far beyond a single Unity scene without turning the project into a mess of manual loading logic.
I want developers to be able to build large overworlds, towns, interiors, and dungeons without loading everything at once. The plan is to introduce a clear streaming workflow that works with the existing grid, world state, saving, quests, NPCs, and interactions.
World streaming touches saving, quests, NPCs, pathfinding, interactions, dropped items, banks, and nearly every other persistent system. Building it after those foundations are stable means the streaming layer can support the actual framework instead of forcing every feature to work around an unfinished loading system.
Multiplayer
Multiplayer is one of the most requested additions and it absolutely fits this style of framework. It is also one of the easiest features to underestimate.
The goal is not to bolt a quick multiplayer script onto the package and call it finished. The goal is to build networking around the completed gameplay foundation so combat, movement, NPCs, quests, banks, inventories, world state, and future streaming all have a clear authority model.
Adding multiplayer before the gameplay systems are mature would make every new feature harder to build, test, and change. I am focusing on finishing and proving the core framework first, then networking the systems with a clear understanding of what data actually needs to be authoritative, persistent, and synchronized.
This also gives the future multiplayer work a better chance of supporting real projects instead of becoming a pile of temporary workarounds.
Long term vision
Tile Tick Core RPG is inspired by the structure and readability of classic online RPGs, but it is not meant to force you into recreating one specific game.
The goal is to give you the movement, combat, progression, world systems, editor tools, and workflows needed to build something of your own without starting every major feature from scratch.
Every update should make the framework easier to understand, faster to build with, and more capable without burying users under unnecessary complexity.
Using the tools already
If you keep running into the same workflow issue, bring it up in Discord. A clear problem from an actual project is far more useful than a giant list of disconnected feature requests.