MoonsideGames
/
encompass-cs-docs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

slight revisions
continuous-integration/drone/push Build is passing Details

main
Evan Hemsley 2020-07-27 20:55:17 -07:00
parent 5af3e5df66
commit d47a6240fe
1 changed files with 1 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/why/architecture/actor_model.md
View File

@ -6,9 +6,7 @@ weight: 20
You are probably very familiar with the Actor Model as a game designer. It is the structural idea behind most of the game code I have seen, though this is slowly changing.
The Actor Model is, unsurprisingly, a structure based on the concept of **Actors**. An Actor is an object which contain both data, referred to as *properties*, and logic, referred to as *methods*.
Object orientation is an intuitive idea when it comes to building simulation-oriented applications such as video games. We think of each "thing" in the game as a self-contained Actor which can be acted upon externally via methods. For example, in the game Asteroids, we could think of the game this way: the ship is an Actor, the bullets the ship fires are Actors, the asteroids are Actors, and so on.
The Actor Model is, unsurprisingly, a structure based on the concept of **Actors**. An Actor is an object which contains both data, referred to as *properties*, and logic, referred to as *methods*. It is an intuitive idea when it comes to building simulation-oriented applications such as video games. We think of each "thing" in the game as a self-contained Actor which can be acted upon externally via methods to manipulate their state. For example, in the game Asteroids, we could think of the game this way: the ship is an Actor, the bullets the ship fires are Actors, the asteroids are Actors, and so on.
Unfortunately, things aren't quite this simple when it comes to more complex games.