• Advertisement

Turn-Based, SP, Combat-System Idea

Recommended Posts

Okay, so I've got an idea for a turn-based combat system that's different from others I've heard of. My purpose in writing this is to get general opinions on it. Any opinion is fine. I do have a specific question though, will this be too complicated or will combat take too long for the player to enjoy it? Of course, I also want know how I can make it better.

The basic idea is:

    1a. Two roles, two characters, attacker and defender.

    2a. The attacker attacks repeatedly.

    3a. Each subsequent attack is easier to counter which means, evading the attacking and attacking in the same move.

    4a. This is determined by the attacker and defender's relative speed and skill. A new character will have a hard time pulling off combos against a veteran NPC.

    5a. When a counter happens characters switch roles, the attacker becomes defender and vice-versa.

Another Idea I'd like to try with melee weapons is weapon range:

    1b. The character with a shorter weapon is automatically defender until they get in range and successfully counter.

    2b. Defenders get closer by the same sort of process as the counter-switch method above.

    3b. But it's a lot easier to get closer because they don't need to attack, just move forward.

    4b. Weapons can still fight at closer than maximum range, but suffer increasing penalties the further out of their "optimum range," which may or may not be their maximum.

    5b. Characters can carry multiple weapons to switch between, but suffer penalties if they carry too many weapons, especially large ones.

    6b. Characters can't pickup discarded weapons and suffer large penalties when switching, but become lighter weight, of course.

Lastly, I don't want to use a hit-point system:

    1c. When attacking characters choose between attacking the left and right arms and legs, the torso, and the head.

    2c. Then they choose a specific target such as, on the head, eyes, mouth, chin.

    3c. If they hit anywhere on the target they wound him.

    4c. Wounds cause disabilities and bleeding.

    5c. Disabilities are essentially status-ailments. Examples could be, blindness, disorientation, etc.

    6c. Disabilities are more likely to come from hitting specific targers, and hitting different ones will give different disabilities.

    7c. Characters all have a blood-level of 100 that can be reduced over time by bleeding from wounds. All wounds, except from blunt weapons, cause bleeding.

    8c. If blood-level is reduced to 50 they lose consciousness, at 0 they die. (You only need to lose 1/3 of your blood to die, so the blood-level value represents 1/3 of a character's blood.)

Edited by RidiculousName

Share this post


Link to post
Share on other sites
Advertisement

Hello Mr. Ridiculous,

I think what you have for the basic idea sounds like it could be a lot of fun, I think it could be an entire game on it's own.  I'd say make a prototype of that, and polish it to a tee.  Once you have the core gameplay loop down, slowly start to add in the specifics, and test as you go.  Knowing how players react to each feature will be good indicators of how and when to implement them into the game, if at all.  In other words, make sure you test the hell out of your game to see what works and what doesn't.  I'm sure you can take it from there :)

Share this post


Link to post
Share on other sites

You're fine man, just keep working on your project, it's an awesome idea.  Update us as you go along, and I'm sure a lot more people will be interested once your game gets closer to completion.  I'll be sure to check it out once you have something to show.

Share this post


Link to post
Share on other sites

In general, I think it's a great start. The counter-switch mechanic sounds fun and the melee weapon range is a cool variation. I don't like the blood system because it's just another name for hit points and you said you don't want hit points.

This does sound like it could be a very involved, tactical, and somewhat slow system, which means it should really be the central focus of the game rather than a secondary feature. It could almost be a purely turn based arena fighting game without any other game play.

Edited by missionctrl

Share this post


Link to post
Share on other sites

Hey, thanks for responding. I'll edit my first post later to make it clearer, but the blood system is meant to be a way to keep fights from going on too long than a name-change for an HP-system. Bleeding is a constant drain on your blood-level, since all wounds inflict some bleeding. However, most matches will be decided by who gets the worst disabilities, (I couldn't think of the word "injury" when writing that. Another thing to change.) many will outright kill you.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By RomanExHair
      Good day!
      My name is Roman Trestcov. I'm engaged in: 
      Producing the sound design of games and video clips; Exclusive creation of music, creation of music on references; Sound Design: Synthesis, Sampling.   
      I work with separate elements of the game, and I voice the whole project. 
      Examples of my work can be found below. 
      For this video, i write music and key sound elements (steps, explosions, noises, etc.). 
      https://www.youtube.com/watch?v=hHhLOkFHK8s&t=25s 
      For this trailer, also was written music and sound effects. 
      https://www.youtube.com/watch?v=Aba_KKhqx6Y&t=35s 
      Below is a compilation of my works: 
       
       
      You can hear more of my work here: 
      https://audiojungle.net/user/knock-noise-room/portfolio 
      https://www.pond5.com/ru/artist/knock_noise_room#1/2064 
       
      If you like my work – cool! I'm always ready to join your project and give it a unique sound design. 
       
      Always online: 
      rtrestcov@gmail.com 
      https://www.facebook.com/roman.baalberith 
      https://vk.com/roman_trestsov 
    • By steve negrin
      hello, i'm steve and im designer, i can design any idea and i'm looking for projects to help, if you are interesting write and we can talk about it
    • By Ovicior
      Hey,
      So I'm currently working on a rogue-like top-down game that features melee combat. Getting basic weapon stats like power, weight, and range is not a problem. I am, however, having a problem with coming up with a flexible and dynamic system to allow me to quickly create unique effects for the weapons. I want to essentially create a sort of API that is called when appropriate and gives whatever information is necessary (For example, I could opt to use methods called OnPlayerHit() or IfPlayerBleeding() to implement behavior for each weapon). The issue is, I've never actually made a system as flexible as this.
      My current idea is to make a base abstract weapon class, and then have calls to all the methods when appropriate in there (OnPlayerHit() would be called whenever the player's health is subtracted from, for example). This would involve creating a sub-class for every weapon type and overriding each method to make sure the behavior works appropriately. This does not feel very efficient or clean at all. I was thinking of using interfaces to allow for the implementation of whatever "event" is needed (such as having an interface for OnPlayerAttack(), which would force the creation of a method that is called whenever the player attacks something).
       
      Here's a couple unique weapon ideas I have:
      Explosion sword: Create explosion in attack direction.
      Cold sword: Chance to freeze enemies when they are hit.
      Electric sword: On attack, electricity chains damage to nearby enemies.
       
      I'm basically trying to create a sort of API that'll allow me to easily inherit from a base weapon class and add additional behaviors somehow. One thing to know is that I'm on Unity, and swapping the weapon object's weapon component whenever the weapon changes is not at all a good idea. I need some way to contain all this varying data in one Unity component that can contain a Weapon field to hold all this data. Any ideas?
       
      I'm currently considering having a WeaponController class that can contain a Weapon class, which calls all the methods I use to create unique effects in the weapon (Such as OnPlayerAttack()) when appropriate.
  • Advertisement