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

Friendly fire enabled in infection #218

Open
1 task
Castiella opened this issue May 25, 2019 · 3 comments
Open
1 task

Friendly fire enabled in infection #218

Castiella opened this issue May 25, 2019 · 3 comments
Assignees

Comments

@Castiella
Copy link

Castiella commented May 25, 2019

Note: for support questions, please use SpigotMC.org. This repository's issues are reserved for feature requests and bug reports.

  • **I'm submitting a ... **

    • [X ] bug report
    • feature request
  • Do you want to request a feature or report a bug?
    report a bug

  • What is the current behaviour?
    when playing an infection game, red [infected] players can kill eachother. So can survivors. However i have noticed that for some reason they are not in a specific team on the scoreboard and instead are on top of the team.

im not sure if this has anything to do with it. (Although, the teams are definitely registering to some extent, as when a player is killed they become infected.

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem, screenshots ok

  • What is the expected behavior?

for players to not kill eachother if they are on the same team.

  • What is the motivation / use case for changing the behavior?

it is game breaking for the infection mech.

  • Please tell us about your environment:
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
@Narimm
Copy link
Member

Narimm commented Oct 31, 2019

We are doing some work on teams in the 1.14 version try that

@Narimm Narimm self-assigned this Nov 1, 2019
@Castiella
Copy link
Author

Has this been resolved as this is still an issue on the recent dev builds for 1.15

@Castiella
Copy link
Author

Still an issue on 1.16

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