Jump to content

Search the Community

Showing results for tags 'suggestion'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Hexters
    • Hexters FAQ
    • Hexters - General Discussion
    • Hexters - Developer Log
    • Hexters - Suggestions & Feedback
    • Hexters - Bug Tracker
  • Triplane Turmoil II
    • Triplane Turmoil II - General Discussion
  • Tools
    • DIM - Draconus Icon Manager
    • DTU - Draconus Texture Utils
  • Music of Markku
    • musicofmarkku.com - General Discussion
  • Other & Off-topic
    • Off-topic
    • Forum & Community


  • Hexters articles


  • Hexters Bug Tracker


  • Files

Found 1 result

  1. Introduction I would like to give my general thoughts about skirmish mode for a colony building sim which are based on my experience of playing games in genres that include colony builders, RTS, squad tactic games, roguelikes/lites, and also chess. In my other post I argued that there should be at least two types of free play modes: an unwinnable sandbox style mode and a winnable, supremely balanced mode that can be won or lost. This post is about my thoughts on the latter mode and how I think it could incorporate select features of the roguelike. Please remember that all of this is only my opinion, even though it might read like a list of demands. I don't want to waste space by writing "I think that" or "In my opinion" before every single point I make , but I will differentiate what is fun for me from what I think is objectively better. I think that a skirmish mode needs replay value to be objectively good, if you will permit such an oxymoron, at least as it pertains to the quality of video games. Whereas a platform game or an RPG can be enjoyed on a single-play through and put away forever, a skirmish mode is better if it makes you want to play it again. A skirmish mode is akin to a board game like chess, which itself is almost like a "skill" because it demands mastery by the player. The genre of the roguelike (and its derivative form, the rogue-lite) is based around this idea of mastery, so essentially what I'm suggesting is a sort of hybrid between a roguelike or rogue-lite (such as Brogue or Faster-than-Light, respectively) and a colony sim. Applying Structural Features of the Roguelike to a Skirmish Mode The features of the roguelike are similar to those of a real-life sport. A roguelike (such as brogue) typically has the following properties: - A single "competitive" mode with settings that have ultimately been picked by the game developer. The unified mode is important because it forces players to adapt their play to the game rather than the other way around by tinkering with settings or whatever. It also sets a standard that can be used for seed competitions in order to build the community around the game, which can be quite important for sustaining interest and spurring further development of the game (see /r/brogueforum for an example). Personally, I don't prefer roguelikes that allow you to endlessly tinker with classes and other such initial values; the competition just feels somehow grander if you know that everyone else is starting off with the same conditions as you are. - Permadeath is probably necessary if the central theme of the game revolves around the player reacting to random events. While save-loading is fine for a sandbox mode or campaign mode, there isn't much point in even allowing saving as an option because it only tempts the player to cheat. If a save file is allowed to be reloaded after the player dies, then whatever results from further play should just be considered practice or void (i.e., the game drops from the skirmish mode back into sandbox mode). In Hexters, I suppose having your hub destroyed would be the death criterion. If there is no permadeath, then there needs to be some fixed duration over which the player must score as high as possible. - A simple win condition that is preferably a binary outcome (win or lose), possibly quantified by a single scalar value. Such a system makes tracking progress over a long series of games much easier. I think it's best if the game can either be won or lost, because it frees the player from having to play in a certain way. For example, if a roguelike had a score which was based on how many monsters were killed, then any stealth playstyle would be inferior to a fighter playstyle. If there is a score, then it should capture the essence of the game. In Brogue, the score is based on the amount of gold collected because exploration, not combat, is the central theme of the game. But the player also gets a large gold bonus for recovering the amulet. For Hexters, good candidates for the metric of score could be the amount of time survived, the peak power generation in watts, or the maximum number of hexters alive at once, because all of these are the core of the game. Regardless of what is used for scoring, the average score should be tracked over the last x games, whether it's simply the win percentage, or something more complicated. - A short game length (lasting from 90 to 150 minutes) follows if there is an expectation that the player is not going to win every game, there is permadeath, and the sole scoring metric is a binary outcome. If you have a 15-hour game, the threat that you're going to die at any point has to be reduced so that the player has a reasonable chance at winning, but this reduces the game from a series of gutsy strategic decisions to one of crossing t's and dotting i's. If there is a scalar scoring metric, then the game can be a bit longer. In addition to all of that, it's easier for humans to retain interest over a shorter period of time, no matter what the subject is. Any individual game is like a sports game or a piece of theatre. Although fans of cricket or Wagner might disagree, the average length to tell a good story seems to be 90 minutes to a few hours. Conclusion I actually had an entire second section to add, but since it brings in my experiences with other types of games besides roguelike (such as colony sims, strangely enough), I'll make a second topic for that. Hopefully this has provided some food for thought.