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

FF parameter adjustment #3060

Closed
Bob-Murphy opened this issue Nov 22, 2023 · 5 comments · Fixed by #3061
Closed

FF parameter adjustment #3060

Bob-Murphy opened this issue Nov 22, 2023 · 5 comments · Fixed by #3061
Assignees
Labels
Change A change to existing functionality
Milestone

Comments

@Bob-Murphy
Copy link

Could you please switch up the FF functionality a bit?
Currently tkPunish enables/disables the tracking as well as the punishment which I believe could be improved.

Please apply the following changes in the params:
New - tkTracking - enables/disables the tracking and the pop-ups - enabled by default
Existant - tkPunish - enables/disables only the punishment being applied - disabled by default

@Bob-Murphy Bob-Murphy added the Change A change to existing functionality label Nov 22, 2023
@Bob-Murphy Bob-Murphy added this to the 3.4.1 milestone Nov 22, 2023
@Bob-Murphy Bob-Murphy mentioned this issue Nov 22, 2023
3 tasks
@jaj22
Copy link

jaj22 commented Nov 22, 2023

Why? What's the use case?

@Bob-Murphy
Copy link
Author

Exemplary usecase:
Small community, open server but not much changing in players.
They sometimes fuck around, shoot each other at HQ, hence they don't want the punishment to trigger and send people to the turtles.
Nevertheless, they still want to be able to track what happened in case somebody is being a dick on purpose, hence the tracking and the pop-ups can be useful.

@Bob-Murphy
Copy link
Author

As an alternative, have it always log into the RPT and have the param enable/disable hints and punishment.
Hence the info is still tracked and no additional param.

@jaj22
Copy link

jaj22 commented Nov 22, 2023

Nah, punishment is quite expensive to run at the moment (every time a rebel unit is hit by anything, it sends a heavy remoteExec to the server) so there needs to be a way to disable it entirely.

Another option would be to expand the parameter to three options (disabled, notify only, punishment), but that would require #3042 to be merged first.

@Bob-Murphy
Copy link
Author

I'd be perfectly happy with that solution.

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

Successfully merging a pull request may close this issue.

2 participants