Briefly stated, the game comes in two parts, the game driver, which is written in Java code, and
the content material. When you connect to a web page to play EdUGames, the page contains a tag
reference to the EdUGames "StartGame.class" applet on the EdUGames server. This is all the
browser needs to run EdUGames. The page may also contain applet parameters to indicate what
material is to be played etc. In the case of a Teacher's Set it may be a list of the serial
numbers of the Rounds to be played and the teacher's email address to send the results.
The content material also comes in two parts, the Master Data Base of Rounds and Sets, and the
Resource Library. Each Round (example) has a unique serial number and is a single record in the
Master Data Base. A Round may ask the players to place a tokens on a map, or to match states
with capitals depending on the type of game (See Game
list). In the former case, it must
reference a map to be displayed and that is where the Resource Library comes in. It contains all
the maps, drawings, sound bytes, videos, etc. used by the Rounds. A Set is a collection of
Rounds, Sets and links to Web Pages.
Each Round also contains information about its creators and owners and that is where the Royalty
Model comes in. Just like a book, poem or movie, a Round is a unit of intellectual property and
just like a book, poem or movie, EdUGames, as it's publisher, pays royalties. In summary, the
Royalty Model allows for multiple Authors, contributors and owners to create and participate in
the revenue of a Round.
In as much as there are over 20 different types of games, a means had to be created to allow for
balanced scoring. The solution was to target a score of 100 points for each Round if answered
correctly in an average amount of time by a single player. This can never be exact however, so
we allow the Set Author to adjust the scores for each Round in a Set. This is done as part of
the Compilation Tools.
The link on Scoring explains this in detail.