Contact us for your own Poker & Casino license now!

info@cubeia.com
Stora Nygatan 44, 111 27 Stockholm
  • No products in the cart.

tutorial Tag

The other day we release Styx to the public. It has served us well over the years as the main protocol generator for Firebase, so we thought we should be a bit more transparent with it. Speaking of "it", here's what "it" is:

  • A protocol format specified in an XML file.
  • Binary and JSON packaging for the above.
  • Automatic API generation in Java, C++, Flash, HTML5, etc...
This might still be a bit abstract, so in this post we'll instead show you how to use it for yourself.

In a series of posts we’ll do “Firebase From Scratch”, an introduction to Firebase and its concepts and ideas. Hopefully, reading this series will give you a firm grasp of what Firebase is and what it can do.

Having talked a bit about the server side game the last three episodes, let's have a look at services. These are extensions to Firebase you can write yourself to provide cross-game functionality and common behavior.

TicTacToe is one of the classic examples when it comes to multiplayer games. The rules and interactions are simple enough to make it a good example. We have now amassed a few examples. A few

In a series of posts we’ll do “Firebase From Scratch”, an introduction to Firebase and its concepts and ideas. Hopefully, reading this series will give you a firm grasp of what Firebase is and what it can do.

Now let's talk a bit more about handling actions in a server game. Why is the actions binary data as opposed to objects? Who do you do scheduling? Can you send actions internally between games, tournaments, services etc? Read on for some answers. The Table Instance When an action comes in to either of the "handle data action" or "handle object action", you are given two objects, the action itself and a table. It is important to re-iterate at this point that your server Game is a collection of objects that collaborate: the game instance and it's processors, the activator and all currently existing tables.

You should never keep references to table instances in your game or activator.

The above rule is because Firebase is build to transparently scale across multiple servers: Firebase needs to be able to "move tables" between different servers and will do so to make sure there's no data loss even if servers are crashing.

In a series of posts we’ll do “Firebase From Scratch”, an introduction to Firebase and its concepts and ideas. Hopefully, reading this series will give you a firm grasp of what Firebase is and what it can do.

In the last section we had a look at the game server code and its different components and we learned that "Tables" are the areas around which a number of players join and participate in games. Now we'll look at the creation of tables, which is done via a game "Activator".

In a series of posts we’ll do “Firebase From Scratch”, an introduction to Firebase and its concepts and ideas. Hopefully, reading this series will give you a firm grasp of what Firebase is and what it can do.

And in this installment we'll get to some actual code! Exciting! We'll start off with looking quickly at the major building blocks that goes into a server side Game, and then we'll dive into a traditional "Hello World".

In a series of posts we’ll do “Firebase From Scratch”, an introduction to Firebase and its concepts and ideas. Hopefully, reading this series will give you a firm grasp of what Firebase is and what it can do.

When it comes to the server code in Firebase, we divide it into three different things, three different artifacts which all have different responsibilities. In the last episode (see "A Maven Interlude") we kind of skipped past them, but let's take a closer look shall we?

In a series of posts we’ll do “Firebase From Scratch”, an introduction to Firebase and its concepts and ideas. Hopefully, reading this series will give you a firm grasp of what Firebase is and what it can do.

Actually, I lied in the last section: We won't talk about the server game implementation here. Instead we'll take a quick peak at Maven and how Firebase uses it. If you plan to roll your own using Ant or other tools, this is probably good for you to know anyway.


Fatal error: Uncaught exception 'wfWAFStorageFileException' with message 'Unable to verify temporary file contents for atomic writing.' in /home/cubeiaso/public_html/cubeiacom/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:46 Stack trace: #0 /home/cubeiaso/public_html/cubeiacom/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(620): wfWAFStorageFile::atomicFilePutContents('/home/cubeiaso/...', '<?php exit('Acc...') #1 [internal function]: wfWAFStorageFile->saveConfig('transient') #2 {main} thrown in /home/cubeiaso/public_html/cubeiacom/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 46