Skip to content
This repository has been archived by the owner on Oct 2, 2021. It is now read-only.

Split collision detection into snake collision and wall collision #284

Open
clemens-tolboom opened this issue Jun 4, 2016 · 2 comments
Open
Assignees

Comments

@clemens-tolboom
Copy link
Collaborator

Depends on #275

As found in #275 we should split the detection into two parts. That way we could use the scheduler for two separate task which can be toggles on/off.

This way we or our users can create snakes colliding into walls or change collision into snake behavior without missing the wall.

@ermiyaeskandary
Copy link
Owner

ermiyaeskandary commented Jun 5, 2016

create snakes colliding into walls

Magnificent with the movetoxy ! We could quickly get the bot to a long length and then test bots head to head or .... !
The skies the limit...
But it may be considered by cheating as some - I classify it as using resources at hand for educational purposes ;)

@ChadSki
Copy link
Collaborator

ChadSki commented Jun 6, 2016

Split collision detection into snake collision and wall collision

Why?

That way we could use the scheduler for two separate task which can be toggles on/off.

Why would you ever want to collide into other snakes or the wall?

This sounds like over-engineering. Your scheduler is interesting but be wary of golden hammer syndrome (if all you have is a hammer everything looks like a nail).

@ChadSki ChadSki added this to the Task Execution milestone Jun 6, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants