Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deal with paddles overlapping and/or colliding #34

Open
t3kt opened this issue Dec 7, 2014 · 4 comments
Open

Deal with paddles overlapping and/or colliding #34

t3kt opened this issue Dec 7, 2014 · 4 comments

Comments

@t3kt
Copy link
Contributor

t3kt commented Dec 7, 2014

Either the paddles shouldn't be able to pass through each other, or we'll need to figure out which one gets credit if they both hit a ball at the same time.

@Dewb
Copy link
Member

Dewb commented Dec 13, 2014

Is it okay if it's random? (And by random, I mean biased by the implementation of collision detection, which is probably going to give it to the paddle that was created first.)

@t3kt
Copy link
Contributor Author

t3kt commented Dec 13, 2014

That's fine.

@JimAnkrom
Copy link
Member

" give it to the paddle that was created first."

...that could create situations where a new player gets grief'd from an
existing player they chose to stand next to.

I prefer to have paddles collide, and allow paddles to move vertically
within a zone, but barring that I think we should have paddle preference in
dual collision be randomized. It can be pseudorandom - pull a number off
the clock or something (assuming C++ or oF has a clock readily available).

On Sat, Dec 13, 2014 at 2:32 AM, tekt [email protected] wrote:

That's fine.


Reply to this email directly or view it on GitHub
#34 (comment).

@Dewb
Copy link
Member

Dewb commented Dec 16, 2014

Randomizing is the easy part. Right now we don't have a way to consider all the potential collisions of an object before deciding which one to respond to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants