Access the full text.
Sign up today, get DeepDyve free for 14 days.
[Different types of game engines have been mentioned in Sect. 1.2 and a feature set to support pervasive games has been distilled and verified in Chap. 2 Using the resulting feature set from Sect. 2.3, a candidate engine is chosen in the same product line as a would-be pervasive game engine. Because the feature set requires support for a virtual game world with world persistence, and a shared data space with data persistence, a virtual world engine is chosen as primary candidate for, being an engine in the same product line as a would-be pervasive game engine. As proof-of-concept, a virtual world engine specific implementation is extended to support the entire feature set and used to implement the pervasive game, called Codename: Heroes. The game is briefly introduced from a cultural perspective and its resulting architecture explained. The explanatory case study in this chapter validates the chosen architecture and gives needed first-hand experience with the resulting architecture. Whereas features from the survey inform the architecture, the implementation of Codename: Heroes serves to highlight those features of particular importance and identify any open issues.]
Published: Mar 23, 2015
Keywords: Virtual World; Game State; Game Engine; Game World; Heterogeneous Device
Read and print from thousands of top scholarly journals.
Already have an account? Log in
Bookmark this article. You can see your Bookmarks on your DeepDyve Library.
To save an article, log in first, or sign up for a DeepDyve account if you don’t already have one.
Copy and paste the desired citation format or use the link below to download a file formatted for EndNote
Access the full text.
Sign up today, get DeepDyve free for 14 days.
All DeepDyve websites use cookies to improve your online experience. They were placed on your computer when you launched this website. You can change your cookie settings through your browser.