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

Marking attacked creature has poor hit ratio #1030

Open
2 of 5 tasks
nekiro opened this issue Jan 9, 2025 · 1 comment
Open
2 of 5 tasks

Marking attacked creature has poor hit ratio #1030

nekiro opened this issue Jan 9, 2025 · 1 comment
Labels
Priority: High Represent a high impact in key areas of the base/user experience Status: Pending Test This PR or Issue requires more testing Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@nekiro
Copy link
Collaborator

nekiro commented Jan 9, 2025

Priority

High

Area

  • Data
  • Source
  • Docker
  • Other

What happened?

Right now right click into game_interface gets the top creature of a tile, which makes it hard to click the creature while its walking sometimes.

This can be fixed by using pixel based aiming (v8 has implementation of it)

What OS are you seeing the problem on?

Linux, Windows, MacOS

Code of Conduct

  • I agree to follow this project's Code of Conduct
@nekiro nekiro added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Jan 9, 2025
@github-actions github-actions bot added Priority: High Represent a high impact in key areas of the base/user experience Status: Pending Test This PR or Issue requires more testing labels Jan 9, 2025
@nekiro nekiro changed the title Marking attackCreature is performing poor Marking attacked creature has poor hit ratio Jan 9, 2025
@Zbizu
Copy link
Contributor

Zbizu commented Jan 19, 2025

for reference: in QT client, regardless of creature size, the red square is the area which reacts to the cursor when marking the creature (origin/destination tile do not matter in here)

Image

in current implementation of otclient, it's inconsistent

north-west path: both origin and destination tiles react, but not the side tiles

Image

south-east path: only destination tile works

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: High Represent a high impact in key areas of the base/user experience Status: Pending Test This PR or Issue requires more testing Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

No branches or pull requests

2 participants