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

Changes to OSCR Combat Time Requirements #92

Open
Kraust opened this issue Nov 29, 2024 · 6 comments
Open

Changes to OSCR Combat Time Requirements #92

Kraust opened this issue Nov 29, 2024 · 6 comments
Assignees

Comments

@Kraust
Copy link
Contributor

Kraust commented Nov 29, 2024

This issue exists to track proposed solutions to combat time requirements within OSCR. These changes are not limited to Infected the Conduit: Elite but largely affect times on that map and specifically the difference in runs between Left-Right and Split run types.

Current Solution

All Maps: A character has a valid parse if their combat time is within 90% of the longest combat time.

Proposed Solutions

  • All Maps: A character has a valid parse if their combat time is within 15% of the mean combat time. Proposed by Stephen here.

  • (possibly alternate table) No combat time restriction but calculate dps over complete combat time instead of player combat time. Proposed by Krassl4 here.

  • All Maps: A character has a valid parse if their combat time is within 85% of the longest combat time. Adjustment to the current rules as originally posted by Mara here.

  • All Maps: Apply a variable percentage rate based on the map and season. Proposed by Markus here

@Kraust Kraust self-assigned this Nov 29, 2024
@Kraust
Copy link
Contributor Author

Kraust commented Nov 29, 2024

image

@Kraust
Copy link
Contributor Author

Kraust commented Nov 29, 2024

alright, so the idea standing is 85%, reloaded on to a new table

Note that if we go with the map / season based approach, we would keep the existing 90% value for legacy ladders, and new ladders going forward would have 85% (or if its changed again, that new value). Basically don't invalidate previous records.

@Kraust
Copy link
Contributor Author

Kraust commented Dec 4, 2024

Resolution of this Issue will be determined based on a poll in the Builds Discord:

https://discord.com/channels/889102180332732436/1311772333475631216/1313866996865171496

@Kraust
Copy link
Contributor Author

Kraust commented Dec 5, 2024

Conversation with Chell and Shinga made me come to the conclusion that we should also be defining where "total combat time" comes from, and that "total combat time" is not necessarily the "longest combat time". Longest combat time was originally used because it was the best method we had available. We now have total run time which should likely be used instead.

@Kraust
Copy link
Contributor Author

Kraust commented Dec 8, 2024

If we go with the new combat time duration consideration needs to be taken to make it a flag where leagues with that flag have the total combat log duration and not the relay-style one we currently have.

@Kraust
Copy link
Contributor Author

Kraust commented Dec 14, 2024

image

85% Won the Poll

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

1 participant