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

135: Fix Knife Hits #153

Open
theonlypwner opened this issue Aug 9, 2015 · 3 comments
Open

135: Fix Knife Hits #153

theonlypwner opened this issue Aug 9, 2015 · 3 comments

Comments

@theonlypwner
Copy link
Member

Fix Knife Hits by darinm223
Issue 135 posted to Google Code on 2013 Jun 30 at 23:19:56

Current status: Acknowledged
Current labels: Type-Defect, Priority-High, Effect-Gameplay, Usability

darinm223 on 2013 Jun 30 at 23:19:56:

What steps will reproduce the problem?

  1. Get the knife/sword
  2. Try to knife someone
  3. Watch in horror as the knife passes through the enemy, doing no damage

What is the expected output? What do you see instead?
At close range, using a knife/sword will do no damage

What version are you using? On what operating system?
2.5.8/Windows Vista

Please provide any additional information below.

theonlypwner on 2013 Jul 6 at 19:47:39:

It's called "lag" and probably only happens online.

However, I'm not sure how I can improve the knife hits. It already does multiple hit checks.

Summary: Fix Knife Hits (was: Knife does no damage at close range)
Labels: -Priority-Unset Priority-High Effect-Gameplay Usability
Status: Acknowledged

@theonlypwner
Copy link
Member Author

The "short shotline" hit detection could be replaced with new intersection methods.

Currently, knife hits are detected by intersecting multiple shot lines with 2 cylinders (torso, legs) and a sphere (head). We could intersect a plane with a cylinder/sphere and check if the intersection is a valid knife hit (check the angle and distance).

@theonlypwner theonlypwner modified the milestones: 2.6.4/2.7.1, 2.6.3 (2.7 Beta 3) Jan 11, 2016
@theonlypwner
Copy link
Member Author

This issue is postponed to 2.6.4; otherwise, there will not be enough time to release 2.6.3 by tomorrow.

@theonlypwner
Copy link
Member Author

The current knife hit works, so this issue is being demoted in priority and no longer has a milestone target.

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

1 participant