den4200 / game-jam-2020 Goto Github PK

Some enemies (preferably bosses) should have health bar.

Should it be similar to damage indicator and be above them, or should we make big health bar that will be full screen width at the top of screen is to be discussed.

Another thing we can add is a mana bar for the player for shooting / abillities.

Assets we can use - https://adwitr.itch.io/pixel-health-bar-asset-pack-2

bullets derive from TemporarySprite and suppose to get killed after certain lifetime but they don't

Preferably only bosses should have health bar.

We already have soundtrack manager, make it play.

Neither is it restored nor is it properly deducted (it just goes from 3 full to 2 full skiping one step of half)

Simple idea:
Randomized spawn same as enemies.
On pickup they restore ability cooldown so it's faster to use abilties.

Some can restore certain ammount of HP/mana?

Description

When sticking to 2 tiles and trying to move diagonal the movement is buggy and throwing you backwards.

Solutions

The solution I thought about was to make the player sliding, so he can slide on a wall while moving to it.

For example if you use green player ability it will not increase altho HP is increasing

We need a way for it to be global, in form of import maybe.

That way we can easily import it and add sounds and deal with slowmode/volume tinkering and additional things instead of passing references around.

Currently the class exists but is a placeholder.

Not sure how would it visually be represented, maybe "throw" some semy transparent sprite (air/dash) in the direction but with very short range.

The player can't pass certain tiles and being glitchy.

So if the ability has duration of 8s the player should not be able to change to other character for that duration.

For the UI we can just set the cards to red color to symbolise not being able to change.

Something got broken with previous commits...
If it's charged to the max it's lifetime is too short and dissapears right away...

Basic explanation on how to setup/run

Description of the game and abilities (see #19 can use text from there).
Should have image of the game.
For copyright should link to attribution.txt

Some method of SoundManager should be activated on slowdonw that would decrease the volume of all playing sounds, then after slowdown method that restores the volume should be called.

To recreate:
Put map seed to 25, play and move up until you get crash.

What happens when the player dies.
Easily to implement new level but maybe show text screen or smth.

Each level will have more enemies (and types!) than the level before.

When hovering the card we should try to implement functionality so it slows down the game instead of pausing it.

Description

We need a core game idea. We've come up with many different ideas, but haven't really discussed or formally agreed on any of them. However currently, we have an incredibly good base game.

Current Game Implementation

The player has 3 different wizards to pick from: red, green, or blue. Each colored wizard has their own special abilities.

Note: ( /\ ) means a higher value is better and ( \/ ) means a lower value is better

When hovering over a card to select a specific colored wizard, the game slows down time, making everything move in slow motion.

The player can move around the map by clicking on a tile. The wizard will then use A* pathfinding to figure out its way over to the player's selected destination.

The map is generated using cellular automata through several generations. The map consists of three things, The flooring, walls, and spikes. The spikes periodically extend up out of the ground, and if the player is on top of them, they will be damaged.

The player and some specific enemies are able to shoot laser projectiles at each other, causing damage to the one entity hit. Currently, we have two enemies: The chasing demons and stationary imps. The chasing demons will chase the player if within range, and use melee attacks. On the other hand, stationary imps will not chase the player. Instead, they will sit still and fire lasers when the player is within range.

I think that's about it for our current game implementation.

Figure Out the Core Design & End Goal

What will our core design and end goal be for this game? Will the game's idea be centered around "survive as long as you can"? Or will it be more like a strategic puzzle game, solving levels and fighting enemies along the way? This game could branch off into so many directions, as it is in a very flexible stage. We need to nail down our idea and final goal.

Some Ideas

• Have the game be "survive as long as you can" with multiple waves of enemies spawning in. There could possibly be power-up items to pick up and use, boosting the player's abilities in some way. In the end, when the player dies, the score will be uploaded to a server to be added into a leader board.
  • Extending on this idea, we can have multiplayer games where 2 or more players can work together to survive the longest. When the players both die, the score will be saved into a different leader board than singleplayer.
  • Extending on this idea even further, we can have multiplayer games where 2 or more players can battle each other, in a free-for-all.

Conclusion

We need ideas and we need to agree on one! Discuss below.

When a sprite inherits this class and uses the move_to function, the sprite does not end up exactly where the destination was set. This needs to be fixed.

While moving, if the player is hit, the player will stop for good and will not move at all.

Implement potions and abilities for each color.

I think the bullets shot by enemies should pass by other enemies.

The images we have for cards are not valid due to copyright.

Currently it's declared as class atribbutes.
Maybe it should be enums similar to enemies, but with value being tuple of tuples or smth

This could be for the better as if it was working:

Higher chances of player being pushed into wall, need to refine custom engine
Enemies do not have collision check, need to refine custom engine for them (thus we can shoot them and push them trough walls)

For sprites that don't move (the moving sprites that are idle and not chasing) the throwback works.

Description

When the player is in trouble, he can just open the cards menu and relax, think about what he should do for a while, i think this is not optimal and we should have some sort of uptime for the cards menu.

Alternatives for pausing

What we should probably do for pausing is a simple menu to pause the game, but the menu will hide or blur the game.

Similar polymorphism as enemies but completely new thing.
For the being just a simple spike trap that periodically extends spikes is good enough.

Should be modular so we can make a trap spike that extends spikes only when player is close/on i etc.

We need at least some kind of basic menu, even if it just has the play button.

Player can activate powerup but he can't know what is the current cooldown.

There should also be a sound or effect upon ability activation. (and deactivation?)

It is dropped, too much work and it tends to be very buggy.
Current implementation is also buggy, since there is no collision for enemies it can push enemies off screen and trough walls.

If it's not gonna be implemented then a simple collision check for wall hit needs to be performed after pushback that will just reset enemy change_x, change_y to 0 AND move them to nearest passable tile (if we don't move them we can spam them into wall.)

Add animation to mouse click / hover

Can be the color of the current character and the cursors will be switched according to the current player state :

• Attacking - Ranged
• Attacking - Melee
• Selecting / Collecting
• Moving? / Hovering on collidables

good assets - https://kenney.nl/assets/crosshair-pack

Set map seed to 3, you will see that it is not due to tons of enemies around you.

It is slighly noticable when you set the seed to 6 and move left.

It is completelly recreatable with seed 13 when you move left.

My bet is that this is due to pathfinding.

Either add sounds effect or don't make him hitable (currently he can get hit)