Friday, May 20, 2011

Update on Programming Research Task

I haven't started implementing much of the framework for my research task, which is a problem since I did plan to have it done for the 25th (4 days).
So, I'm a little behind.

What I have done however, is implemented A* - which will be useful for Tree navigation, and I've started researching heuristics for specifically trying to take into account how likely it is for a research to lead to other research paths down the track.

So, if a political goal was researching C, and further down the line they wanted to also research D - they might take research A, which leads to both - rather than B which reaches C quicker, but now not lead to D.

I am programming this task in C# - because it is extremely quick to get off the ground. I already have a simple GUI going, with inputs.
The only issue is that it is slower than C++ - so, my efficiency calculations will have to consider this. It is possible that as C# and C++ are pretty similar, I could try to quickly port the code over, and test it on C++ as well.

I am using XML for the research trees - and loading in of other data items, for example, "Area" templates which define temperature ranges, local materials and such which define the initial products that a civilisation can create (such as rice, fruits, and metals).

While, again, XML is slow, it only really needs to be loaded in at the start of the application for skill trees, and, depending on whether I allow the saving and loading of past simulations, they can be accessed on the menu screen when selected.
On the plus side, XML is very quick and comprehensive to edit.

To make up for the time I've lost, I'm going to implement a very basic skill tree, and expand it as I go.

Monday, April 18, 2011

This blog will be home to my major research project.

It totally will.

So... ummm... this is late!

Hey guys!
The Game Design comp finished a week ago - and, so, here are the entries!

Tales of Berefriszia: The Knighting of Delacroix
By Wafik Salim

Impending Ascension
by Matt Jones

PROJECT neverWAKE
by Raymund Serrano (This one had to be cut down for submission)

A.N.T.agonist
by Adam Taubert

Cyberelm
By Greg Lennard

Zombie Hallway Dash
By Justine Colla

Sloth
By MEEEEEEEEEEEEE! (Zanda Cetinski)

Project: Element
By Sean Evans

Chino
By Josh Dobson

Dropper
By Adam Vieira

Watch them all, they're all awesome!

Thursday, March 24, 2011

Best College Ever?

Today, the head of my college campus help a PSP box just outside my room, and motioned towards a poster I had up saying "First prize?".

Yes, that's right guys, AIE Sydney has officially donated a PSP to the competition as first prize!
That should certainly motivate people!

Thanks to Neil and the other staff at the AIE for spicing up my poor-college-student prizes with something much more awesome!

Saturday, March 19, 2011

Metaphor for Skill vs. Imbalance.

Introduction
Do you ever find yourself arguing over balance on forums?
Damn right you do - or at least I do occasionally.
One thing I find in every single gaming community is that many people (new to the game and experienced alike) don't understand that when discussing balance, you must eliminate skill as a variable.

Hence, most discussions are like so:
"X is too powerful"
"Just use [unreliable attack] to kill him!"
"But that assumes he just stands there and lets you use it!"

In this situation, someone defends a unit by assuming a player of low skill is playing it.

Or
"X is too powerful"
"I find it to be balanced as when I'm playing, other people kill me with [unreliable attack] all the time!"
"That attack is easy to counter if you are aware of your surroundings, though."

In this situation, people often degrade their own skills, or give examples of extremely strong opponents to defend the unit.

Obviously, all of this argument is invalid, because, your test subjects should be at an equal skill level, or, as I posted in a previous article ( http://zandagamedesign.blogspot.com/2010/02/skill-ceilings-and-floors.html ) - they should be at the skill ceiling of their respective units to accurately judge absolute potential.

Anyway, I'm not going to dive into all that and restate everything - this article is made so that, if you ever do need to explain to a person how skill relates to a unit's potential, you can just refer them to this article.

On with the Metaphor!
To balance two units, you MUST measure their potential at their skill ceiling (or peak human skill if the skill ceiling is higher than the limits of human qualities).

To demonstrate this, I will be discussing the fine art of carpentry.

Firstly, imagine that instead of complex characters, the units in your game are simple tools, that you as a player, utilise to win the game.
This is exactly what they are. You unit in a game is a tool. Nothing more.

So, let's say we have two Hammers, the "Craptacular Nailpusher 101" and the "Super-Gold-Hammer Deluxe 5000". We'll assume that, as their names suggest, the 5000 model is far superior to the 101.

Let's say that "Balanced Hammer Co." wants to measure up the hammers against each other - as they are unsure of whether the Deluxe model really is any better.
So, they pick two carpenters from the local area, Tom and Dave to test out the hammers.
The thing is, Tom has been hammering for an odd 20 years now, and specialises with his Nailpusher 101, while Dave is completely new to the trade, and was frankly dropped a few too many times on his head while he was a baby.

The test begins, and Tom immediately takes the lead. He finishes the task deftly and with prowess, while Dave manages to hit himself in the face more than the nails he's supposed to be hammering.

The company records these findings, but obviously note that Dave was a really bad test subject, and so they discard the reports.

To relate this back to balance briefly, this shows that just because a unit is overpowered, it does not necessarily mean that new and unskilled players will immediately dominate skilled players with it. Even in unbalanced scenarios, a wide skill gap will still favour the more skilled player.
If it doesn't, then the balance issue should be so plainly obvious, it would have to be intentional.

So, back to the hammers.
Balanced Hammer Co. goes back to the drawing board.
What could they possibly use to test the hammers?
They search around, and find another carpenter - Adam, who has the same degree in hammery as Tom, and has been hammering for exactly the same number of days as Tom.
As far we can tell, Tom and Adam are both skilled at carpentry, and they are both about equal in terms of skill.

So, the competition starts off again, and, Tom, who now gets to try out the 5000 model, wins by a mere nail.
The company takes the results, and concludes that their new hammer isn't worth the 200% markup over the 101 model, and agrees that they must add more and more features to the 5000 model.
Seeing as Tom has been a willing participant in two tests, the company give him a free 5000 model as thanks - and guarantee him a discount on the model when they finish superpowering it.

So, Tom goes home, and, decides to use the hammer full time. It did win the competition, so why not?
Anyway, 3 weeks later, he's hammering some nails when he realises that on this particular model, the handle has a flat base that, on every 3rd swing, can be used to strike nails harder than usual.
Conducting his own test, he decides that this feature should be raised with the Hammer Co. company, to help them with their designs.

What does this show us?
Just because players aren't currently bunnyhopping with the Sniper class, headshotting every player they encounter with quickscoping, doesn't mean that the unit cannot do it. Players will often gain more and more skill until a large portion of a unit's potential is realised.
When judging balance, you cannot just use "good" players, you must go further, you must evaluate the unit's absolute potential.

Back to hammers.
So, Balanced Hammer Co. take this last lesson in their stride, but unfortunately they're still unsure of how they can measure up the two hammers.
But, one of their engineers has been doing some searching, and he finds the contact details of a couple of Romanian Hammer Brothers who are said to have such amazing skill in carpentry that they can immediately take one look at a hammer, work out every single trick with it, and utilise the hammer and all its features to a near perfect degree. The degree at which they can utilise these hammers is at the absolute limit of human hammering ability.

So, the company flies them in, and hands them each hammer.
The brothers take a quick moment to analyse the hammers, and the competition begins.

The result is that the brother with the Deluxe Super-Gold-Hammer 5000 wins by a land slide. He found many more tricks to this new hammer, than the other brother could find with the older one due to the new design's slick form, useful handle, and other features.
The brothers were completely equal in skill - and both were at the peak of human skill in hammering terms - so what happened?

As we started at the beginning, the Deluxe Hammer was simply better.

If we liken this to games, you can have a player at the skill ceiling of a Machine Gun class - but, if the machine gun class only deals 2 damage per second, while the others deal 100 damage per second, all that skill does not matter. The class is inferior to the others.

Conclusion
So, Balanced Hammer Co. choose these results over all others - why?
  • We are not comparing a bad player to a good player.
  • We are not comparing two equal players, that cannot utilise their units properly yet.
We are comparing two players, who use the units to their full (human) potential - and they demonstrate how powerful the units really are in comparison to each other.

This is how you evaluate balance.

I hope everyone enjoyed this post, and I want to try to follow this up with more skill vs. balance articles really soon.

Friday, March 18, 2011

AIE Sydney Game Design Competition!

Okay guys, I've been talking about this for the last year or so, but I've decided to finally get off my butt and set it all up.

Not all details are finalised, I'm just putting this up now so that everyone can get started.

In the spirit of the competition, I've decided to lay this info out as its own game pitch.

So, let's get started:


AIE Sydney Game Design Competition

Basic Concept:

Participants must submit a video pitch for a video game idea to be judged.

The video should be of 3 minutes or under in length.

The design can be any original design, for any style of video game.

The video should detail the concepts of the game, its tone, its gameplay, and etc.

The competition ends on 3/4/11.

The winners will be announced on (to be decided)


Gameplay (Specifics):

Information and updates on the competition will be displayed in my statuses, notes, and on my blog. (link below)

This competition is only for AIE Sydney students (first and second year)

No implementation is required, and any additional material will not be considered during judging.

Any video style is fine, whether it's full video, audio over animation, or a simple powerpoint.


Submission:

Videos must be uploaded to Youtube.

When the video is uploaded, post the link to my wall, or email it to alexander.cetinski@gmail.com

Submissions close on 3/4/11.

I will showcase submissions on my blog, and on my wall.

You can only submit one entry.

Multiple people can work on the same video, but the prizes are not negotiable or multipliable.

Submissions > 3:10 mins will be rejected. The extra :10 is to protect against youtube length issues.

Please include your year in the video description.


Win Conditions:

The competition will be judged by our amazing and wonderful game teachers - Conan, Dan, Epona, Matt and Mike.

The Judging Criteria Are:

- Concept

- Gameplay

- Fun Value

- Sellability


You will get a rating out of 10 for each criteria, which is averaged for your final score for that judge. Then the final scores are averaged for your over all mark.


Rewards:

Overall Awards

1st Prize: "Game Development Essentials: Gameplay Mechanics” - http://www.amazon.com/Game-Development-Essentials-Gameplay-Mechanics/dp/1418052698

2nd Prize: $25 in Steam games

3rd Prize: $15 in Steam games


Prizes are not negotiable or multipied for group submissions.


Year Specific Awards

First, Second, and Third Best Submissions will be announced for each year.

There are no year specific prizes however.


Additional Awards:

Best Original Protagonist

Best Original Antagonist

Best Game World Concept

Best Tone (Comedic, Suspenceful, Dramatic, etc.)


Joke Awards:

Most Likely to get Cease + Desist’d by Nintendo.

Most Likely to get a terrible movie adaption.

Most likely to require a Valve-Time release date.

Most likely to be refused classification in Australia.


-------------------------------------------


An example entry that won me a similar competition 2 years ago (2009):

http://www.youtube.com/watch?v=YL294g3svr0


So yeah, spread the word, and start with the entries!

I want to see lots of them. LOTS OF THEM.

This comp will be useful for getting your skills up to pitch for the major project coming up!

Saturday, December 25, 2010

Risky Design: Plain Sight

Introduction:
All games have design flaws. Some are major, some are minor. Some can be fixed, others can't without changing the game greatly. This is just a reality we all get used to. I doubt any game could have perfect gameplay, pacing, balance, or interface - but all great game designers aim to limit their game's flaw's impact on gameplay as much as they can - so they are barely noticeable.

An example of this would be for example that in many modern games and sports that are objective driven and focus on simultaneous attacking and defending (such as Capture the Flag), once a team has the lead - in some games it may be more effective to defend said lead, rather than attacking and trying to get a larger lead.
This is a flaw, yes, as part of the main idea behind Capture the Flag is balancing your offense and defence - but most games will just allow it - why?

There are very limited ways to actually fix it.
You could separate the offensive and defensive elements so that each team takes turns trying to get each other's flags (kind of how Rugby-styled football games do, or how Counter Strike's CS maps play out), but that's not capture the flag. It would in fact completely remove the balance that we want to achieve.

Another alternative is maybe buffing the losing team slightly so they can break through defences easier - but then you could run into balance issues, and teams being wary to get the first point in fear of a strong counter attack - which, could lead to stalling until the clock is very low and then trying to win.

So, Capture the Flag is flawed - but we all live with it and enjoy it still, because there are few ways in which the game style could be slightly tweaked to fix the issues surrounding it, without completely changing the game type. The problem is also fairly minor, as most teams will continue to pursue the flag even if they have the lead.

Still, there's room for improvement.

Moving On:
The point of this article is to talk about the game "Plain Sight".
Plain Sight is an amazing game developed by Beatnik Games, and the reason I'm writing thisarticle is because Plain Sight takes many features that have very easy to recognise flaws, and actually mashes them together to make for a greatly fun, near-seamless game style.

Before I dive into it, check out Plain Sight here: http://www.plainsightgame.com/
And I greatly recommend you buy it from Steam here: http://store.steampowered.com/app/49900/

Plain Sight uses the following flawed systems:
  • "Big Head" mode from Goldeneye.
  • Progression through death
  • Exponential power growth
  • Transparent player actions

"Big Head" Mechanics.
Explanation: In case you haven't played Big Head mode in any games such as Golden Eye, Unreal Tournament, etc. - it is a supplementary game style where, you still pick "Deathmatch", "Capture the Flag" or the like, but in Big Head mode, when you get a kill, your head gets larger so it's easier for people to headshot and kill you.
Pros for Gameplay: A fun silly mod for people to mess around in.
Cons: People can be reluctant to go for a large spree, and will sometimes commit suicide to make their head smaller.
In Plain Sight: Characters get larger and larger as they get kills, and as they do this, they can be targeted and tracked from a wider distance. Also, players who are larger yield more rewards for those that kill them, making them not only an easier kill, but a more sought after one.

Progression Through Death
Explanation: Progression through death is where a player feels that they gain more from relentlessly pursuing a goal and dying over and over, rather than trying to stay alive. Think of it like a player using a character with high area of effect damage running in a group of enemy players over and over to slow their progression, rather than taking them with skill and planning on as the game designers would intend.
Games can reward progression to death, they can punish it heavily, or any measure in between. It depends on the game.
Pros: The only time when death should be rewarded is where death is the objective - which is extremely rare. So, if "Death" is considered the failure condition, there are no pros to rewarding it.
Cons: Again, if death is the failure condition, it is bad to reward it.
In Plain Sight: Plain Sight is the first game I have played where death is the objective. In Plain Sight, you must gain energy by killing opponents (and getting bigger), which, then, when you commit suicide - gives you the fruits of your labour in your past life. Dying with a lot of energy (being a big fat robot), gives you far more points than dying with no energy.

Exponential Power Growth
Explanation: Exponential power growth is the term used to describe when players are rewarded for their achievements in the game, and so they are more effective, and are rewarded more. The cycle repeats until the game is unfair because one player (or team) is completely dominating with overwhelming power due to a couple of early achievements.
Pros: None. You never really want exponential power gain - though, in any game where you level up, it's a given. As a player gets stronger, they'll naturally be more capable when dealing with the same threats. Most games balance this out by making it so that over the scope of a 'round' or 'match', a player will never gain permanent advantages that an 'unlevelled' player cannot overcome with skill. For example, in Monday Night Combat, a non-upgraded player can still kill a completely upgraded one with skill.
Cons: An unbalanced game.
In Plain Sight: In Plain Sight, as a player gets kills and energy, and gets bigger, they also get stronger, they can jump higher, acquire targets at a larger range, their suicide detonation is bigger, etc. That said, they do not gain defence, so while they become a killing machine, it still only takes the regular dash attack to kill them. Also, as a player detonates with more energy, the points they gain is increased greatly. So, detonating after one kill yields next to nothing, while over 10 kills is a real game changer.

Transparent Player Actions:
Explanation: When a game makes player actions transparent, it means you can see and understand what the enemies are doing easily, and there is no real element of surprise.
Pros: Forces players to play in the open, without worrying about flanking, camping, stealth, etc. Depending on the style of the game, this can be good or bad.
Cons: In most games, removes strategic depth. Like it or not, camping, flanking, and sneaking are all valid strategies.
In Plain Sight: Players emit energy trails, that other players can follow to the player. Similarly, when players step on a part of the level, the ground lights up so that other players can see where the action is. The trails and ground light up more as you gain energy - so it's far easier to find more valuable targets.

How These Features All Come Together
So, Plain Sight implements all of these pretty flawed concepts, all in the one game - but it comes out great! Why?
They all cover each other's weaknesses.

The Big Head Mechanic and Exponential Power Gain mechanic work together to make for a very risky game style.
As you get more kills, you get more powerful, more deadly, but - you also get easier to kill.
Progression through Death allows the person to capitalize on the risks they have taken if they wish - or continue on, as the risk builds up higher and higher. As the risk builds, so does their reward if they are successful in committing suicide.
The Transparency of Player Actions is important as it increases the risk. An energy-filled player cannot hide and camp, they can only run and kill.

Conclusion:
The concepts above all work together perfectly to make a game style that is all about risk, greed, and chasing the most valuable players. And I love it.
It's great fun, it's an adrenaline rush whenever you have a long streak going and - I love how the game's gameplay almost seems to mirror its design. Beatnik Games took a gamble on mashing these features together, but it completely paid off.

I think this article is just saying that, well, first off, Plain Sight is designed masterfully - but also, that with enough thinking and creativity, you can find solutions to design problems anywhere, and even mash them together to fix each other.

Who knows? You could create a better Capture the Flag one day!