Skip to main content
↑
↓
Spherical forums
Community for the
Sphere game engine
New?
Contact Us
to register an account!
1 Hour
1 Day
1 Week
1 Month
Forever
Community
Help
Search
Recent Posts
Log in
Contact Us
News
Spherical
Facebook
-
Twitter
-
Discord chat
New?
Contact us
to register an account!
Creations
Game Development
[ebook] Game Programming Patterns
1
Print
Topic: [ebook] Game Programming Patterns
(Read 5108 times)
previous topic
-
next topic
0 Members and 1 Guest are viewing this topic.
N E O
Hero Poster
Posts: 585
Making it happen!
Logged
Administrator
Senior Administrator
[ebook] Game Programming Patterns
August 19, 2014, 08:59:00 pm
http://gameprogrammingpatterns.com/
(also
on GitHub
)
The author, Bob Nystrom, apparently worked (works?) for EA and created the
Magpie programming language
so I'm pretty sure he knows his stuff. It's pretty hardcore, though, and also deals with game programming aspects that theoretically may already be taken care of for Sphere users by the engine itself, so don't go in expecting a read aimed at novice devs.
That's not to say it's not useful for Sphere users or even the few of us here developing/maintaining Sphere-compatible engines. Basically, if you have an interest in learning how a game development professional recommends organizing task-specific sections of code it will be a useful read, especially if you're a fan of the book
Design Patterns: Elements of Reusable Object-Oriented Software
.
Radnen
Big Chungus
Posts: 1,440
Sphere Studio Developer
Logged
Senior Staff
Wise Warrior
Re: [ebook] Game Programming Patterns
Reply #1
–
August 19, 2014, 09:27:49 pm
Quote
Especially early on, it's common to write code that you know you'll throw away.
Loved this statement.
Also his Data > Code section in "Bytecode" under Behavioral Patterns is great. I oftentimes hardcode spells and enemies when they should have existed as data.
I keep coming from the mindset of small demo games and tend to forget when you go big your architecture has to develop past that 48 hour compo type of coding that I tend to employ. It's the driving motivation for my RadLib library which I use in all of my games past 2007/8.
If you use code to help you code you can use less code to code. Also, I have approximate knowledge of many things.
Sphere-sfml
here
Sphere Studio editor
here
1
Print
Creations
Game Development
[ebook] Game Programming Patterns