plexsoup / gwj53 Goto Github PK

The scene StreetBattle01.tscn doesn't end after the player has killed all the mechs.

Verify fidelity and performance 1024x1024 environment art test asset rendered in engine.

after player gets hit, they should have a moment to recover, where they don't keep taking damage. (Normally called iframes).

Translate weapon art from cards into parts that appear on/attached to the mech.

Beam, AoE, Projectile?

Laser, missiles, auto-cannon?

NavigationServer2D, NavPolygonInstance with cutouts for obstacles so entities can pathfind around them

add shake_and_flash property in Global.
Add checks to all particles and knock back effects and camera shake.

(good for epilepsy and slow computers)

After defeating all enemies, you can still die to any remaining projectiles on screen, sending you to the junkyard.

1. Play naturally.
2. Eliminate all but 1 enemy mechs
3. Reduce player HP to 100
4. Eliminate last mech while in the path of one of its projectiles
5. Take damage from last projectile

Expected result
Player victory

Actual result
Player loses

Player impact
It can be frustrating to lose due to unfortunate positioning. Especially so when the player is locked in place after defeating the final mech.

• Enemies can be difficult to hit with the laser or missile.
• Missiles will occasionally appear to hit enemies, but deal no damage.
• Friendly lasers have the weakest hit registration of all current weapon.
• Shotgun does not appear to have these issues.

If a player loses a match, they go to the junkyard before the mechBuilder.
If they win a match, they should go to a dialog screen.

Set up the Dialogic screen so designers can implement the dialog tree.

It's easy for players to mess up their keybindings.
Make a restore default button.

Tracked by https://docs.google.com/presentation/d/1Jb92QlMrf8zeSP-lPKnFi0Qnvu1gNCSONkcWnr_ncO0/edit#slide=id.p

The gameplay transitions between two stages, starting with the mech builder, and moving to the mech battler.

The player is induced to build a mech in the mech builder stage. They do this by spending scrap on cards which provide the player parts. The player attaches these parts to their mech and the do battle with it.

The battle phase is still in the design phase and is expected to be roughly 60-70% of the gameplay.

Verify fidelity and performance for 256x256 and 512x512 module art test assets rendered in engine.

What's the reward for completing a battle?
How, Where does that appear?

Must pass new parts to mech builder scene / parts inventory

How do we git hitboxes to line up with visuals?

Should each part have it's own hitbox?

levels are quite large. Player can find themselves without obvious enemies.

Need arrow pointing to remaining enemies or minimap.

Fix EnergyShield.tscn, which is linked to Head.tres.

It's butt ugly now.

• When the player refreshes their card pool, do they keep current cards, or are current cards discarded?
  • If discarded, what happens to discarded cards?
• Where does a purchased card go?
  • Is there a pool of purchased, but unequipped parts?
  • Is the player forced to equip a card when it's purchased?

Bosses will occupy mechs that the player discarded, or built previously, or something.

The AI needs to be able to operate the same mechs that the player might have used.

In addition to shotgun, missile, and laser, create 2 new weapon types.

In addition to Ice Ice Baby, create 1 new ability type.

make a shotgun that fires 3 projectiles instead of using an area2D for hit detection.

In no order of priority

• advanced player movement feature (dash)
• "bullet hell" projectiles, remove hit scan weapons
• increase player move speed +++
• increase map size (design is in progress)
• establishing shot, prefight (zoom out and countdown)
• cleaning up player and enemy hitboxes
• removing reroll system, establishing "market"
• retooling game launch scene order
  • Game Start -> Junkyard -> Narrative intro -> Battle scene 1 -> mech builder
• default player mech improvement (better/more weapons)

basic missile projectiles only work with the line_of_sight flag enabled.

When line_of_sight is false, they should travel to the known cursor location, then explode, without harming anything on the way toward the destination.

lasers are super wide now, but they look weirdly stubby as a result. Make them much longer and reduce damage to compensate for game balance impact.

most games turn you into a ghost during iFrames.

• parts collection

• mech building

• shootemup

• rewards

• upgrades / scavenging --> feeds back into parts

• possible interactions with customers, but probably not

Generic spawners spawn waves of enemies. Once the waves are gone, the round should end.

Win condition monitor could count enemies killed, or it could be a time limit.
Something needs to end the scene, present a reward and return to the mech hangar for rebuilding.

Seems like mechs are waiting for their decisions timers, but it looks weird having them just stand there doing nothing.

Right now, weapon aim seeks Global.player_cursor.
It should seek mech/InputController/Cursor

Add a targeting cursor to enemy mechs (eg: ChaseMech02.tscn)

For accessibility, some people will need click-to-move instead of wasd.
(presumably along with auto-targeting)

Basic player controller, 8 way movement, shooting, lookahead camera.

Look at the pathfinding code,

look at the nav polygon,

look at their collision shapes.

Last resort, give them random back-up behaviour if they're immobile for too long.
Maybe give them a raycast and have them turn away from terrain.

James pointed out that guns all fire more or less simultaneously.

It might be more satisfying if they're staggered.

Add offsets to the initial load time, or give them random deviation so they drift over time.

move the code for movement into entity instead of legs.

Legs can provide get_velocity() instead of executing move_and_slide().
entity can add up all the velocities and apply some diminishing returns multiplier.

Add a button to settings to disable particle effects.

Many particle effects are currently hidden inside AnimationPlayer animations.
Track them down and set/unset them in code.

Player uses [parts] to build [mech] of their dreams.

• requires parts from another scene
• can be slots, hardpoints, or physics based.
• delivers avatar to shooting scene.

2 levels for local battles with mooks and thugs
1 boss battle

--- MVP cutoff after this line is optional ---

additional levels as required / time permitting

Generate game SFX at https://sfxr.me/ for:

To-do:

• Part buy
• hover and click sound for menu buttons
• Laser shooting
• Alt. laser shooting
• Missile shooting
• Mech walking
• shotgun shooting
• mech taking damage
• missile shooting
• missile detonating
• auto-cannon shooting
• auto-cannon impacts
• a "schwing!" sound from a 1v1 fighting game (see Kyveri ref)
• Steel door open and close
• Picking up a part in a junkyard (crunchy)
• putting a part on a mech (snap, pop, or click)
• removing a part ("")
• Special "start" sfx when entering the game for the first time (The effect should have reverb and fade for the transition to gameplay)
• Mech destroyed sound

Crowd noises (new ask)
crowd noises would really spruce up the battle scene. could we get the following noises?

• Crowd talking before a show level of crowd (this can loop during the match)
• Crowd really excited like someone scored in a sport (like when an enemy mech is destroyed)
• Crowd groans like a boxer took a bad hit (When you take too much damage or die)

pathfinder towards player, avoid peers, shoot at player, get hit, die

After winning the third match, we should have a win-game screen.
Setup a stub for dialogic.

Disable mech input while zoomed out, only spawn the mech in (or even just unhide) after zoom in.

To meet accessibility guidelines, we need to implement auto-targeting for some players.

Therefore, we should add an autotargetting toggle somewhere in the settings menu.

enabled: an AI cursor/mouse will automatically seek nearest enemy.

Right now, AI goes toward player. (PathfindToPlayer.tscn)

The design doc calls for 1v1v1 Battle-Royale style last man standing arena battles.

That means AI mechs need to be able to target each other.

Cards are broken up into following categories:

• Weapon
• Defense
• Movement
• Ability

Whenever the player is delt a new hand of cards, they are guaranteed at least one card of each category.

Cards also posses other features:

• Name
  • e.x. "Shotgun"
• Rarity
  • Common
  • Uncommon
  • Rare
  • Legendary
• Power Draw
  • How much power it takes to equip
• Cost
  • How much scrap it costs to buy the part
• Combat/Stat changing values