flamendless

This should be included in the documentation as most of the time devs need to know the current frame position

The `other` is just a table. You can put variables/properties there before (or even after) adding to the bump world. isCoin and such are just examples, you put other variables...

```lua local PlayerTable = { name="player", --you can add more properties isPlayer = true, isCoin = false, } world:add(PlayerTable, 0, 0, 64, 256) -- x,y, width, height ```

Hi, you can easily have such behavior by using a flag. If there's a collision and the flag is false, that means thats an `on_enter` collision, then set the flag...

You would add that to the table you pass into bump as body yes. doing `check` or `move` returns the tables that have collision so yes you can modify that

@Shadowblitz16 what? More details please?

You can easily create your own method for that, i dont think this is needed in classic unless im mistaken.

Yeah I vote as well for vi/vim keybindings support

@ddovod that would do. Thanks! _Sent from my HUAWEI GR5 2017 using [FastHub](https://play.google.com/store/apps/details?id=com.fastaccess.github)_

@ddovod awesome! I will get on this asap. For the compile_commands.json, we can use the tool "bear" to generate one for us with `bear make` _Sent from my HUAWEI GR5...