Game Menu Shell讲解、system辅导、C#编程语言讲解、辅导c++
- 首页 >> CS Project 01B: UI - Game Menu Shell
Due Date: Sept 30 at 15:59pm
Points: 50
Late Policy: 5% Deduction for Each Full Day
Background: Professor Price made you roll a character by hand, on paper. Show him that you
can do better by using Unity to make a character generator! Create a game with a user interface
that will act as a scaffolding for the development of the rest of the semester. Using Unity
2019.4.### and the Canvas system, make a game to satisfy the following requirements.
Requirements:
1. Build a UI that should function as a ‘menu’ system to quit your game in editor mode and
executable mode. You will need Five menu options (buttons): About, Settings, Roll Character,
Play Game, and Quit. Roll Character and Play Game should be visible but not be available - that
will be int Project01c.When a user selects a menu option, your game will load a new unity scene
using SceneManager.LoadScene.
a. The UI should implement a UI Controller software design pattern.
b. The Play Game menu item should load a scene with a back button that send the player
back to the menu screen.
2. You must build and code this UI all by yourself. No additional assets (Free or paid for (Especially
the Unity Tutorials)) may be used.
3. You may not use external APIs to generate your character.
4. Must be coded in C# using Unity3d 2019.4.# or higher
5. Original art will score highest. Documented borrowed art will result in a higher score than
unattributed works. In general you should include a list of attributions in the form of a
bibliography.txt.
6. The assignment will be turned in on the class gitlab server at https://rijeka.sdsu.edu/ . Your repo
and unity project must be named CS583F2020_Lastname_Firstname_Project_1b . Do not initilize
your server with a readme. Create a Unity project with the exact same name as the Rijeka project.
Then link the two projects together via git commands. This will result in a merge conflict. For
maximum points, resolve the merge conflict.
7. Push your code to your Rijeka repository. When you are ready for grading, push you code with a
commit message of “Ready for Grading - Hi Kyle”
Category Excellent Very Good Good Poor
10 - 6 Points 5 Points 4-1 Points 0 Points
Graphics All original art. At least 1 original
graphic was used
to give the game
screen visual
appeal.
No original
graphics or
"borrowed"
graphics were
used to give the
game screen
visual appeal.
Little or no color
or fewer than 3
graphics were
included.
10 Points 9--6 Points 5-3 Points 2-0 Points
Folder Asset
Organization
All assets, scenes,
materials and scripts
are organized
according to best
practices
Most assets,
scenes, materials
and scripts are
organized
according to best
practices
One or two
assets, scenes,
materials and
scripts are
organized
according to best
practices
No assets,
scenes,
materials and
scripts are
organized
according to
best practices
15 Points 13-6 Points 5-3 Points 2-0 Points
Version
+Control
Quality
Frequent
Well explained
Commits that are
related to single
functional
change/requirement
Frequent commits
with multiple
functional
changes per
commit
Infrequent
commits, little or
no explanation
All commits at
or near end of
project with no
explanation
15 - 8Points 7-5 Points 5-3 Points 2-0 Points
Push back to
gitlab
Merge conflict
resolved to original
repo on rijeka
Some issues with
merge conflict
resolution, but
Some Merge
conflicts Partial
game few bug
No Push, No MC
resolution No
game no points
Due Date: Sept 30 at 15:59pm
Points: 50
Late Policy: 5% Deduction for Each Full Day
Background: Professor Price made you roll a character by hand, on paper. Show him that you
can do better by using Unity to make a character generator! Create a game with a user interface
that will act as a scaffolding for the development of the rest of the semester. Using Unity
2019.4.### and the Canvas system, make a game to satisfy the following requirements.
Requirements:
1. Build a UI that should function as a ‘menu’ system to quit your game in editor mode and
executable mode. You will need Five menu options (buttons): About, Settings, Roll Character,
Play Game, and Quit. Roll Character and Play Game should be visible but not be available - that
will be int Project01c.When a user selects a menu option, your game will load a new unity scene
using SceneManager.LoadScene.
a. The UI should implement a UI Controller software design pattern.
b. The Play Game menu item should load a scene with a back button that send the player
back to the menu screen.
2. You must build and code this UI all by yourself. No additional assets (Free or paid for (Especially
the Unity Tutorials)) may be used.
3. You may not use external APIs to generate your character.
4. Must be coded in C# using Unity3d 2019.4.# or higher
5. Original art will score highest. Documented borrowed art will result in a higher score than
unattributed works. In general you should include a list of attributions in the form of a
bibliography.txt.
6. The assignment will be turned in on the class gitlab server at https://rijeka.sdsu.edu/ . Your repo
and unity project must be named CS583F2020_Lastname_Firstname_Project_1b . Do not initilize
your server with a readme. Create a Unity project with the exact same name as the Rijeka project.
Then link the two projects together via git commands. This will result in a merge conflict. For
maximum points, resolve the merge conflict.
7. Push your code to your Rijeka repository. When you are ready for grading, push you code with a
commit message of “Ready for Grading - Hi Kyle”
Category Excellent Very Good Good Poor
10 - 6 Points 5 Points 4-1 Points 0 Points
Graphics All original art. At least 1 original
graphic was used
to give the game
screen visual
appeal.
No original
graphics or
"borrowed"
graphics were
used to give the
game screen
visual appeal.
Little or no color
or fewer than 3
graphics were
included.
10 Points 9--6 Points 5-3 Points 2-0 Points
Folder Asset
Organization
All assets, scenes,
materials and scripts
are organized
according to best
practices
Most assets,
scenes, materials
and scripts are
organized
according to best
practices
One or two
assets, scenes,
materials and
scripts are
organized
according to best
practices
No assets,
scenes,
materials and
scripts are
organized
according to
best practices
15 Points 13-6 Points 5-3 Points 2-0 Points
Version
+Control
Quality
Frequent
Well explained
Commits that are
related to single
functional
change/requirement
Frequent commits
with multiple
functional
changes per
commit
Infrequent
commits, little or
no explanation
All commits at
or near end of
project with no
explanation
15 - 8Points 7-5 Points 5-3 Points 2-0 Points
Push back to
gitlab
Merge conflict
resolved to original
repo on rijeka
Some issues with
merge conflict
resolution, but
Some Merge
conflicts Partial
game few bug
No Push, No MC
resolution No
game no points