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

Change speed descriptions to reflect what actually happens #7184

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

DakkJaniels
Copy link
Contributor

No description provided.

@qndel
Copy link
Member

qndel commented Jul 9, 2024

Personally I'm not a fan of this change, old descriptions felt cool :P

@AJenbo
Copy link
Member

AJenbo commented Jul 9, 2024

At least i would not put the tick count in there, it's an implementation detail that the user should not really be aware of.

@DakkJaniels
Copy link
Contributor Author

Personally I'm not a fan of this change, old descriptions felt cool :P

I guess, but people are confused by them, thinking the game changes (e.g., monster AI changes to become more aggressive) beyond just making it faster.

At least i would not put the tick count in there, it's an implementation detail that the user should not really be aware of.

I can remove that.

@kphoenix137
Copy link
Collaborator

kphoenix137 commented Jul 26, 2024

I think the descriptions are a bit confusing. I would revise to something like:
Standard game speed
1.5x game speed
2x game speed
2.5x game speed

Stuff like Game runs 150% faster than normal makes you do mental gymnastics to figure out how fast that it, despite being technically correct. I could see many users mistakenly thinking that means "The game runs at 150% speed".

Additionally, the old descriptions could be appended to my suggestion, giving a very clear demonstration of what is happening, as well as being immersive.

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

Successfully merging this pull request may close these issues.

4 participants