Putting the 'role' back in role-playing games since 2002.
Donate to Codex
Good Old Games
  • Welcome to rpgcodex.net, a site dedicated to discussing computer based role-playing games in a free and open fashion. We're less strict than other forums, but please refer to the rules.

    "This message is awaiting moderator approval": All new users must pass through our moderation queue before they will be able to post normally. Until your account has "passed" your posts will only be visible to yourself (and moderators) until they are approved. Give us a week to get around to approving / deleting / ignoring your mundane opinion on crap before hassling us about it. Once you have passed the moderation period (think of it as a test), you will be able to post normally, just like all the other retards.

Bard's Tale The Bard's Tale IV Pre-Release Thread [RELEASED, GO TO NEW THREAD]

Infinitron

I post news
Staff Member
Joined
Jan 28, 2011
Messages
97,510
Codex Year of the Donut Serpent in the Staglands Dead State Divinity: Original Sin Project: Eternity Torment: Tides of Numenera Wasteland 2 Shadorwun: Hong Kong Divinity: Original Sin 2 A Beautifully Desolate Campaign Pillars of Eternity 2: Deadfire Pathfinder: Kingmaker Pathfinder: Wrath I'm very into cock and ball torture I helped put crap in Monomyth
Meet your new object of potential hatred, Codex - Systems Designer David Rogers. UPDATE: https://www.kickstarter.com/projects/inxile/the-bards-tale-iv/posts/1562643

Glorious Combat

Hello Citizens of Caith. My name is David Rogers, and I'm the Systems Designer on The Bard's Tale IV. I know I don't have to tell any of you that combat is a core pillar of The Bard's Tale. It's where all of our choices about race, class, gear, and party composition combine with our own sense of strategy, leading to either glorious victory or humiliating defeat. Combat design is what I've been primarily focused on, and what I'm here to chat with you about. Before we dive into the real meaty bits, I need to give the obligatory disclaimer that what you're about to see is all a work in progress, and changes may occur between now and the final release of the game.

Combat Basics
One of the great things about designing for a dungeon crawler is your ability to quickly build the game on paper before you build it out digitally. We've put a big emphasis on proving out our designs by playing them out on the tabletop. Similar to playing a game of D&D, we're able to play out the bard's tale on the tabletop and make sure what we're doing is fun, strategic, and ticks all the boxes we're looking for in The Bard's Tale IV. We started from a foundation of classic blobber combat, distilling down the parts that truly compel us. But we also make note of missed opportunities for rich strategic decision-making, and brainstorm how to capitalize on them.

One area we really want to improve on is the kind of decisions the player has to make during combat. It was a common trend in older blobbers that most of your decisions were made out of combat and once you entered combat you did the same actions over and over again. That old chestnut of "attack, attack, attack, defend, defend, fireball" is something we want to disrupt. Gaming has come a long way since the heyday of old school dungeon crawlers and we're dead set on bringing the genre back into the spotlight.

We discussed our 4x4 battlefield grid in a previous Kickstarter update. Accentuating the role that the battlefield plays in combat is one element we're focusing on. To briefly recap, during combat our battlefield is a 4x4 grid where the players' party occupies one half of the grid and the enemies' party occupies the other half. Because we want to show your enemies (and the bloody pulp you beat them into) in all of their glory, their half of the grid exists in 3D space. Your party, in classic blobber fashion, lives on your HUD. It looks a little something like this:

38d3db8ff414ea7fdd5e80c2f962dd27_original.png

This is what our board looks like while we're playtesting our paper prototype. After our art director gave it a little love it started to look a little something like this:


This is an example mockup, not an in-game screenshot, but should give a sense for our intended combat presentation.


There's a lot to talk about, so let's start with the grid. As you can see, the grid does a great job of blending the 3D space and the HUD together into a single battlefield. Where your character sits on this grid in relation to the enemy is of vital import. For instance, by positioning a resilient warrior in front of your frail conjurer, you can protect him from direct physical attacks, allowing him to spell-sling with relative impunity. Even beyond the classic front row/back row dynamic, characters can generally only attack enemies that are in front of them. Of course, there are exceptions to this, particularly when we start talking about magic. This heavy emphasis on your party's position has a lot of really cool implications that makes each combat a real strategic puzzle to be solved.

Which characters should I use to tank damage from each enemy? If an enemy is charging up a powerful attack, should I try to move someone into position to interrupt him or should I move everyone out of the way? Should I move my character into position to attack a critical target next turn, or should I just stay put and attack whoever is in front of me this turn? Should I cluster my team together to share short range buffs, or should I spread them out to avoid AOE damage?

These are choices we've not been able to present in past Bard's Tale games and we're finding them to be really fun and rewarding.

Designing Attacks
Positioning is one component of combat, but where things really start to get interesting is how attacks can tie into things like battlefield positioning. To give you a better idea of what I'm talking about, let's talk about the anatomy of an attack.

At the core of our design for The Bard's Tale IV is the idea that all attacks and abilities should be interesting to use. We are trying to move away from giving every character the same basicattack ability that just does damage. While doing single target damage is effective, there isn't a lot of strategy revolving around the choice of whether or not to attack your enemy. The answer is generally yes. That's an example of a missed strategic opportunity we wanted to capitalize on. Your weapons, spells, and abilities will offer their own unique attack types that often have different built-in properties to set them apart. You're saving the world, gosh darn it, so you'd better do something heroic! These differences can be minor or major, but the point is that each attack is designed to shine in different scenarios. Throughout your adventure you'll encounter enemies using new abilities and tactics. You'll need to keep evolving your strategy to be victorious.

When examining the anatomy of an attack and making it interesting to use, we have a number of qualities at our disposal. These include Attack Pattern, Damage, Damage Type, Special Effect, and Cost (Just to name a few). In this update, we'll cover Attack pattern, Damage, and Special Effects. We'll cover the other elements in a later update. Let's start by breaking these down one at a time.

First is attack pattern. Keeping in mind the influence the battlefield plays on our gameplay, each attack has a pattern associated with it that dictates who the attack will affect. An attack pattern may look something like this:

4e085664568ed843bc7812ad32423b45_original.png

This attack pattern is something you'd find on a sword thrust attack, and indicates it will attack forward, striking the closest enemy directly in front of it, up to two grid squares away. Other abilities may be able to pierce multiple targets, may strike from different directions, or be able to directly target an opponent regardless of their position (this is especially true of magical attacks). In game, you'd see a helpful targeting indicator show you the range of your attack, along with who'll ultimately be affected.


Once again, example mockup, not an in-game shot.


Our attack shown in the image above has a range of 2. Since our Warrior is in the front row, he can reach all the way to the enemies' back row. That enemy ogre is in for some poking the likes of which he's never seen! Had the Warrior been sitting in his back row, he wouldn't have been able to reach the ogre. The Hunter, positioned behind the Warrior, has long ranged bow attacks that can strike up to three grid squares away and is more than capable of sniping the ogre from relative safety.

Like we've said in previous updates, we want to allow player to experiment with multiple party compositions, including ones that might not conform to the tank + DPS format. One way this grid system supports that goal is evasion based defense and enemy disruption. Evasion based defense is the idea that I can attack with a character and then move that character in such a way that it makes it difficult for my enemy to effectively re-position themselves to mount a concentrated counterattack. Rogues are particularly good at this sort of hit and run tactic. Enemy disruption is similar, in that some classes are capable of throwing their enemies around the battlefield, disrupting their formation and making it difficult for them to effectively strike back in their following turn.

Now that we know who we're attacking, let's talk about the bloody part: Damage. Damage is a pretty simple calculation. Damage comes from the character's stats, which are sourced from a variety of places including gear, skills, level, etc. Most of the time, damage is a fixed amount instead of a random range. This really allows you to plan out the perfect combo, that will for sure take that ogre down before he crushes your skull in. There are some abilities that do random damage, but that random element is something special about the ability that makes it unique.

Once damage is dealt, then we apply any additional effects. This is where attacks start to get more interesting. An effect might knock an enemy to the side, exposing that frail caster he was protecting. Another effect might be a poison that damages an enemy over time. Yet another might be a debuff that reduces a target's armor, softening it up for your allies. You get the idea - effects open up a world of possibilities for us to play with.

To give you a more real-world example of how attacks can synergize in interesting ways, during our playtesting, one of the synergies that the warriors have been using is a bleed and bash combo. Axe-wielding warriors can cause their target to bleed, which causes them to take damage whenever they move around the battlefield. You can imagine them exerting themselves and gushing blood, leaving a red trail behind them as they bleed out. Once that effect has been applied, shield and club wielding warriors get to work. These blunt armaments can often knock an enemy from one grid square to the next, throwing them out of their ideal position and opening up attacks to the more vulnerable glass cannons they've been protecting. The nice thing is, when you forcibly move an enemy, it also triggers the bleeding effect. If done right, you can get a nice ping-pong combo by bashing a bleeding enemy back and forth between warriors, each time causing them to take bonus bleed damage.

Now, hopefully, you can see how all these elements come together into a really fun and thought-provoking combat system rife with opportunities for combos and counter play. We're continuing to tune and iterate on it, of course, making adjustments constantly based on playtesting.

There are a lot of things we didn't go into here that will also play a huge role in combat; things such as Mana management, combat stances, charge up attacks, and more. However, this should give you some insight into the depth we are building into The Bard's Tale IV. Stay tuned for Glorious Combat Part 2, where we'll cover the even more advanced and unique features of the Bard's Tale IV's combat system.

For now, let us know what you think! We've touched on combat before, but this is the first time we've shown anything in this much detail, so we want to hear your ideas. Also, thanks for supporting The Bard's Tale IV. All hail the Sword Father.

David Rogers
Lead Systems Designer
 

Llama-Yak Hybrid

Wild Sheep
Dumbfuck
Joined
Apr 1, 2016
Messages
321
So it seems that they're making the blobber where there's 8 member party limit but it's not necessarily optimal to have all of those slots filled. I think Fargo realised what I was talking about for a loooooong time. He won't ride on kickstarter nostalgia craze whole his life, he has to try something new.
 

Bumvelcrow

Somewhat interesting
Patron
Dumbfuck
Joined
Nov 17, 2012
Messages
1,867,060
Location
Over the hills and far away
Codex 2013 Codex 2014 Make the Codex Great Again! Strap Yourselves In
Infinitron prepared me to hate, but that looks quite promising. I'm not sure about a sword having two squares range, but that could just have been a simple example.

I'm not so happy with the fixed damage, though. They say that it allows for strategic planning, which is a fair point, but I think it reduces tension and the possibility of having to handle unexpected or unfavourable situations, making the game more samey. No attack should do the same damage every time, even if it hits. I presume they negate that by rolling for a to-hit chance, or am I being hopelessly naive?

I think I backed it, but these KS games are taking so long who can remember any more?
 
Self-Ejected

Excidium II

Self-Ejected
Joined
Jun 21, 2015
Messages
1,866,227
Location
Third World
Who knows? But that attack hits the first target it meets, maybe spears can circumvent that and hit backrow regardless?
 

Jimmious

Arcane
Patron
Joined
May 18, 2015
Messages
5,132
Steve gets a Kidney but I don't even get a tag.
It's not the sword but the attack from what I understood.
I'm not sure I understand. That character is attacking with a sword. What's the difference? What if I had a spear?
If I got the feeling right, with the sword he would attack the first enemy in the two tiles in front of him. Maybe with a spear you can choose to attack the one in the second tile even if there's another one in front?

Seems interesting generally
 
Self-Ejected

Excidium II

Self-Ejected
Joined
Jun 21, 2015
Messages
1,866,227
Location
Third World
Yeah, it's a lunge attack if you will. And with 2 square reach means you can still hit the front enemy from the backrow.
 

Bumvelcrow

Somewhat interesting
Patron
Dumbfuck
Joined
Nov 17, 2012
Messages
1,867,060
Location
Over the hills and far away
Codex 2013 Codex 2014 Make the Codex Great Again! Strap Yourselves In
The point is that swordsman should be able to take out a guy who's unprotected in the back row.
Yeah, that's the bit I'm concerned about. If it is a 4x4 grid then either the sword has an inordinately long range or the wielder has to put himself out of position to reach the back row. As I said, it could be just an example - he said sword when he meant 'generic range 2 weapon'.
 
Self-Ejected

Excidium II

Self-Ejected
Joined
Jun 21, 2015
Messages
1,866,227
Location
Third World
It probably has limited use in some way, I imagine the main advantage is the reach so there must be more attractive attacks unless you really need to hit a square further (like if an enemy ability dislodged your swordsman to backrow). or God forbid a cooldown.
 

Alchemist

Arcane
Joined
Jun 3, 2013
Messages
1,439
This sounds pretty good so far, though the lack of random damage by default made my inner grognard start to twitch. But I'm liking the tactical options they're describing.

It seems they've been checking out the Japanese blobber scene... the UI mockup immediately reminded me of this: (Stranger of Sword City)
Lj1MA5C.jpg


And that's probably a good thing, as the Japanese have done more to advance blobbers than any western studios have in recent years.

Also I think it's awesome that "blobber" is entering into legit game designer vocabulary. That was a Codex-originated term wasn't it?
 
Self-Ejected

Excidium II

Self-Ejected
Joined
Jun 21, 2015
Messages
1,866,227
Location
Third World
This sounds pretty good so far, though the lack of random damage by default made my inner grognard start to twitch. But I'm liking the tactical options they're describing.
Deterministic damage doesn't bother me as much. A range or the average in the end makes little difference. Plus with all the extra effects there's more decisive things with every attack.
 

Hirato

Purse-Owner
Patron
Joined
Oct 16, 2010
Messages
3,961
Location
Australia
Codex 2012 Codex USB, 2014 Shadorwun: Hong Kong
That's a pretty standard blobber set up they have there.
Hopefully they'll experiment with a few more things.

And with the range-2 swords, do the usual restrictions apply? ie. if you attack a thing with 1 row inbetween (eg, attacking back row from the front row) is there's a large damage penalty? Or have they opted to simply make it not possible if there's an 'obstacle' in the way?
 

Llama-Yak Hybrid

Wild Sheep
Dumbfuck
Joined
Apr 1, 2016
Messages
321
And with the range-2 swords, do the usual restrictions apply? ie. if you attack a thing with 1 row inbetween (eg, attacking back row from the front row) is there's a large damage penalty? Or have they opted to simply make it not possible if there's an 'obstacle' in the way?
If there's an other party member on the way, he'll take the hit, as in - it hits the first target 2 tiles away.

btw this isn't something new or weird, it was just presented in a weird way, because they're drawing some tiles and shit, making it look like some HoMM derivative rather than ordinary blobber, from what I understand it does pretty simple thing:
  • melee fighters in back row can only attack enemies in front row
  • melee fighters in front row can attack both enemies in front and in back row, hits the first thing on its way - so when you have front row only, you can hit the ranged attackers in enemy's back row once you kill enemies shielding them
  • ranged attacks can hit all rows from whatever row they are(it's not specified if enemy's front row will take all the damage they'll do or not)
 

As an Amazon Associate, rpgcodex.net earns from qualifying purchases.
Back
Top Bottom