lojemiru/loj-hadron-collider

A robust, pixel-perfect collision engine for GameMaker Studio 2.3.

loj-hadron-collider's Issues

asset_has_tags is broken on YoYo's end

As such, all references to it must be replaced with equivalent functionality.

lhc_cleanup() crashes if run before lhc_activate()

This is an issue for some scenarios where instance layers are deleted before their creation events can run.

Investigate new collision system oddity with bbox_right and bbox_bottom

Not sure if it screws up the LHC or not, but I need to find out.

lhc_bind(xVelVar, yVelVar)/enhanced lhc_behavior_push

Add a binding function to feed x/y velocity variable references into the LHC for use in the builtin collision behaviors. Along with enabling more complex builtin collision behaviors in general, this should theoretically allow for an enhanced version of lhc_behavior_push that manipulates an object's x/y velocity instead of position, allowing for pushables that stop at walls.

This would also require a semi-recursive call of lhc_move(xVel, yVel) as follows:

function lhc_behavior_push_horizontal() {
	var col = lhc_colliding();
	
	if (lhc_collision_right()) {
		variable_instance_set(col, __lhc_xVelVar, bbox_right + (col.x - col.bbox_left) + 1 + __lhc_xVel);
	}
	else if (lhc_collision_left()) {
		variable_instance_set(col, __lhc_xVelVar, bbox_left - (col.bbox_right - col.x) - 1 + __lhc_xVel);
	}

        with (col) {
                lhc_move(variable_instance_get(self, __lhc_xVelVar), variable_instance_get(self, __lhc_yVelVar));
        }
}

Fix manual collision calls still occurring (and crashing) after lhc_cleanup() has been called

title

Question - Using different masks for different interfaces?

Howdy! I've been checking out the LHC and it looks awesome. I am curious, though - does it have any way to use different collision masks for different interfaces? For instance, using one mask for collisions with terrain and a different one for collisions with enemy hitboxes. As far as I can tell by reading the wiki, it seems like this wouldn't be possible if both types of collision are being handled using lhc_add(), since everything's handled within a single lhc_move() call.

Of course, it wouldn't be a big deal if it's necessary to just make a separate obj_hurtbox that sticks to the player and other things with this behaviour, but I figured I'd ask just in case I missed something.

Static collisions

Forgot about accounting for static collisions in the transition to Interfaces. Whoops.