Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Vulpkanin Rework: Number Changes #713
Vulpkanin Rework: Number Changes #713
Changes from 3 commits
710356a
3327904
5353a6e
b8c250f
f6de9e5
473b742
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This for me personnaly is a nono.
I seen the effect of it and its horible. (on frontier)
Just please remove this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I disagree, I've also seen the effects of this and it was a rather interesting experience.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Mnemotechnician I reduced the 25% increased hunger rate to 15% due to feedback. What do you think is the ideal number for it?
I initially chose 25%, because EE does not have an increased hunger rate unlike Delta-V (see DeltaV-Station/Delta-v#1302, DeltaV-Station/Delta-v#1384). A 25% increase does not come even close to the default Delta-V hunger rate, which is
0.035f
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@FoxxoTrystan I've done some research on the hunger rate changes of vulps on Frontier. It seems like they were set to a whopping 3x hunger increase from the Frontier base hunger rate (
0.02f
).That's a LOT and puts it in context for me. A 1.25x hunger increase will likely not feel the same at all as a drastic 3x hunger increase.
With the base hunger rate of ~0.0166, the fastest time to get to starving is around 72 minutes. With the hunger rate multiplied to 25%, it's still 58 minutes, still nearly an hour of playing. With that in mind, I'm reverting the hunger rate increase to 25%.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I meant the opposite - I agree with the change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okay then. we are sticking with 25%. if the global hunger rate gets increased like in DV, that's when i'm inclined to take another look at the hunger rate increase
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
25% is still huge in my opinion, but we will see.
Honestly i do prefer the 15%