Simulating Boredom (Yes, Seriously)

Started by
16 comments, last by TyrianFin 14 years, 1 month ago
In games where you can perform an action to raise a skill or stat, what do you think about some mechanism that forces players to rotate their actions for maximum benefit. This one's simple: The more your character does something in a short space of time, the less and less its character building effect (XP or point boost) will be. Would it work to discourage repetitive skill or stat grinding? It seems to me that if you include a way to do something profitable in a game, even if it's boring, players may feel compelled to do it. This might be a way of counter-balancing things so that players just play the damn game rather than min-max. I could see doing this by keeping a list of "most recent actions" and apply what effectively would be a cool down time to each. Your character could be said to benefit the most from doing the things that are most exciting to him or her, and chopping a combat dummy 1000x times or baking a gazillion loaves of bread just aren't.
--------------------Just waiting for the mothership...
Advertisement
Sounds nice, but in reality, players will grind A until xp drops off, then B, then C, then back to A. You're better off finding fun things for them to do (by not letting them gain more skill until a the level is complete or some other condition is met).

After experience Star Wars: Galaxies and UO, players will grind anything and everything, and will find optimal ways to grind your system.
If the game has lots of content, make the countdowns permanent, so that repeating a task more than the amount you want the players spending there stops producing a benefit for good.
hehe, i was tricked into this post by its title.

What i have in my game is say the travel between
two plantes takes 5 min, then i give the player the
possibility do something he normally would not do,
but by doing it he got some kind of bonus. So it is
a force and a reward and the same time.

And besides, by knowing this, i hope the player
could plan ahead and save these special tasks and
do them during the travel delay.

P.S. not sure if this is offtopic though.
The game I've been designing for a few weeks with a friend has a skill system similar to this.

Our game doesn't present the experience to the player, it's kept in the background. Not all skills level the same way, and how much it takes to level a skill depends on other skills and the character stats. On top of that, after not using a skill for a certain period of time, the skill starts diminishing, and skills diminish at different rates depending on which skills you use the most.

A diminished skill is easier to level up to the base level than a normal level up, but it's not instant. In this way, we're hoping players just stick with the style of character they want to have (warrior, mage, rogue, assassin, etc) because stopping to raise other skills will only start diminishing the skills the player uses more often at a faster rate.

However, because of the differing diminishing speeds, a skill not used a lot takes a lot longer to start diminishing. Because of this, we're hoping that non-essential skills will level up through the quest line instead of repetitive actions at the beginning of the game.
If you are looking to deter skill grinding, you could create a level system that is independent of skill gain and then limit the amount that can be gained per skill each level.

Or you could limit skill gain per level and then tie in several skills to level up. For example, perhaps to gain a level in a "Fighter" class a player would have to gain at least 7 skill points in Weapon Use, Parry, AND Dodge, up to a maximum of 10 skill points in each of those skills per level.

These won't stop the grinding, but they will divide it up in such a way that the player doesn't benefit too much from simply taping down a key overnight.

Another option: if you have a stamina/vitality bar, don't replenish it so quickly. In most games it refills fast to prevent the player from finding himself too exhausted to fight effectively. However, if you include, say, a temporary "adrenaline rush" to vitality when a player first engages in combat that fades after, say, 20-30 seconds, you could both treat out of combat physical activity more realistically by limiting skill use/gain for an exhausted character, but also force players to resolve combat more quickly instead of spend time grinding stats against a single weak opponent.

Optionally, with non-physically oriented skills, you could use a "focus" stat with a bar similar to vitality that drains as he/she uses skills that rely on concentration.

I do think a boredom system is logical from a realism standpoint (most people would get bored jumping rope for five hours for example), but I do agree with above sentiments that if there is benefit to grinding, players will find a way to do it as efficiently as possible.
I've only glanced at the replies thus far but I have a suggestion. What if skill increases via actions is worked a bit like xbox achievements. By this I mean that each action is a distinct event which gives a predefined reward when done and can not be done again for more points. There can be duplicates of course, but there is a limit that the player is aware of. You could also make the player aware of the most profitable actions to take (which should also be the most challenging) and so the player will become engaged in achieving and growing rather than just grinding.

P.S. I only glanced at the replies because I am about to go play left 4 dead again to try for some achievements I haven't managed yet.
@JasRonq

I had been thinking of something like this too. Might start a post in Writing for Games, though, just like my other game idea thread this game will probably never see the light of day because I don't have any experience and no way to pull a team together. Still, would appreciate if you and anyone else would share more thoughts once I have the thread up. Nice to know that others are catching on to a similar idea.

P.S. My game idea is not based around achievement experience/skill gain. That is only a small part in what I hope will not seem too complicated. Good day.
"It wasn't Me who was wrong. It was the World!" -Zero
Just sort of popped in my head...

Tactical: Quantum torpedos have been reloaded. Ready to fire on your order, Captain.
Captain: Meh, we've been doing that for 10 minutes now. Prepare to ram their ship.

Using a bordom level to effect a diminishing level of gain from repetitive training sounds like a good idea to me. I think you might not need to discourage grinding to the extent that you think you do. At least, not if time is a factor. I could sit in one location chopping trees for a year making myself the strongest soldier ever only to find that when I've completed training, the war has been over for quite some time. With time being a factor in the gameplay, grinding in effect becomes training. When and how much to train becomes a tactical decision.

Still, if you want to discourage this sort of behavior further, perhaps part of leveling up a skill could involve having a teacher (or maybe a how to manual) of some kind. Require a combination of training and instruction to net any gain. If the instructor's skills are lesser than yours then there is no gain. The search for better instructors becomes its own quest. Perhaps when the player finally finds the master he's been seeking he's refused training for associating with some faction or another.

You're setting the game system to favor the dps classes (if your into rpg type game) because they can rotate the different skills enough times until the first skill will be available again without the penalty. The ability to rotate skills is a necessary experience for a player to effectively learn the dps class. As in all instances, people have favor over certain classes over others ( dps, healer, tank ), and this post shows favor towards the dps.

Since the trend of MMORPG is towards having lots of dps characters and few tank or healer, your idea will definitely make the tank or healer class even rarer as these classes can quickly reach redundancy if the dps is too powerful.

Players like to be occupied with action, so this rotation of skill will improve the time at which the player will be occupied with playing the game. Essentially, the idea does have positive influence to a game design. But, this mechanics actually encourage the player to grind even further than ever because they can gain much more repetitive skill of a longer chain of action than the shorter chain of repetitive skill. The longer chain of action for the repetitive skill encourage more motion for the player's hand across the keyboard. This mechanic increases the min-maxing of the players because they will rotate the skills they play. The goal of the player is to memorize a chain long enough so that they will reach cool down for their initial skill of the series of techniques. You're only setting up a longer "chain of memories" ( lol, didn't really want to use that phrase because it's a title of a game ) for the player to accomplish the game play.

Summary:
This mechanic encourage repetitive skill and stat grinding. The repetitive skill is a longer "Chain of Memory" ( has nothing to do with Kingdom Hearts )
Players are skill min-max by rotating the skills instead of using one skill.
The effect of cool down timer will allow the player to select series of skills that will ensure that the first skill complete the cool down so they can reuse the skill again for maximum benefit.

Counter:
You are trying to stop repetition, but you have to remember that playing the game itself is a abstract level of repetition. The only way to stop repetition is to somehow make the player stop playing any games i.e. you cannot run away from repetition, you can only extend the length of action so that it is long enough for the player to lose their sense of repetition.
Players will always min-max unless all choices give the same result. If all choices give the same results, then their is not reason to even play the game because you will always get the reward. Thus, you cannot attempt to get rid of the motivation / reasoning behind the element of a game.
I use QueryPerformanceFrequency(), and the result averages to 8 nanoseconds or about 13 cpu cycles (1.66GHz CPU). Is that reasonable?
I though that the assembly equivalent to accessing unaligned data would be something similar to this order:

  • move
  • mask
  • shift
  • move
  • mask
  • shift
  • or

So it seems reasonable to say that it takes 14 cycles for unaligned data since we'll have to do the series of instructions once to access and once to assign?

This topic is closed to new replies.

Advertisement