bratah123/brackeysjam2024.1

Our game submission for Brackey's Game Jam 2024.1

BrackeysJam2024.1

Our game submission for Brackey's Game Jam 2024.1

brackeysjam2024.1's Issues

Users can die from taking too much damage

Users can interact with collectible resources

• Collectible resources should be present in the overworld
• Collectible resources should be present in dungeons
• Interacting with them should allow the user to obtain items
  • Items can be recovery potions
  • Items can be gear
  • Items can be other materials that can be sold to shops

Users can enter dungeons.

User story for dungeon related issues.

• #11
• Enterable Doors
• NPC's in Lobby/Home Dungeon
• Tutorial Dungeon (?)

Create the Main Menu Scene

Users can see their HP Bar

Create enemy Node

Users can pick up new weapons to use

Users can get moved along in progression inside dungeons

Upon entering a door in the dungeon, the user is moved to the next room and the door they came from should have a tween where it disappears. This gives the user a sense of moving forward

Users can fight new random monsters every time they enter a door

• Monster type should be randomized
• Monster stats should scale with dungeon depth
• Monster location should be slightly randomized

Create dungeon room layouts

• Create/import suitable tile maps (check with Deltzio)
• Create at least 10 different dungeon room layouts for normal rooms using tile map
• Devise some way of noting plausible spawn points in each layout
• There should be more spawn points planned than used
  • Procedural generation step will pick which spawn points to use via RNG
• Create at least 2 different layouts for boss rooms
  • (optional) gimmicks in boss rooms, like loot boxes or destructible scenery

Users should be able to target weak points of bosses

Areas like necks can be given an independent hitbox for detecting critical hits which award more damage

Users should be taught how to control their character

• Keybind/control hints in HUD where appropriate
• Some kind of rudimentary tutorial system via a tutorial dungeon (optional)

Users can experience dealing with semi-intelligent enemies

• Enemies at idle should slowly roam a fixed area
• Enemies should chase user when user is too close
• Enemies should be able to lose sight of of user (i.e. stop chasing)
• Bosses can have at least skill(s) for ranged/AOE attacks

Users can attack with their weapon

• Activated on left-click
• Basic sword swing that hit any entities in range
• Damage dealt depends on stats of weapon

[FEAT] Link Main Menu Buttons

Link Main Menu Buttons to the lobby_dungeon scene. (When player clicks on Start Game button, send them to lobby.

When player clicks on Help button, send them top another Help Menu page that displays the controls (and credits if want)

Users can obtain currency

Users can kill monsters/bosses

Monster related user story.

• #16

Create the initial Home/Lobby Dungeon Area

Users can dodge/roll their character

Users should have scores tracked

Global variables

FLOORS

• Simple accumulator for number of floors cleared in dungeon

BOSS_KILLS

• Simple accumulator for number of bosses killed

HEAL_POT_COUNT

• Simple accumulator for number of healing potions consumed

DEBUFF_POT_COUNT

• Simple accumulator for number of debuff potions consumed
• Should not be incremented if players consumes one when effects from the same kind of potion have not yet expired

TIME_PLAYED

• Number of seconds spent in the dungeon

Tabulation functions

calculate_score()

• Increment using some function of the number of number of floors
  • It should scale more than proportionally with dungeon depth
    • i.e. fewer floors => more linear; more floors => larger increment per floor
    • e.g. + floori(exp((FLOORS-9)/7) + (FLOORS/10) + 1)
  • If implementing critical hits via boss weak spots, perhaps increment another accumulator for crits
    • e.g. + (CRITS * floori(pow(BOSS_KILLS/13, 2) + 1))
• Variable change on potions consumption
  • Decrement for healing potions (e.g. - (15 * HEAL_POT_COUNT))
  • Increment for debuff potion (e.g. + (1000*DEBUFF_POT_COUNT*floori(BOSS_KILLS/3)))
• Decrement for some function of time played
  • I.e. if you can clear more mobs in less time, your score will be better
  • e.g. - pow(floor(TIME_PLAYED/320), 2)

Users can pause the game

Users should have an inventory

• Shortcut key to open inventory menu
• Inventory menu UI for browsing items in inventory
• HUD for current selected consumable (optional)
• HUD for current weapon (optional)

Users can see doors appear upon clearing a room

There should be 3 doors with tween animations for appearing. This should happen when all mobs/bosses are killed in the room.

Users can "talk" to NPCs

Add an NPC framework, that essentially is an NPC that stands there, but whenever a player walks up to its range, a dialogue box sorta expands (tween animation) with some text.

Users can use joke items

Joke Weapons

Items that don't do much damage but might be fun for bullying mobs

• Wooden Stick
  • High knock-back; always deals 1 damage
    
• Harisen
  • Causes flinch on enemies; short duration; no damage
    

Debuff Potions

Obtainable from merchants

• Moonshine
  • Inflicts Blind:
    • Reduce FOV for 300s
• Untreated water
  • Inflicts Sick:
    • Reduce Max HP for 300s
    • Reduce Attack for 300s
• Gin
  • Inflicts Drunk:
    • Reduce Accuracy for 420s
    • DoT 1 HP every 15s

Users can control a character

User story relating to character movement.

• #10
• #13
• #14
• #15
• WASD movement

Write initial Game Documentation and Plan on README

Users can buy items

## Natural recovery
- Slowly recover HP in home

Merchant

• Sells items (stock is RNG)
  • Healing potions
  • Debuff potions
  • Weapons (see #6)
• CharacterBody2D object in dungeon
• Can be interacted with
• Displays shop menu
• Can only sell items
• Has sanity checks for currency
• Has warnings for purchase attempts that may exceed carry limit

[ASSETS] Starter assets

High priority visual assets to start the project with

Sprites

Chest

• Idle
• Hit (i.e. get hit by player)
• Death

Character

• Idle
• Walk
• Roll
• Attack
• Hit (i.e. taking damage from mobs)
• Death

Sword

• Idle
• Swing
  (No break sprites - assume no durability)

Create character Node (Godot) with Script

Create the initial Node for the character (player), should include a script, colliders, and Sprite2D

Users can click on "Play Game" (Main Menu)

• #12