Was just getting ready to post an update, actually. 😉
Today is the last day for nominations before the election starts tomorrow. So if folks have been waiting to throw their hat in the ring, now's your last chance!
3
There's currently just one nominee, so your odds of success are very good. 😁
I think you might want to wait a bit. You're still quite new to the site, and you have a lot of moderation powers still to look forward to by earning reputation normally.
Haha, don't worry too much about rep. It's mostly just a tool to stage-out introduction of user moderation powers, so that we don't get too much spam/chaos from drive-bys and low-investment users.
You only get the +2 when editing a post that is not your own. "Post" means question or answer. You can not edit even your own comments after a certain window and you can never edit someone else's without being a diamond moderator.
The most reputation you can earn for edit suggestions is 1000 r...
> The most reputation you can earn for edit suggestions is 1000 reputation - and you don't earn any reputation for submitting post edits after you earn the edit privilege at 2000 reputation. So, unless all someone does is edit, they usually reach 2k long before they hit that 1k rep cap for suggested edits.
Hey, can someone please help me with this animation problem in my game? I'm using an isGrounded bool, and I'm using that to decide whether or not to play the animation. The issue is, I can't figure out how to order the animations to work properly. Here is the portion of my code:
// Finds whether the character is grounded
isGrounded = Physics2D.OverlapCircle(groundCheck.position, checkRadius, whatIsGround);
// This is the jumping method
if (Input.GetKeyDown("space") && (isGrounded == true))
{
rb.velocity = new Vector2(rb.velocity.x, (jumpsystem.middleness * 4f));
animator.SetBool("jumping", true);
}
I figured out how to make it start, but I can’t figure out how to make it stop.
I was just running into the issue where if I made the exit requirements “isGrounded == false” I ran into the issue where it would cancel out everything else. And, if I made it “isGrounded == true”, it canceled out again. I kinda ended up in a loop of sorts.
Folks used to use that Yoda style to guard against accidentally writing an assignment instead of a comparison. I think with modern compilers/linters warning about that, these have fallen out of style.
user92578
9:36 PM
I actually use assignment in if statements quite a lot
The big difference is that if you accidentally leave out an = sign, if (2 = myVar) fails to compile, because you can't assign a new value to the concept of 2 (in any sensible language)
Not sure if I understand the scope reduction angle - can you walk me through that?
user92578
const auto value = getMaybeSomethingNullable()
if (value) {
value->setup();
}
value->print(); // ... Whoops! Runtime crash
// VS
if (const auto value = getMaybeSomethingNullable()) {
value->setup();
}
value->print(); // ... This won't compile, as the scope if 'value' is restricted to the if-block
user92578
Basically it's the same as wrapping the initialization & if-statement inside extra curly braces
The "difference" here is that you also declare the variable in the if, you don't only assign to it.
user92578
C++ also has initializer support inside if statements to extend this, basically you can do if (const auto value = getValue(); value->isModifyable) { value->modify(); }
user92578
Same scope reduction, but the if-statement doesn't have to check the truthyness of the assignment itself
You only get the +2 when editing a post that is not your own. "Post" means question or answer. You can not edit even your own comments after a certain window and you can never edit someone else's without being a diamond moderator.
The most reputation you can earn for edit suggestions is 1000 r...
