skdigital / vue-monster-slayer

Max Udemy Course Project with VueCLI 3, Flexbox - Monster Slayer Game Project

vue-monster-slayer

Summary

This project is a quick game that uses the following technologies & libraries.

• Yarn
• Vue 2.5
• cli 3
• flexbox
• GSAP animations

I also use an 'EventBus' architecture for component communication. I subscribe to my EventBus much the same as subscribing to an observable. The game works and I achieved the challenge objectives without directed help from the Udemy course community.

I am unaware of the shortcomings of using my EventBus and how this affects performance of my game, or whether this kind of architecture or solution is used in production.

I have noticed that a central data store would be ideal for health attributes and for game running booleans so that the state can be communicated and updated from a central location. At the moment there is so much interdependencie and direct communication between all pages that its starting to get a confusing as to where things are being updated etc...

Project setup

yarn install

Compiles and hot-reloads for development

yarn run serve

Compiles and minifies for production

yarn run build

Lints and fixes files

yarn run lint

vue-monster-slayer's Issues

feature_menuButtons

Currently: Buttons do not have any hover attributes when mouse over occurs or click down happens.

Preferable outcome: CSS class change when the mouse hovers over buttons and when click down occurs on the main menu.

issue_MonsterDamageAmount

Potential issue: The amount of damage a monster generates per turn could be too much and non-random. Please check the functionality completely.

issue_healthAfterWin

Problem: After winning a game and actioning a new game to start, AI Monster actions a turn and takes the health of the player straight away.

Solution: Player should always have the first move and should always start the game with 100% health.

feature_clearLogOnNewGame

Problem: When starting a new game the log doesn't clear recorded actions from the previous game.

Solution: Clear log action to clear all previously recorded logs when starting a new game.

issue_health

When player heals himself with health at 100%, messages still display in the log that the player is adding health.

This is a bug, as a player should only have 100% health as a maximum value. If the player starts a new game or heals to 100% health then the log should no longer display messages that show added health when no health is being added.

Instead, the when the player is at full health, if the user presses the health button then a message should display in the log component that the player is at 100% health.

issue_healthNewGame

Problem: Health doesn't always fully regenerate to 100% when starting a new game after WonLost dialogue.

Solution: Fix and test to make sure that health regenerates to 100% when commencing a new game after an old game.