Jump to content
  • Advertisement
Sign in to follow this  

game design & actual logical code theory resources? language agnostic

This topic is 554 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hey there,


I am not a good coder at all, making a game in unreal because I can understand blueprints. 


I am looking for any (basic) theory resources to do with game design & game logic, but searching 'game design' usually means 'philosophical youtube videos' (great and inspiring) or 'game logic', (language dependent), and as i'm using blueprints, a heap of c++ code or whatever isnt very helpful, although using BP i am slowly understanding the structure of code, albeit very slowly. I was never taught and it just doesnt go in as well as visual things like BP.



Any books or online resources with simple game structures?  so I can start making simple things in blueprints?  like a game design theory bible?

ideally, flow diagram style.   ?


thanks for any help - finally after years of thinking I cant do it, UED4 is actually enabling me to get somewhere

Edited by rasseru

Share this post

Link to post
Share on other sites
You should ask game design questions in the Game Design forum. You'll get answers
from game designers there.
This forum is for technical (programming) questions.

Share this post

Link to post
Share on other sites

most games are a form of real-time simulation software.

the basic algo is:

1. draw everything (render)

2. process user input (input)

3. move everything (update)

repeat until quit.

grab paper and pen and draw the flowchart for that.

the basic algo for render is "for each visible object, draw it". this too can be expressed as a simple flowchart.

but very soon technical details make things trickier.

polled input: for each pressed control - process that control.

queued input: for each input message. process that message.

similar, but not quite the same.

at this point, almost all examples will be language specific.

what you want is the algos that code implements. good examples will explain the algo first.

by googling algos as needed and drawing up the flowcharts from the descriptions you should be able to get what you want.

eventually you'll come to picture all but the most complex flowcharts in your head just by reading the algo, and wont need the diagram on pen and paper anymore.

Share this post

Link to post
Share on other sites
Sign in to follow this  

  • Advertisement

Important Information

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

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!