jigoku / boxclip Goto Github PK

Don't move enemies unless they are on screen.

This might help with speed in the long term. Also makes some enemies predictable, which can be useful for creating bounce/jump courses throughout a level, making things less chaotic for speed running etc.

For now these are some ideas to implement;

• gravity
• mapmusic
• background colour
• groundLevel texture (lava/water etc)

Right now velocity (x and y) gets 'capped' so a spring cannot apply an extra boost, find a way to make this work for left/right and downwards facing springs.

Should have quick access to all implemented features so far.

This would be sitting in one place.

Ideas;

• Apply gravity so it's fixed to the structure below it, rather than manually fiddling to the pixel level.
• When player is within a certain range, it shoots a projectile depending left or right side.
• Cannot be killed
• Player can stand on top of it however.

Secondary platforms that do not collide with left/right/bottom sides.

This could be used to create more interesting maps.

Sometimes (rarely) collisions fail to resolve... usually if gravity is set to a stupid amount, or the system freezes momentarily.

Highly noticable when loading a VERY laggy and messy map. many enemy entitys will just decide to plop through the platform and die.

add layers;

1. back layer (non collision background images; eg trees or other detail)
2. middle layer (collision objects, 'structures' here)
3. front layer (non collision foreground images)

When dying, make the player bounce and fall out of camera (no collision), before respawning.

Like the walker, it has a fixed movement area with no left/right collisions, but jumps back and forth instead.

low priority

groundLevel should be removed (changed) to be a deathzone.

world platforms would reside above it. deathzone should be able to be set as water (drown), lava (die) etc. This way pickups can fall into the deathzone and be destroyed, aswell as the player losing a life.

Should be keyboard/mouse controlled, by either a popup menu (keybind, eg M for menu?) or small corridor style menu at edge of screen. Should be scrollable to select entity type, showing a preview/name.

Why? Because there are now 9 entity types that can be added to the world, and 1-9 binds have been used up.

Appearance would be a ball with a chain attached to a spiked ball rotating around it.

• No gravity
• Can be given a movex or movey parameter

when object is positive velocity and structure is negative (vice versa), this causes overlapping and object passes through.

Can be added to world like the platform with click/drag, but appears as a shaded area (transparent) in the editor. Not visible in world but kills objects that collide with it.

As of now, *.love reaches above 12MB... is this ideal? Might be better to try and separate the assets, so that only script files are stored within the executable.

This would be easier to organize LICENSE files (one per folder) similar to how some other FOSS games do it.

eg;

graphics/<AUTHOR>/file1.png
graphics/<AUTHOR>/LICENSE

Like the icicle/spike enemies, but falls when you are below it, and collides with the ground below.
If it collides with player, it kills.

This would check for collision with objects, and if it collides, it simply switches direction.

When a crate is destroyed, add velocity depending on the side the crate was hit, and bounce momentarily before stopping.

add a grid overlay, and snapping for placed entities

Only stop the player travelling through when falling and colliding with top side

This could be used for loading another map, ie; challenge room, hidden room etc.

Zippy | Too many projects relating to platformers already use Zippy it turns out...
Boxclip | Generic, boring, descriptive engine name

Find something else!

This should reset the world, platform origins, enemy origins, pickups, etc. To default state.

These would not be breakable, but fall when pushed off a ledge.

• keys as pickup types
• chests similar to crates
• can only be opened if key has been collected
• red key, opens red chest, etc.
• one colour type per level.

add support for sprites

moving platforms are bugged when trying to reposition, also needs to have other entity types added (particularly, crates, and other non-gravity applied objects)

It feels sluggish when moving about, and if you move the camera view, the crosshair ends up being drawn off screen until mouse event has moved.

Add a switch to this; eg enemies:spike(x,y,dir)

0 facing up
1 facing down
2 facing left
3 facing right

would allow spikes on platform ceilings or platform sides.

when selecting ents in an area that overlaps (of the same kind).

eg; platform over platform over platform. the oldest/lowest layer platform is selected for actions like deleting. most recently placed ent should be selected instead.

add some kind of reordering to platforms.

Like the walker, except there is no gravity applied. Can be used for weak flying enemies.
These shouldn't clip platforms either.

Arches, pillars, meshes, grates, fences, other generic platformer structures, etc.

They can be coloured or greyscal (to be themed with the world pallette/theme). These are objects that never collide with anything, but just add some detail to the world.

Example:

This gives a small depth illusion and appears to be supporting the platform above.

Or used as a tunnel support/entrance

Looks okay in "game" mode. But changing the scale gets broken in editor.
Also effects minimap view in the editor mode.

On a solid structure, holding right or left, causes tiny amount of pixel fighting, adjust this to make the object stay still.

mode select.
initially, "load map", "edit map", and "quit"

add a map editor mode

Should find out how to use 'love.filesystem' instead of 'io.open'

Objects should fall (if not colliding) with gravity, BEFORE first frame is rendered.

If no checkpoint has been activated, and we die... we can simply reload the map.

If a checkpoint is activated, we want to store all states of entities...
*crate
*enemies
*pickups

etc

So that when we die after activating a checkpoint, we make sure collected/killed/destroyed entities collected after dying are restored to the last checkpoint state.

Might be simpler to fix this, by getting rid of all tables named "pickups" "crates" "enemies" etc, and merge them into entities={ ... }, activating a checkpoint would create a new_entities={ ... } table, when dying load up the new table?