As a note: no longer posting here. I'm around and still doing gamedev in other places though, if you're interested in following.
Thanks and be well. :)
There’s no just giving up or tuning out. Authoritarianism doesn’t just stop because you quit looking at it. And there are so many people who deserve your help and support and solidarity who don’t have the privilege to give up.
Donald Trump — the twice impeached former president, Jan. 6 coup leader, convicted felon, adjudicated sexual abuser, and man who mismanaged the 2020 economic implosion and coronavirus disaster that killed more than 1 million people in this country — has convinced American voters to give him another term in the White House.
🔗 https://t.co/41sRvIxLmT
On Saturday, I did a civic duty and helped in Michigan's Early Voting for the 2024 US General Election.
Folks I worked with said they had done multiple shifts, and Fri/Sat were the busiest. I was swamped the entire day.
I recommend more people should experience the process!
@Playeroth If you don't need it, should be able to remove it. If the compiler/IDE complains, you have a reference to it somewhere.
It's like setting up a reference to a static class across the file. If you wanted SomeClass.SomeStaticMethod(), you would just use SomeStaticMethod() instead.
@Playeroth Ahh, doesn't really matter outside use case.
Sometimes the state of your code can be reset every frame (like in update), other times you use conditions to reset them elsewhere.
If you need it reset at the start of the method, no problem doing so.
Very minor compiler stuff.
@Playeroth Depends on your use case! If the data needs to be updated frequently, then do so. If it needs to be updated as the result of an action happening, you can do that with components/events.
I advise to just get the thing progressing, then check usage later if there are perf issues.
@Playeroth The overall idea being method or property names can be state or condition, then allow consuming code to build up use cases that make more sense in context.
e.g. If I changed your function context to IsMoving, consuming code can infer other details based on what it wants to do.
@Playeroth Either way totally works. And if you do start working with others and you need to change the scope of a method or a property down the line, you can always do so.
You're never (usually) backed into a corner if you're making the system yourself!
@Playeroth Properties are good as data accessors; you can limit the scope outside the object that can access members or derived info.
Methods can do the same thing for simple cases like this, and if it needs to be used in an event or do more work you have the option to do so.
@Playeroth Your preference, though I would advise against baking Not into the context of code and instead leverage ! when checking it.
E.g if(!IsRunningOrIdle()) ...
GHPC lead dev @JoshBusuito just put out a really informative targeting video for the current main battle tanks in the game. Check it out!
https://t.co/UMhvsWEms0