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

only-tag-attacker issue where it just untags if theyre hit back #89

Open
omega015 opened this issue Aug 28, 2016 · 8 comments
Open

only-tag-attacker issue where it just untags if theyre hit back #89

omega015 opened this issue Aug 28, 2016 · 8 comments

Comments

@omega015
Copy link

When I have "only-tag-attacker: true" it tags the person who hits (which is expected) however if the other player hits back it untags the first player and only tags the new attacker. I think the original attacker should continue their tag countdown (for as long as they keep hitting) otherwise during pvp you just have tags going back and forth between players with every hit.

@Techcable
Copy link
Contributor

What's your full config and version?

@omega015
Copy link
Author

See attached for the config (I have only changed only-tag-attacker)
config.zip

As for the versions I have tried release 1.2.3 and the latest build #143

@omega015
Copy link
Author

omega015 commented Sep 6, 2016

Hopefully this wont be too hard to fix or that its just a config issue.

@Techcable
Copy link
Contributor

Could you please gist it?
I don't like to download and extract untrusted zip files for risk of viruses.

@omega015
Copy link
Author

omega015 commented Sep 7, 2016

My bad. here it is:

https://gist.github.com/omega015/dfffe8843187052b76e0cebf61f2a313

@Techcable
Copy link
Contributor

What happens with only-tag-attacker set to false?

@omega015
Copy link
Author

omega015 commented Sep 21, 2016

With only-tag-attacker set to false, this keeps both players with combat tag and both countdowns reset no matter who hits. It is just when setting to true that it isn't working as expected (or desired).

Thank you.

@omega015
Copy link
Author

omega015 commented Nov 6, 2016

Hi Techcable, did you manage to look into this or reproduce the problem?

Thanks.

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

No branches or pull requests

2 participants