With SKALD: Against the Black Priory entering the final days of a phenomenally successful Kickstarer, it’s time to squeeze in another article discussing game-play features and design.
Last time, we did some exploration into classes and stats. Today, the subject is the application of the classes and stats! In other words: “Combat and Adventuring”!
Just like in the “Classes and Stats” article, let’s start with some design pillars for combat and adventuring:
Respect the players time: SKALD is developed for a modern audience and this means allowing players to pick up the game, play a short session and still have a fun experience. This includes reducing book-keeping by adding features such as a journal system and auto-mapping, avoiding grindy areas of pointless content padding, making combat fast and having a forgiving save system that allows the player to save anywhere.
Allow the player to make informed choices: The game should be mostly transparent in how the rules work and how the characters class, stats and roleplaying choices interact with the world. If information is kept from the player there should be a good reason to do so.
Provide multiple solutions to quests: Quests should be solvable by non-combat means and players should be able to play non combat-oriented characters.
Choices matter: The world should be interactive and react to players choices.
Adventuring in SKALD takes one of fours forms:
- Combat (more on that later)
- Exploring the environment through the tile-based map
- “Choose your own adventure” sequences
You explore the game-world with a party of up to six characters. At the start of the game, you create a single main character and then recruit characters along the way. I’m considering allowing players to create characters at inns as well, to replace the recruitable characters if they wish.
At any given time, a single character leads the party (you can swap any time). It’s the leader’s skills and abilities that are used when interacting with the world so you should take care to have the right leader at any given time.
The SKALD scripting language is quite powerful in allowing me to reference player skills, abilities and previous player choices in the dialogue and the “choose-your-own-adventure” sequences.
Specifically, this gives me a lot of leeway in creating scenes with multiple solutions beyond combat (I’m taking a big leaf from the early Fallout games here). There should be room for all the different classes, and builds, to shine.
In the interest of transparency, I want as few hidden rolls as possible. If, for instance, a dialogue choice gives you the opportunity to use a skill, the game will tell the player so explicitly.
Combat is a staple of fantasy RPGs and SKALD is no exception. The basic combat draws upon inspiration from classics such as Wasteland 1 and Bard’s Tale, tabletop RPGs and other, more modern games.
As combat begins, the game switches from the tile-map to the tactical map. The tactical map consts of a background with the combatants animated upon it.
Combat is resolved in order of initiative until all the combatants on one side is either dead or somehow incapacitated.
Combatants do not move freely around the battlefield and combat is not tile-based. Instead the combatants occupy either the front, or rear rank of their formation. The player is of course, free to reorder the party formation during combat to move characters between the front and rear rank.
In general a melee weapon (excluding spears and pole-arms) can only attack the adjacent enemy rank, whilst ranged weapons and exceptionally long weapons can attack more distant ranks.
For each turn, each combatant can perform a single action (in general). This may be either a normal attack, casting a spell or using an ability. I intend for there to be interactions between different spells and abilities that reward clever planning and an attention to detail.
For now I’m hoping to make combat difficult but not unfair. Party-members are very rarely killed outright in combat. Instead they are knocked out and failure only comes if the entire part is somehow incapacitated. Knocked-out party members come around after combat (albeit at reduced total HP). I’m also playing around with having a sanity score in the game and taking a lot of beatings might impact sanity in the long run.
I’ve chosen to go with this decision because I don’t want combat to prompt constant save-scumming. I would rather you survive most combats but have to make decisions of how far into a dungeon you can push your luck and then having to plan how to get back to a safe port with an injured party. I feel it will make for more memorable gameplay in the end.
Finally, combat has an auto-resolve feature that can be used to resolve full rounds of combat allowing players to blow through easier encounters or finishing combats quickly once they have them “locked down”.
That’s it for now!
This is a work in progress and it might look very different a year from now.
As always, I would love to hear from you if you have questions or comments. Feel free to reach out on twitter or get in touch at (contact at skaldrpg dot com)! Most importantly: SKALD is on Kickstarter till July 3rd and we would love to have your support!
Have a great day!