bomberman | : video_game : { { incomplete } } { { 2012 } } ncurses | Game Engine library

I would like to state that I solved this issue thanks to @PallarDue & @NicoSchertler.

I had to reorganize my code and play around a bit, but I finally got it working. I will try to sum it up.

The idea is simple, I have an if statement that checks if the direction of fires it belongs to has previously collided. Lets say that index 4 in my fires array collides with a crate. Then I don't want any more fires to be created in that specific direction.

Afterwards I make a Fire object and I check if that Fire object's hitbox collides with any of the colliders hitboxes using IsFireColliding(Fire fire). This method loops through all the collidables and returns true or false depending if any collision is detected.

If IsFireColliding returns false, then I add the fire to my fires List.

If it returns true, then I add the object to my list and set the direction bool (directionContinue[x]) equal to false. Setting the bool to false hinders any more fires to be created in that direction.

Here is the code to the class that does this:

According to WM_DEADCHAR:

WM_DEADCHAR specifies a character code generated by a dead key. A dead key is a key that generates a character, such as the umlaut (double-dot), that is combined with another character to form a composite character.

So the WM_DEADCHAR message is not what you think corresponds to the WM_CHAR message.

You can also use WM_KEYDOWN/WM_KEYUP messages to handle character keys:

This might probably be coz while creating your own class you might have also accepted to create a default class as prescribed by your IDE. If that's the case try this: go to PROJECT folder -> src folder -> Default package keep only one class(in which you had written code) and delete another one.

Perhaps downgrading the java version and re-creating the project will help

You can use rect.collidelist(list) and pass in a list of rects.

I'm pretty sure that all collidelist() does is iterate through the list of rects, similar to what you're currently doing, but I'd recommend looking at the documentation if you have any further questions.

I have refactored the entire code because the code you posted throws an error and i couldn't test my code. The way we have implemented collision detection here works but is not really effective. If you want to know which side is colliding so you can implement the game logic, then colliderect is quite pointless. I suggest you ask a new question on how to build custom collision detection, since it's an entirely new topic but the following code solves the original question of how to implement collision detection using colliderect. The following example also shows how draw functions should be a separate method, which is the better way to do it. Btw, if tile == 10 you had put pygame.Rect(x * 32, y * 32, 32, 32) in your question which basically does nothing, so i put pass. If you want it to be a new type of wall, you can make a new class similar to Breakable and Wall. Final answer, hope it helped :).

You can configure how the collisions work in a particle system in this submenu, doing it dynamically can be hard:

If _objPosition as I understand it contains the location (x,y) of your person then just check that against the size of the PictureBox with an If statement. I'm not sure what the _objPosition contains, you could just use your x and y directly as well.

If you can't get the names before they've been joined by commas, you might be able to use a regex delimiter to split them. For example, if it would suffice to not split at commas preceded by only two non-whitespace characters, you could use:

When you get to Odczyt_z_Pliku, Renderer is still a NULL pointer.

As it stands, in your main() function you have a variable Renderer of type SDL_Renderer* (initialized to NULL). You then pass that value NULL into SDL_Renderer* which also takes an argument of type SDL_Renderer*.

However, in C this is just a pass by copy of the value of the pointer itself (not the value pointed to by the pointer). In other words, the argument Renderer to your function just creates a local variable in that function. So in Odczyt_z_Pliku when you do Renderer = SDL_CreateRenderer(...); that may return a new pointer but it's only assigning it to the local variable Renderer, but this has no effect on the Renderer variable in your main() function.

In C, the way to write a function that sets the value of a pointer that is a local variable in the calling function is to use a double pointer. That is, change the signature of Inicjalizacja to