-
Notifications
You must be signed in to change notification settings - Fork 90
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
Discussion for reducing spawnkilling #1283
Comments
Hello. This solution is not suitable IMHO. As this prevents any spawn killing. We just want to prevent excessive spawn killing. |
This is a pretty complex problem to solve, and needs a lot of thought/testing put into it. |
Alternatively simply reward less points if an enemy is killed on their own spawn. |
Why not just make the player invincibility last until their first input/coordinate change |
Maybe something like this might work: |
Smth like this suggestion? Discord |
@LoneWolfHT I think either this needs to be closed, or that you need to "hijack" it like you did with the rankings storage issue. |
Well this poll suggested that players are okay with the current spawnkill situation https://discord.com/channels/447819017391046687/447819018028449793/1253398670372769843 |
As the spawnkill is sometime a very attractive sport for some players and not easy to report and therefore not deterrent, I would suggest that, for example, for all distant shoots (riffle, magnum, bomb, grenade...etc) on a player located in the 9 or the 25 blocks around the flag, it will automatically behave like dammage cobblestone : hurt the shooter rather than the player.
The text was updated successfully, but these errors were encountered: