Here we are six months into this blog and there hasn’t yet been a post dedicated to the game’s namesake robot! Unlike a majority of roguelikes you don’t start the game by selecting a race, class, or anything else. You play Cogmind, more or less a “naked robot core,” and are quickly defined by what […]
As we transition from internal developments to content creation, let us first present an overview of how most of that content is organized. Cogmind is an example of the “open data” model, wherein as many content-specific parts of the game are exposed in public files anyone can open up and read/edit with a text editor. […]
Cogmind is edging into a new phase of development, that all-important part of making a game called “making a game!™” Naturally any game needs an engine to build it with (some devs skip this phase entirely if there’s something out there that can already do what you want, e.g. Unity3D), but a lot of unfinished […]
Continuing on the concept touched upon in the previous post about message logs in roguelikes, shifting the player’s attention from log to map works in tandem with making more information available directly on that map. I like to summarize this kind of feature with the phrase “map dynamics” (from a UI perspective, not map layout), […]
Arguably the most vital part of a traditional roguelike’s interface, a message log gives the player all those details that might otherwise be depicted by (or lost in the confusion of) greater graphical detail. It’s also a nice after-the-fact record of why you find yourself flirting with the brink of death when things suddenly start […]
RSS (posts)
Mastodon
Patreon
Discord
/r/Cogmind
Indie DB