GAME DESCRIPTION:
A game where your objective is to clone builds using items found in the shop for profit.
RATINGS:
Visual Appeal: 16/20
Sound/Audio Design: 15/20
Completeness: 30/30
License: 30/30
Originality: 20/50
Gameplay: 30/50
Performance: 40/50
User Friendly/Intuitive: 80/100
Codebase: 110/150
FINAL SCORE: 371/450
FINAL THOUGHTS:
For a concept that isn't original, it is still intriguing and with a few small changes, I think it would boom as an online server. Defining custom sizes for schems and building them for others would be great. Timing the builds and having a leaderboard would be awesome.
NOTE: Recommended/not recommended is based on if the score is an 84% or higher.
Visual Appeal scored high because: Although shops are nothing special, the game itself looks alright.
Sound/Audio Design scored high because: Sounds are important. I would give 20, but the only song I head has this repeating arpeggio that gets rather annoying after time.
Completeness scored high because: The game accomplishes what it claims to do.
License scored high because: Permissible license.
Originality scored low because: Building replicas of buildings in games has been done for a while now.
Gameplay scored high because: It's fun, but I can imagine the game losing its luster after completing the schematics. Maybe add the ability to create them for players online?
Performance scored high because: As far as it goes, it isn't a taxing concept, but schems can take nearly a second to load in some instances. More of a Minetest issue, but my recommendation is to load everything at start and keep it loaded for a seamless experience.
User Friendly/Intuitive scored high because: Signs were hard to read at spawn, and putting errors in the chatbox is a little inconvienent to read. Otherwise, easy to understand what the goal is.
Codebase scored high because: Little copy/pasting in node defs, also I am a little uncertain as to why you get player names and hand it to a function when it is used repeatedly. Just pass a playerref and have the function grab the player name.
GAME DESCRIPTION: A game where your objective is to clone builds using items found in the shop for profit.
RATINGS:
Visual Appeal: 16/20
Sound/Audio Design: 15/20
Completeness: 30/30
License: 30/30
Originality: 20/50
Gameplay: 30/50
Performance: 40/50
User Friendly/Intuitive: 80/100
Codebase: 110/150
FINAL SCORE: 371/450
FINAL THOUGHTS: For a concept that isn't original, it is still intriguing and with a few small changes, I think it would boom as an online server. Defining custom sizes for schems and building them for others would be great. Timing the builds and having a leaderboard would be awesome.
NOTE: Recommended/not recommended is based on if the score is an 84% or higher.
EVALUATION:
Visual Appeal scored high because: Although shops are nothing special, the game itself looks alright.
Sound/Audio Design scored high because: Sounds are important. I would give 20, but the only song I head has this repeating arpeggio that gets rather annoying after time.
Completeness scored high because: The game accomplishes what it claims to do.
License scored high because: Permissible license.
Originality scored low because: Building replicas of buildings in games has been done for a while now.
Gameplay scored high because: It's fun, but I can imagine the game losing its luster after completing the schematics. Maybe add the ability to create them for players online?
Performance scored high because: As far as it goes, it isn't a taxing concept, but schems can take nearly a second to load in some instances. More of a Minetest issue, but my recommendation is to load everything at start and keep it loaded for a seamless experience.
User Friendly/Intuitive scored high because: Signs were hard to read at spawn, and putting errors in the chatbox is a little inconvienent to read. Otherwise, easy to understand what the goal is.
Codebase scored high because: Little copy/pasting in node defs, also I am a little uncertain as to why you get player names and hand it to a function when it is used repeatedly. Just pass a playerref and have the function grab the player name.