2D Platformer Demo

This is a prototype demo. Its core mechanics are what was being focused on (2D platformer, run, jump, interact with enemies, gather items and skills). The core mechanics are going to be used in a different project later but were being tested in this demo game.

was made for the "Launch a Game! Boot Camp by Pro Indie Dev"

CONTROLLER FUNCTIONALITY ADDED
BOW AND ARROWS ADDED
CRATES AND TREES ADDED (Use heavy weapon to interact with them)

Default Controls:(Key Remapping available in menu)
Keyboard:
ESC = Menu (have to be out of full-screen view since its the same button)
WASD = Movement
E = Bow/Arrow (after picking up skill) *Bow becomes a melee weapon after arrows run out
SPACE = Jump
Left Mouse Button = Light Attack
Right Mouse Button = Heavy Attack

Controller:
Pause/Start Button = Menu
Left Joystick = Movement
Xbox (A)/ PS4 (X) = Jump
Xbox (X)/ PS4 (square) = Light Attack
Xbox (Y)/ PS4 (triangle) = Heavy Attack
Xbox (B)/ PS4 (O) = Bow/Arrow (After picking up skill) *Bow becomes a melee weapon after arrows run out

We are aware of 2 glitches at the moment:
1) NOW FIXED - A sprite glitch that happens during wall sliding causing the character to look like its floating in midair instead of against the wall. This feature will be corrected in later version of this prototype demo or in the actual game mechanics when placed in the other project later.
2) WORKAROUND APPLIED -
Original Note: Occasionally when entering the 2nd stage, the player is loaded near the treasure chest or the Orc. we are looking into this.
UPDATE1: So far we see that this is an issue that occurs in 2D games after SceneManager.LoadScene() is called in Unity. It has been an issue since around 2018. We will build a work around to resolve this at some point. Most people suggest making a spawn point and assigning the player to it. it seems to only effect the object that is on either tagged "Player" or on the "Player" layer that is pre-defined in Unity. We May try changing to a tag/layer that is user-defined one and updating all associated coding to look for that new tag/layer instead.
UPDATE2: We decided to not adjust the "Player" layer. Instead, we force the player game object to go to a specific location after loading. This has shown to be significantly more reliable instead of allowing the SceneManager.LoadScene() to place the player. This does cause a slight flash of the screen occasionally during level loading but it has proven to be consistent on placing the player correctly.

Items that need adjustment:
1) D-pad on controllers is not responding like anticipated, we are looking into this but the joystick is main control so it doesn't break the game. This seems to be a generic controller related thing. if you are experiencing this, please try to use a different controller.
2) Chrome browser doesn't seem to support generic controller functionality with WebGL games. If your controller isn't working with Chrome, please use a different browser such as Brave while we investigate this further.