While you’re building your browsergame, there’s one important point to consider: balancing your game.
A lot of developers create browsergames without thinking about balancing them first – this usually tends to result in games that are released with some serious balance issues. Certain characters might be over-powered in comparison to others, and certain items might be complete gamebreakers – things that make the game virtually unplayable for players without the item by comparison.
How will you solve the balance problem in your browsergame?
One approach that a lot of browsergame developers take is limiting users to a certain number of turns in a day – that way, a user who has all the time in the world and a user who can only sign in for 5 minutes each day can both remain relatively close to each other in terms of in-game performance.
While action-point/turn-based systems are a good way to keep your players a little more evenly matched, they don’t (unfortunately) fix balance problems – at best, all they can do is prolong the amount of time that it takes for a balance issue to appear.
Here’s an example: you run a small browsergame, with 5000 users who are active daily. Players can play the game in real-time, and at any given moment there are at least 200 players online at once, interacting with the game. In a weekly update, you push out a new sword that can only be found after defeating a particular boss monster. Unbeknownst to you, this sword in combination with the armor you released three weeks ago combine to form the most powerful combination in the game – capable of instantly killing any player who is attacked by a player using both of them.
In a real-time game, you’ll notice this issue fairly quickly – all of a sudden, a handful of players will be able to instantly defeat any other player. You’ll soon start to see complaints in your forums (if you have them), and you’ll be able to watch as more players find the item and begin to exploit the balancing issues present.
Now think of the same scenario, in the context of a turn-based game. Users get 25 turns per day, and it takes them 40 turns to get to the boss (if they don’t use turns, they stack up). It will be at least 2 days post-update for a user to get to the boss, let alone retrieve the sword – and if it takes them a full turn to attack a player, a user who just acquired the sword (assuming they had 50 turns saved up) will be able to instantly kill 10 players. Now, is the 10 players being instantly defeated by a single player a balance issue, or just a player who is that much stronger than 10 other players?
As you can see, there are pros and cons to either system. If you build a real-time system, there are more balance issues related to keeping casual and hardcore players even – but you will quickly find balance issues that have to do with gameplay features. In a turn-based system, there are far less problems keeping individual players balanced – but gameplay features can easily cause balance headaches that you won’t find for a long period of time.
So how will you balance your game? The answer is entirely up to you – although I would recommend setting your game up in a way that suits your development style. If you heavily test your changes before deploying them to a production environment, you can probably safely get away with a turn-based system – you’ll just need to make sure you thoroughly test all of your changes before you deploy them. If you’d rather have your players do the testing for you, and just fix balance issues as they come up – go for real-time. Either way, it’s your game – and the only important thing is recovering from balance issues when they do appear.