You could try to create a new script at runtime, set the source to the existing script source, then try to get the static variable on the new script object. Would be incurring a compilation cost though.

I think it looks great, a lot of 3D games do this too. I would actually advise against trying to make this "visible" by adding more tween time and frames, this is not the kind of detail that needs to be noticed, just felt.

Feel free to reach out for any future work I can help with, I'm currently open for contract work and have experience with the Godot source code and systems.

Yeah 100%. I strongly prefer Godot and its approach. Give me the tools to shoot myself in the foot, I don't want a framework/starter sketch.

Yes but it arguably shouldn't. The whole thing is a bit like praising or blaming the pencil for how a sketch turned out.

It actually kinda frustrates me when inexperienced people praise UE's graphics, and then you see a bunch of the indie games made with it have the same smudgy feeling cause everyone leaves the setting on default.

Yeah fully agree. Unless you're going for hyper realism, or the extreme opposite of like very specialized custom rendering techniques, you're going to be fine with most any engine.

This is without C# support, correct?

Visiting Japan after years and years of dreaming about it and hearing stuff about it is weird cause it's like... exactly how I imagined it and sometimes even better than I imagined.

#japan #日本

I've certainly found that to be the case. In game dev, the game almost always benefits from being as hardcoded as possible for the design. The design itself can be systemic and immergent, but its underlying structure usually best supports it if it's specifically built for it.

After a certain point of complexity, it becomes truly quite difficult to keep the actions of a game all mapped to intuitive buttons, so leaving a whole input unused would be quite a waste. It really is more intuitive once you try it.

Also game designer

That's the good shit

I read this as "I am a woman looking for a man and a woman"

Yes and even JSON as long as you make sure to validate and sanitize

Other than size, the biggest one for me is code injection from downloading saves online. For instance, if you use the human readable resource format for Godot someone on the internet can share a save file with injected GDScript that could be malicious.

Ah, so they leak

Ooof 😬

Also, embedded game window in the editor

Awesome I'd love to give it a read! Can you post a link?

Made Senior babyyy 😤

Ah interesting! This one's on me for assuming modern standards for games that existed before the standard was set. Good job recreating that!

That looks cute! Keep in mind tho, you've kinda broken pixel art rules. The Favel on the opposite side is higher res that the player one. Remember that your pixel grid needs to be consistent across the screen, not across depth/scale. Smaller = less pixels. Looking very faithful to pokemon tho 👍😊

Um, no, that's obviously a car

Oof gonna have to deal with some difficult ergonomics without operator overloading.

Maybe something like
Bitmask.or(
Bitmask.shift(0b1, 110),
Bitmask.shift(0b11, 300)
)
?

Can then override bitwise & and | as well. Using it might require chaining together multiple 32 bit values though, like (Bitmask(0b11) << 110 | Bitmask(0b1) << 300)

Don't know, might be a better way but that's my first thought.

Could make a Bitmask struct with a templated size for use on the stack, or a heap based one with argument in the constructor. Internals would be array of uint32s of size (bitmask size / 32), and operator overload the bitshift operator to return Bitmask, with the rvalue modulo 32 as array index.

Every feature has it's use cases. It took me years to unlearn the instinctual distrust in reflection, casting, GC allocations etc. in C# because everyone kept telling me they're bad when I was still learning long ago. Turns out, they're not bad if you know what they actually achieve.

Agree, teach them how to use them well. Beginners are very malleable and they will take things to heart that are very difficult to unlearn down the road, especially when the more experienced of us tell them "don't use this cause it's bad".

Actually, disagree. Singletons have been extremely demonized for no reason. There are times when you need more complex solutions, but those are extremely rare and mostly in the domain of threading. A static method and a manager can absolutely do wonders for readability and maintenance.

Don't pay too much attention to TGA, it's not actually relevant and doesn't give meaning to your game. "Clout" and quality have become completely disconnected in the industry, at the end of the day only the player's and your opinion matters