liggiorgio / ogd

Shared repository for the Online Game Design course project

OGD - Online Game Design

Shared repository for the Online Game Design course project.

ogd's Issues

GDD review & formatting

Global document review: major language issues, document formatting, and content coherence.

Missing media list

Media list in GDD is empty. Must find proper sample resources to include in the document.

Unconvincing introduction

Let's try to write a more interesting introduction, to intrigue potential players when reading about the game.

GTD review & formatting

Global document review: major language issues, document formatting, and content coherence.

GDD documentation changelog

Both GDD and GTD are missing the edit history section. This will be added as soon as the documents themselves are ready for production deployment.

Rules in boundaries section

The current elements in the "Boundaries" paragraph are reported to be Rules actually. Move them to the right paragraph, and define new Boundaries elements to include in the document.

Fill rules section

Rules section is missing directives about number and drawing of cards.

First writing of GTD

Complete first writing of the Game Technical Document. As soon as it is ready, a review will start to discuss its contents.

Development management

Section 8 of the GTD contains everything needed to understand the development processes of the team. Hardware used for testing and developing, software programs used for creating and editing, major development tasks, and the Gantt diagram must be included.

GTD cover page

Document covers must refer to the same template as a matter of coherence across production material.

Opening procedures

Game procedures are well defined when describing in-game action, but the game start is mentioned nowhere. Initial setting description and actions are required.

Missing backend technology references

The GTD doesn't refer to valid libraries/technologies for back-end implementation. Define these within other members.

GTD documentation changelog

Both GDD and GTD are missing the edit history section. This will be added as soon as the documents themselves are ready for production deployment.

Missing game logline

Insert game logline into the GDD, it is available in the latest version of GCD from the current development docs branch.

Unconvincing game description

The game description should arouse someone's interest without being annoying. Too many details are boring, though it must deliver a clear message about the game contents and game action type.

GDD cover page

Document covers must refer to the same template as a matter of coherence across production material.

Definitive game name

We need an appealing name for our game. This issue is long-term until a good name comes up, before the latest deliveries.

Poor key features

We must expand this section to include clearer, more interesting elements. Game content should ideally be unique, or at least we try to make it so: we need some more ideas.

Missing frontend technology references

The GTD doesn't refer to valid libraries/technologies for front-end implementation. Define these within other members.

Unclear target platform

We may better define this when working on the technical document. On the other hand, I guess prof. Ripamonti just wanted us to define a smartphone/tablet distinction.

Target players

"One to two", "Single player and cooperative multiplayer", "PvE games", "PvP 1-vs-1" were underlined as mistaken. We must not define the player role in the game modes, but rather its profile as a possible user. IMPORTANT: Bartle's type is missing, must be added ASAP.

First writing of GDD

Complete first writing of the Game Design Document. As soon as it is ready, a review will start to discuss its contents.