In this post I’ll go a little over some thoughts on the Swarm system and post some screen captures from the login/registration system built so far.
Swarm System
The Swarm system will basically be a way for people to compete as teams/groups and provide advantages to those who belong to a Swarm.
Swarms will cost a set amount of gold (and/or crystals) to create and will have a member limit of between 10-20 to prevent Swarms from becoming too large and to level the playing field slightly.
An advantage of being in a Swarm is to have a percentage of your gold protected from theft when you lose a battle. My idea at it’s current point is to have no form of banking in the game so any gold amassed is subject to theft if you lose battles. My initial thought on this is to have, let’s say, 10% maximum of your gold subject to theft from each lost battle, then from being in a Swarm, of that 10%, an extra 10% is protected.
Then have the option of being able to upgrade certain aspects of your Swarm (one being gold protection) up to a maximum of 60-70%. This would mean that being in a Swarm could potentially leave you with only 3-4% of your gold vulnerable as opposed to the full 10%.
Other advantages may consist of more quests available to members of Swarms depending on the number of members in the Swarm. A Swarm with 5 members may have an additional 10 quests available to each member, whereas one with 15 members could have up to 50 extra quests available to any given member.
Login/Registration
The login and registration pages have been made as simple and easy to use as possible.
Below is an example of an attempt to login to the game with a non-existent user name, as you can see the user is greeted with a red message just above the input area for the user name. They never have to leave the same page to attempt login, any errors that can be picked up before submitting for further validation will be displayed promptly (such as user name/password too short or too long), and the others will be displayed in a few seconds at most on a slow connection.

The login and registration pages also have a Dragon Struggle header added to them and links to both the Login and Register pages just underneath it to make navigation easier.
All errors encountered during registration will act the same as the login page, showing errors directly above the input area they relate to. You can see a couple of examples below:


In my previous post, I also talked about limiting the number of accounts on any one IP address to 2. In the image below, you will see what a user will see if they are about to run into this problem:

The reason for limiting the number of accounts on any one IP is due to cheating. Many people will make tens, sometimes even hundreds, of accounts to send currency/items/other things to their main account or to even collect referral rewards on their main account. Limiting account creation on IPs will not stop this, but it will slow them down as they will need to make 2 accounts, switch proxy, make 2 accounts, switch proxy, etc.
Next Post
That’s all for this post, I hope you’ve enjoyed reading this series of posts so far.


