Jump to content
  • Advertisement
  • entries
    7
  • comments
    6
  • views
    1816

Developers Diary #1. Game design and research.

Clarus Victoria

2521 views

Hello!

Merry Christmas and Happe New Year everybody! Lina's here. Thanks for checking our blog again :)

I would like to share with you a bit of our development jorney with the focus on the new game, Egypt: Old Kingdom.  

It all begun with the idea of making a strategy game which will be truly historical, not only set in historical decorations, like many other strategy games. But having some experience in the gamedev industry, we didn't want to rush into an ambitious complicated projects which we will have no chance to finish.

In 2013 our first game Stone Age was released. It was made by Mikhail, the leader and the mastermind of our team. The game was intentionally simple and focused on workers management. The feedback was mostly positive, so we kept the gameplay, and added more functions for the next project, Bronze Age. It became our main approach to making games - present the concept, check the feedback, keep the good parts, get rid of the bad parts, add some new features. On and on. Games got more complex, the team got more members in order to divide tasks like programming, art and game design.

The most challenging part of the process, aside of solving thechnical problems, was the historical research. Everything had to be 100% according to the history. For the games like Bronze Age and Marble Age Mikhail somehow managed by himself, but it changed when we started to work on Predynastic Egypt. The support came from Center of Egyptian Study of Russian Academy of Science (CES RAS). Scientists who work there are not only in the University, they are also archeologists and their support was invaluable. 

That's how our main routine of game production was established. It's based on our ideas, players' ideas and scientific data. That's how, by the time we started to work on Egypt: Old Kingdom, we had a clear image of what we would like to make.

Before we will get into a more detailed explanation, let's cover the basics:

The history fo the Ancient Egypt is commonly divided by these main periods (credits to Wikipedia):
Early Dynastic Period    3150–2686 BC
Old Kingdom    2686–2181 BC
1st Intermediate Period    2181–2055 BC
Middle Kingdom    2055–1650 BC
2nd Intermediate Period    1650–1550 BC
New Kingdom    1550–1069 BC
3rd Intermediate Period    1069–664 BC
Late Period    664–332 BC
Predynastic Egypt game was set in 5000-3000 year B.C. in the place called Nekhen, or Hierakonpolis. In this game player has to develop the city, discover new territory and learn ancient technologies. At the same time (s)he learns about the very beginning of Egyptian civilization.
Egypt: Old Kingdom is the sequel, the next chapter of the story. It begins with a group of people sent from Hierakonpolis to discover a new territory. It overlaps with Predynastic Egypt by 500 years. The period of the new game is 3500-2140 B.C. Said group of people came to the Lower Egypt border, where they will have to establish a new settlement, Memphis. 
 
After Predynastic Egypt was released, first people to start the research for a new game were our artists, Maxim and Ivan. For their part of the job, they had to find out what how did Memphis look like at that time? Surely it wasn't the same as today. As they found out, during Old Kingdom period Memphis was less dry, it was a savannah. It resembled a lot the current nature of the South Sudan. 
With this reference they were able to start sketching maps and arts for a new game.
 
After that the main research for the game design begun. It included reading a huge amount of  historical sources and the work with scientist. It's a whole another topic, so we'll keep it untill the next post. To finish today, please enjoy this beautiful video about the nature of South Sudan. See you next time!
Our sources. Please subscribe and add our new game to your wishlist!
Egypt: Old Kingdom on Steam;
Predynastic Egypt on Steam;
Our community on Facebook;
Our Twitter.

 

P.S. I try my best to write without mistakes. But English is not my native language, so some mistakes are inevitable. Please don't hesitate to correct me if you see any, I will really appreciate it!



4 Comments


Recommended Comments

2 hours ago, jbadams said:

Your English is actually very good! Thanks for sharing!

Oh, thank you so much! I'm really very happy to hear people saying that! :)

Share this comment


Link to comment

Hello! Thank you for sharing and as mentioned above your English is very good! What I found are mostly typos:

experiens -> experience

"we didn't want to rush into an ambitious complicated projest which we will have to chance to finish." Here I had no problem with understanding but I think you should write "projects which we will have no chance to finish". (And ye typo in projects word)

Looking forward to second dev diary!

Edited by RootKiller

Share this comment


Link to comment

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
  • Blog Entries

  • Similar Content

    • By Defend
      Obligatory disclaimer - Yes this is for academic purposes, not for making actual games.
      I've been employed as a Software Engineer for 2 years but still feel like a beginner when it comes to writing a game engine (and much of coding in general). What little experience I have with writing 3D software from scratch is from super rough university projects (which we called "engine" but that's definitely debatable). Meanwhile, my current job doesn't really take me down this line of learning.
       
      This thread is to ask for advice; mainly pointers to good guides, or comments on what structural approaches are considered to be good ones. I'm looking for something that teaches me about how to structure a game engine so that:
      it's good for learning about writing an engine it's not completely devoid of modern techniques it will be usable for later feature learning; networking, AI, unit testing, etc. (I imagine this criterion is typically a given anyway.)  
      Some things I'm aware of so far (you may want to comment on any of these):
      https://www.gamasutra.com/blogs/MichaelKissner/20151027/257369/Writing_a_Game_Engine_from_Scratch__Part_1_Messaging.php I also have the book Kissner recommends: Game Engine Architecture by Jason Gregory. From what little I've read of it, it appears more advice than structural guide. ECS was a buzzword back when I was at uni, but the more I google it the more it appears to have become a dirty word. Unreal Engine's source  
      Regarding ECS: For all the flak it appears to generate nowadays, it is at least a structure. If ECS isn't recommended I'm interested in what other general structural approaches there are.
      Regarding Unreal: I'd love to jump in and learn how Unreal Engine's structure works, but it might be biting off more than I can chew. 
      Language of choice is C++.
       
      Thanks
       
    • By Ikkon
      Hi guy , i wanna really quickly introduce myself , So i'm a 18 year old Highschool student that have been for a while really pationate about video game (i have been doing Esport , Streaming all that really fun stuff) but lately i had to made a choice about what i wanna do in life and i'm pretty sure its going to be in the video game industry. Last year i started learning to use UE4 , pretty much only for fun trying to recreate cool stuff i was seing in the game i was playing at that time. But now , i wanted to trie creating something of my own so i wanna show you what a got in the head. Also , I'm french so sorry if my spelling is quite right.. 
       
      So in Short , i was playing lately alot of FPS (Quake champion , Law Breaker and bunch of other cool game). I was talkinh with my friend and its pretty much their that a got the global idea of what this game is going to be. I wanted to take little simple game mecanics from every game and put them i one unique game. For exemple , Player could Strafe Jump like in quake , while other Start randomly Wall running like in Titanfall 2. After i came up with what would be the game objective , because player won't start playing a game for no reason . I didn't played CTF game for a long time so , i decided why not make this a CTF game , But ctf is kinda mainstream and really linear in term of game play, 
      This is when my friend had this idea of <<Why not let the player decide if the want to play it ''Run it down to the flag'' or ''let's just #*@! the other team'' (sorry for the bad words) >>. at this time i had a clear idea of what would exactly be the Core ''gameplay'' (if we can call this gameplay).  To win you have two option :
      1- Capture the flag and bring it back to your's. If you managed to do so , the game instantly stop and you win. 
      2- Kill all the enemy team.
      Now you most be thinking , <<Well how? they will just respawn right?>> well no , because i came up with the idea of limiting the number of time player can respawn using some kind of respawn point system. 
       
      i'll came up with more details later (i have to go to my next class) , but let me know what you think about my idea? what should i add or ajust? 
    • By EnderStaffExe
      Hello! I'm new to the scene of video game developing and was wondering if anyone here has any experience developing 2D fighters and are up for making a little test demo to see if the idea would catch on to the public? I have no way of paying but I want to put the demo onto Kickstarter and I will pay a good amount if I get a good amount. Please, if you want to contact me for more info, add me on my Discord or Twitter. Thank you, and see you later!
      (Twitter: @enderstaffexe
      Discord: EnderStaffExe#3193)
    • By Heretic Arts
      Hello, 
      We are an American based videogame development team that crafts games utilizing neural networks, handcrafted art, studio quality audio, and immersive storytelling to provide the player with an unforgettable experience. Our current team comprises of a Software Engineer, Designer, Producer, Audio Engineer, and a systems admin. Obviously we are missing an art staff! Now, that being said, we have outsourced our concept art for the game to an experienced artist. We are wanting talent to join us to take it the rest of the way with animation and art. If you are interested in joining the team and feel that you are ready to work along a committed team, send a sample of your work and contact information to HereticRecruitment@HereticArts.com. 
      Job Specifics: 
      General: 
      Unpaid. This is normal. We all have fulltime careers outside of the team, but if there is money to be made upon release, it will be split evenly - no questions asked.  All expenses are paid by Administrative Team (GSuite account). So no worries - We want someone to join, have fun and create with us! Expectations of meeting weekly (via internet) and taking direction from producer.  Open minded  
      Skill sets: 
      Experience in designing and creating character art.  Full adobe suite.  Maya experience preferred.  Experience with developing for the Unity Engine.  Willing to work with design team to incorporate their ideas into art.  Knowledge of game design documentation and how it pertains to art creation.  In depth sprite animation knowledge. 
    • By Samuel Aponte Sustache
      Ok am not an game developer but I really got annoying when a player uses aimbot and no way as a player to do a thing. Im graduated as electronic technician and I study the nand.
      This guy can be implemented on our game program as a protection in case of cheating.  The objective of a cheater is for example 7, 10, 15, kills on a row but what if the player install a nand program and instead of the cheater kill he automatically dies....."wtf" he will be confuse.  What about a nand program.  If the player suspects cheating or server admin then you will apply the cheater the medicine and he will eventually goes.
       Thanks
      Samuel Aponte 

×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!