Vincent Alexander Seliang

The ‘start’ scene.

The initial place where the player will start.

The respawn point, just in case the player got killed.

An enemy that can either be hostile or docile, but it’s tall enough to hinder player’s movement.

A jump pad that doubles player jumping power.

A moving platform that moves in sinusoidal movement, where y = 0px and x = 100px (approximately).

A climbable wall.

The choice that the player has to make in order to progress, uses the Trolley Problem model.

End of the model.

 

Note: this page will be written in GDD (Game Design Document) form.

 

Introduction

Game title: P

Intended game systems: PC

Targeted age of players: 5 years old or older

Intended ESRB rating: E (Everyone)

 

Game Outline

Summary: P tells a story of a nameless square that tries to find his way home, called ‘the Ego’ after the nameless square falls into the place called ‘the Id’.

Game flow: P is a platformer that uses third-person view game that finds the nameless square finding its way home called the Ego after it fell to the Id.  As the Nameless Square venture through the Id, the game assesses the player perspective of the world and their moral compass. The challenges that the player will encounter are listed below:

• Traps such as pitfalls, hostile shapes, and spikes (notes: spikes will not be present until the player pass the first level)
• Choices that player must choose in order to progress.

To win the level, the player needs to reach the end the of the level and player will be rewarded with story progression as each level is completed.

 

Main Character

Protagonist name: The Nameless Square

Age: Unknown

Mode of movement:

• Walking
• Jumping
• Latching

Controls (Keyboard only):

• Right arrow – Move right
• Left arrow – Move left
• Up arrow – Jump
• Up arrow x 2 – Double jump
• Up arrow, while on a wall – Wall latch
• Jump while on a wall – Wall jump

Backstory: The Nameless Square lives at the Ego until he accidentally fell into the depths called the Id. Now it wants to find a way to ascend to its home.

 

Gameplay

Genre: Platformer

Point of View: Third-person, side-scrolling view.

Sequencing: Divided into different levels

Platform: PC

Number of Player(s): One

Mode of obtaining: Download

 

Game World

A sample of the first map, the tutorial level (game engine).

• The level starts at the upper left and end at the lower left.
• The tutorial map is the first region of the Id, which is the instinct.

 

Game Experience

Initial view:

• Player’s sprite
• the floor
• TextOne that says, “There no point of looking back.”
• TextTwo that says, “Follow the arrow to explore the land.”

Intended Emotion to be Conveyed: Discomfort and, depending on the player, variety of emotions.

Type of Music: Calming Instrumental, main music instrument is piano.

Audio Source: https://www.youtube.com/watch?v=xjoqx7wYbVw

 

Gameplay Mechanic

Mechanics:

• Every single wall can be used as latching
• Moving platform
• Wall climbing

Hazards:

• Pitfalls
• Moving hostile shapes.

 

In this final project, I do the front-end (and a little bit of back-end) using Visual Basic, which I made a form that allows the user to manipulate the tables of the database (in this case the administrator). Below is the screenshots of the script and the design of the form, following with the testing stage.

Form 1

This form acts as the login form, which assumes that only the manager that is allowed to edit and have full access to the database. This form also allows the user to use the ‘User Mode’, a mode that shows the prototype of the application that is inspired from commercial taxi applications. In order for the user to be able to access the database section of the program, the user needs to know a manager ID and its staff ID, otherwise, it will display a message box that says that either both or one of them is wrong, similar to online social medias’ login page.

Form 2

This form will only open if the user has successfully if the user knows the correct manager ID and staff ID. All of these database’s tables are stored in different datagridview objects. Datagridview object allows the user to edit directly on the object itself instead of using an external method and/or object to create any changes to the tables that is located in the database. There are several differences between the ‘MySQL Query’ tabs and the rest of the tabs as listed below:

• All tabs have the search bar, search button, update button, and delete button active, while the ‘MySQL Query’ does not.
• Only the ‘MySQL Query’ tab has the combo box to show the requested queries.
• Only the ‘MySQL Query’ tab’s content is uneditable, while other tabs allow the datagridview objects to be added, altered, and deleted, followed by clicking the ‘Update’ button to commit any changes to the datagridview object itself and the actual table in the database.

Form 3

This form can be accessed from the ‘Form 1’ object without the need of inputting the correct both manager ID and staff ID. The forms act as a prototype and a simulation of product that allows the user to use the service. The first part requires the user to input their current or the desired position to be picked up by the driver and the destination the user is heading to. When the user is done inputting the necessary information, the user can click the ‘Let’s go’ button to call a driver. It will lead the user to the next event, where the form informs the user that the application has successfully called a driver and shows the simulated distance between the pickup location to the destination and the price. The progressbar object shows the estimated time for the driver to arrive at the pickup location.

As the user click the ‘Let’s go’ button, the transaction will be recorded into the Jobs table, which can be checked from the database form (Form 2) and also updates the number of how many times does the user has used the service into the Clients table, which can be also checked in the database form.

Form 4

This form acts as a simulation for the user to sign up for the service. It basically allows the user to add themselves to the database by inputting the required information about the user, along with the type of service they need. If they clicked the ‘Accept’ button, the information will be added to the ‘Clients’ table. The ‘Return’ button will bring the user back to Form 3.

Form 3’s update

The new feature allow the user to cancel their trip at anytime, provided that the user has a reason for canceling the trip. As the user hit the ‘Confirm’ button, the reason will be recorded into the Jobs table, in the failReason column.

 

Project Name: Fastcab Database Manager

Project Member: Vincent, Archel, Charotama

Course: COMP6339 – Database Systems