Project Requirements

Project Requirements

Project BrowserQuests™ is ambitious, seeking to combine players, authors, developers and marketers together and take the single-player RPG "old-school" experience to a whole new level. Such a project requires substantial planning, resources and talent.

The game primarily serves four distinct audiences: Players (who can create characters and adventure as much as desired), Authors (who can develop custom content assets such as text, graphics and music to tell their own stories), Programmers (who help write the custom code needed to drive the game) and Marketers who can purchase small banners that display to game players and help support the overall project financially. To meet the needs of these diverse audiences, the project addresses the following goals and requirements.

Project Goals

  • Build a common website and application infrastructure that serves players, authors, developers and marketers
  • Allow authors to submit quest-based content that improves the player's experience
  • Attract quality developers and graphic artists to help build the RPG infrastructure
  • Ultimately provide a quality product that marketers and advertisers will be willing to commit advertising dollars to

Game Engine Requirements

  • Single-player, persistent world environment (this is NOT a MMORPG)
  • Virtual game master ("GM") interface that interacts with individual players online
  • Dynamic game command mechanism that accepts player input for the GM to resolve individual encounters
  • Character management panels (for managing hero statistics, possessions and spells)
  • Environmental management panel (for interacting with encountered objects)
  • Auto map for displaying the player's immediate and overland surroundings
  • Time/Weather management system (controls game time and weather)
  • Complete administrative interface for developing and managing game content and associated resources

Technical Requirements

CMS Roles

By default, the DNN framework provides for four generic roles: Administrators, Authenticated Users (those who have specific log-in privileges), Subscribers (those who can automatically receive resources from the framework such as newsletters) and Anonymous (those browsing the site who have not logged-in). To meet the business needs of the project, additional roles have been added as well:

  • Administrator (default role). Reserved to Scott Huelsman and a tiny handful of very trusted administrators
  • Developer (new role). Those assigned programming and development responsibilities (and can do nearly anything in the system)
  • Author (new role). Those allowed to add, edit and otherwise manage RPG content (quest elements, graphics, audio, etc.)
  • Marketer (new role). Those who purchase ad campaigns within the system and help generate revenue for all involved
  • Registered (default role). Players who sign-up to play are assigned the Registered role and can’t edit any RPG content
  • Subscriber (default role). Not utilized within the RPG
  • Anonymous (default role). Site visitors who have no special authentication (not utilized in any special way within the RPG)