bomberman | SMTP Performance and Load Test Tool | Performance Testing library

Even though your for loop reversed, it still passes in the same index for every iteration, and that index is used to compute the delay it gets. So no matter what, the item at index 0 gets 0*50 milliseconds delay, regardless whether it happens first or last. You still need your original counter in order to define their ordered index. You could solve it like this:

Inheritance is implemented using __index.

See https://www.lua.org/manual/5.4/manual.html#2.4

__index: The indexing access operation table[key]. This event happens when table is not a table or when key is not present in table. The metavalue is looked up in the metatable of table. The metavalue for this event can be either a function, a table, or any value with an __index metavalue. If it is a function, it is called with table and key as arguments, and the result of the call (adjusted to one value) is the result of the operation. Otherwise, the final result is the result of indexing this metavalue with key. This indexing is regular, not raw, and therefore can trigger another __index metavalue.

So whenever something is not implemented in B you can refer the index operation to A.

I suggest you give this a read

http://lua-users.org/wiki/InheritanceTutorial

You can boil everything down to a function like this:

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 :).