Hello everyone, I’m trying to make tile based game… so far I made level that stores tiles into Tile[] variable. I have getTile method to get the tile from level. Now, I would like to implement collision for player and other Entitites.
The thing is, How would I check collision for tile left from entity and also right from entity ? Also, when I detect collision, I set the boolean collision to true. What to do then, how to stop player, and disable him from stucking in wall ?
OK I managed to do the checking on right side, now only how to disable player from stucking in wall ?
If you paste some code I can help 
[ code ] [ /code ]
Here you go… the move method :
public void move(double xa, double ya) {
if (xa != 0 && ya != 0) {
move(xa, 0);
move(0, ya);
return;
}
boolean collision = false;
if (this.intersects(level.getTile(x / Tile.WIDTH, (y + 16) / Tile.HEIGHT)) || this.intersects(level.getTile((x / Tile.WIDTH) + 1, (y + 16) / Tile.HEIGHT))) {
collision = true;
}
if (!collision) {
x += xa;
y += ya;
}
}
the intersects method :
public boolean intersects(Tile t) {
if (t != null && t.solid()) {
if (this.x < t.x + Tile.WIDTH || this.y < t.y + Tile.HEIGHT || this.x + Tile.WIDTH > t.x || this.y > t.y) return true;
return false;
} else
return false;
}
Once there is a collision, you need to move what ever collided away from what it hit + some small amount so you can move away again.
When I do that, I get stuttering, and also sometimes, when I try to go away from wall, player moonwalks into wall.
Hope it helps, first diagram of mine xD might be 2 noob for you lol.
IDK, im making a pong game at the moment, physics are just mindboggling >…<
Actually I’m trying to test it with only one collision variable, and intersects thing…
But I can’t make it working… 
Firstly I think it’s really helpful to have a basic grasp of vector based collision detection, at least to the point that you know how it can make things easier and also what it is able to achieve. Secondly I think it’s helpful to be aware of quantisation when checking for floating point equality.
The diagram below shows a moving red box being checked for collision with a green box. On the left you can see the full extent of the relative velocity vector - and FYI if you wanted to take it further you could have a rotating square, the maths just “works”. On the right is what vector based collision detection can achieve, the point in time of impact.
Now the question you might want to ask now is, “how do you find the point of collision”? I’m on my way out now, but when I get back I will find a link to one of my previous posts on this forum or another about using vector maths to solve collisions for geometric points, and I’ll upload some of my old collision examples to github
Now you can see what vector collision detection looks like (at least what it takes in and what it puts out) you might notice something specific about the image on the left that might not have stuck out before. Suppose the boxes passed through each other, if you only checked for collision on specific time slices you are going to miss many collisions when velocities exceed the span of the boxes.
Edit: maybe tomorrow actually, so far I’ve collected links of previous topics, but it’s quite a mouthful right now …
I hope your post will help me !
Hi.
I wrote up an article that might give you a good deal of insight into how point-collisions work.
Be aware that my method uses simple points. If you’re going to be dealing with a lot of things impacting the player movement-speed, you might have an easier time using vectors (like keldon85 suggested).
Doing player-collisions with the intersects-function leaves you with no indication of where on the rectangle the collision happened. For that, you need reference points or vectors.
I use the intersects-function for projectile-collisions and such, and it’s great for that, because I don’t need much information. To make blood-spatter I just need to know roughly where the projectile enters and exits the monster to place a particle-emitter. But if you need to correct something on account of a collision, you have to use something that’ll give you pixel-perfect information.
Well, I’m still learning, what I’m trying to do is simply block character by wall…
Is anyone going to help me here ?
Every time the entity moves, check if he is colliding, if he is, revert his position back to the previous one. Or set his individual x and y to that of the colliding walls boundaries depending on which side he is colliding on.
Or, before you move your object, check if there is a collision at the point he is going to move to before moving him at all.
Seems like your movement and collision checking code is pretty much good to go - what’s the problem?
Is it ok if I send you my source code, to see it yourself, and tell me what should I change ?
Got some code from source code of LD game genesis by Yan Chernikov ( TheChernoProject on YouTube ) that works, but needs some modification for my game.
Just to tell everyone I got it working !
Here’s the code :
move method :
public void move(int xa, int ya) {
if (xa != 0 && ya != 0) {
move(xa, 0);
move(0, ya);
return;
}
if (!collision(xa, ya)) {
x += xa;
y += ya;
}
}
collision method :
private boolean collision(int xa, int ya) {
boolean solid = false;
for (int i = 0; i < 4; i++) {
int xt = ((x + 16 + xa * 16)) / 32;
int yt = ((y + 32 + ya * 8)) / 32;
if (level.getTile(xt, yt).solid()) solid = true;
}
return solid;
}
The multiplication of xa and ya is used to make player collide further or closer on wall.
Glad you got it sorted. I’ve been extra busy, but let me know if you still would like to see some of the vector based collision resources as I will still be collating them for future reference anyway.
Of course !
I like learning as much as I can !