Pairwise Collision Rules ⚠ Click here to regain focus ⚠
?
?

Keyboard Navigation

Global Keys

W, A, P / S, D, N Jump to previous / next marker
t / T Toggle theatre / SUPERtheatre mode
z Toggle filter mode V Revert filter to original state

Menu toggling

q Quotes r References f Filter c Credits

Movement

a
w
s
d
h j k l


Quotes and References Menus

Enter Jump to timecode

Quotes, References and Credits Menus

o Open URL (in new tab)

Filter Menu

x, Space Toggle category and focus next
X, ShiftSpace Toggle category and focus previous
v Invert topics / media as per focus

Credits Menu

Enter Open URL (in new tab)
1:35Recap of where we left off with collision responses
1:35Recap of where we left off with collision responses
1:35Recap of where we left off with collision responses
4:44Changing things so that stopping on collision is part of collision handling
4:44Changing things so that stopping on collision is part of collision handling
4:44Changing things so that stopping on collision is part of collision handling
6:25Overview of ignoring certain collisions
6:25Overview of ignoring certain collisions
6:25Overview of ignoring certain collisions
13:40Restructuring collision code for ignoring certain collisions with rules
13:40Restructuring collision code for ignoring certain collisions with rules
13:40Restructuring collision code for ignoring certain collisions with rules
23:33pairwise_collision_rule and collision rule hash table for ShouldCollide
23:33pairwise_collision_rule and collision rule hash table for ShouldCollide
23:33pairwise_collision_rule and collision rule hash table for ShouldCollide
31:27Tricky problem - How to remove collision rules?
31:27Tricky problem - How to remove collision rules?
31:27Tricky problem - How to remove collision rules?
34:11AddCollisionRule function
34:11AddCollisionRule function
34:11AddCollisionRule function
39:42Adding first rule - sword shouldn't collide with entity that throws us
39:42Adding first rule - sword shouldn't collide with entity that throws us
39:42Adding first rule - sword shouldn't collide with entity that throws us
41:55Adding collision rule when StopsOnCollision is false
41:55Adding collision rule when StopsOnCollision is false
41:55Adding collision rule when StopsOnCollision is false
43:37Problem - Don't want to keep on adding new collision rules
43:37Problem - Don't want to keep on adding new collision rules
43:37Problem - Don't want to keep on adding new collision rules
47:16Clearing collision rules for an entity
47:16Clearing collision rules for an entity
47:16Clearing collision rules for an entity
58:15Debugging collision rule code
58:15Debugging collision rule code
58:15Debugging collision rule code
1:04:05Q&A
1:04:05Q&A
1:04:05Q&A
1:05:03What stops us from programming a game that directly boots into BIOS (hooks up to hardware as low as possible basically)?
1:05:03What stops us from programming a game that directly boots into BIOS (hooks up to hardware as low as possible basically)?
1:05:03What stops us from programming a game that directly boots into BIOS (hooks up to hardware as low as possible basically)?
1:07:11Do you ever use function pointers?
1:07:11Do you ever use function pointers?
1:07:11Do you ever use function pointers?
1:09:07Should the thrown entity have the player's direction/speed added to its thrown speed/direction so you cannot catch your own throws?
1:09:07Should the thrown entity have the player's direction/speed added to its thrown speed/direction so you cannot catch your own throws?
1:09:07Should the thrown entity have the player's direction/speed added to its thrown speed/direction so you cannot catch your own throws?
01:10:34Could you explain again why you should order the entities before processing the properties?
01:10:34Could you explain again why you should order the entities before processing the properties?
01:10:34Could you explain again why you should order the entities before processing the properties?
1:12:30Isn't there a potential bug in MoveEntity if an entity happens to spend the whole distance limit, which gets set to (0,0), and then gets considered unlimited in the next frame?
1:12:30Isn't there a potential bug in MoveEntity if an entity happens to spend the whole distance limit, which gets set to (0,0), and then gets considered unlimited in the next frame?
1:12:30Isn't there a potential bug in MoveEntity if an entity happens to spend the whole distance limit, which gets set to (0,0), and then gets considered unlimited in the next frame?
1:14:07Can the pointers in the hash function become a memory problem?
1:14:07Can the pointers in the hash function become a memory problem?
1:14:07Can the pointers in the hash function become a memory problem?
1:16:41I have two gameplay requests - A non-euclidean room and a monster that spans multiple rooms vertically. Are those things possible?
1:16:41I have two gameplay requests - A non-euclidean room and a monster that spans multiple rooms vertically. Are those things possible?
1:16:41I have two gameplay requests - A non-euclidean room and a monster that spans multiple rooms vertically. Are those things possible?
1:19:11Are renderers reusable?
1:19:11Are renderers reusable?
1:19:11Are renderers reusable?