Admin Client Proposal for Game Development: Features and Functionalities, Study Guides, Projects, Research of Software Engineering

The proposal for an admin client in game development, which includes the ability to add, remove, or modify various game elements such as items, location, quests, game events, interactions, and factions. The admin client also provides user controls for managing players. The implementation concerns and features for each functionality.

Typology: Study Guides, Projects, Research

Pre 2010

Uploaded on 08/19/2009

koofers-user-5d1-1
koofers-user-5d1-1 🇺🇸

9 documents

1 / 2

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Game Admin Client Proposal
The utility of an Admin Client is threefold:
1. Having a content-creation interface will streamline development of content.
2. Demonstrates the effective functionality of our project subsystems (interaction
server, management server, interactions repository, authentication and
communications module, etc.).
3. Since the Player client’s abilities/features is a subset of the Admin’s
abilities/features our Player client can be proved to function properly if the Admin
client can as most client-end/communications obstacles (not all, but most) will
have been encountered during the creation of the Admin client.
To that end, an Admin Client needs to have the following features above and beyond the
normal client. A quick discussion of these will follow the list.
The Admin Client requires the ability to add, remove or modify any of the following:
oGame Items
oThe Game World’s geography/concept of location
oQuests
oGame Events
oServer-triggered/-scripted Interactions (i.e. night/day/natural disasters).
oFactions
Adding Game Items
-Simple .dll sent to server, which becomes a template in the item template
database.
Removing Game Items
-Remove specific references of the item from any inventories or game locations.
-Remove the template from the item template list.
Modifying Game Items
-Implementation concern:
Altering a game item template could automatically cause all the items to update
all instances, but there could be an issue with remaining field values in the
database (aka removing old ones) and providing all clients with the updated
template as soon as possible.
Location/Spatial Add/Remove/Modify
-Implementation concern:
For ease of implementing this, it could be best to all items, users or not, within a
given (x,y) to (x,y) area. Having a mass admin_move_all_within implies a
necessary admin_move_item sort of functionality. Thus from here we derive
additional, but useful, features. However, since location is merely an attribute,
this would not be hard to accomplish given the ability to make a specific
admin_modify_item for the purpose.
pf2

Partial preview of the text

Download Admin Client Proposal for Game Development: Features and Functionalities and more Study Guides, Projects, Research Software Engineering in PDF only on Docsity!

Game Admin Client Proposal

The utility of an Admin Client is threefold:

  1. Having a content-creation interface will streamline development of content.
  2. Demonstrates the effective functionality of our project subsystems (interaction server, management server, interactions repository, authentication and communications module, etc.).
  3. Since the Player client’s abilities/features is a subset of the Admin’s abilities/features our Player client can be proved to function properly if the Admin client can as most client-end/communications obstacles (not all, but most) will have been encountered during the creation of the Admin client. To that end, an Admin Client needs to have the following features above and beyond the normal client. A quick discussion of these will follow the list. The Admin Client requires the ability to add, remove or modify any of the following: o Game Items o The Game World’s geography/concept of location o Quests o Game Events o Server-triggered/-scripted Interactions (i.e. night/day/natural disasters). o Factions Adding Game Items
  • Simple .dll sent to server, which becomes a template in the item template database. Removing Game Items
  • Remove specific references of the item from any inventories or game locations.
  • Remove the template from the item template list. Modifying Game Items
  • Implementation concern: Altering a game item template could automatically cause all the items to update all instances, but there could be an issue with remaining field values in the database (aka removing old ones) and providing all clients with the updated template as soon as possible. Location/Spatial Add/Remove/Modify
  • Implementation concern: For ease of implementing this, it could be best to all items, users or not, within a given (x,y) to (x,y) area. Having a mass admin_move_all_within implies a necessary admin_move_item sort of functionality. Thus from here we derive additional, but useful, features. However, since location is merely an attribute, this would not be hard to accomplish given the ability to make a specific admin_modify_item for the purpose.

Add Quest

  • This should be similar to, or a more robust version of, the user quest_create functionality.
  • Necessarily it sets up the trigger/status graph and stores it in the quests section of the database.
  • Implementation Concern: We haven’t settled on where quests are stored fully. Removing Quest
  • Alters the trigger/status graph.
  • All people within the given quest who are at some now-unreachable point x should be returned to the nearest node y which branched off towards x but is still within the quests altered flow. Removing Quest
  • Remove graph from its data storage location.
  • Player’s status within the quest (stored as an attribute), should be removed from all players. Game Effects, Server Interactions Add/Remove/Modify
  • Game-fired events should be editable at any time.
  • Implementation Concern: Events are placed into a queue when called, and so if it is already within the queue, the options are to extract it from the queue or let it be and just be satisfied that it will never fire again now that it is removed from the servers list of time- triggered events. Create Faction
  • Add faction to the db with the necessary variables, i.e. creator.
  • Creator is added to the member list. Modify Faction
  • Modifying memberships
  • Modifying abilities/attributes of the faction or those provided by the faction.
  • For those provided by the faction, they should also be removed from the members who have them in their list as a result of membership. Delete Factions
  • Remove the members of the faction from the faction. This is attribute modification.
  • Remove faction from db. User Controls
  • admin_kick_player ( id )
  • admin_ban_player ( id , timespan )