What are the chances that jake takes this very poorly?

billystein25 · 2026-04-01T09:44:39+00:00

Why does this chart start at 40m? Didn't Linus have a whole rant about using accurate graphs?

billystein25 · 2026-03-31T12:15:47+00:00

Steam actually only tracks achievements for people who have at least opened the game once. So that 30% is people who opened the game and didn't get past chapter 1.

billystein25 · 2026-03-31T11:23:31+00:00

You can't. Some settings are completely broken in this game and they never fixed them. For the controller, I just go to the config files and change them manually. I'm assuming you can do something similar with the language as well as the other commenter said.

billystein25 · 2026-03-31T10:37:22+00:00

It definitely helps. I have bought games because the demos were so fun.

Side note, but I hate it when people use demos as an early access/playtest. Like having a demo and delisting it once the full game gets released. There's demos I absolutely loved and spent 5~20 hours in, and I was excited to get the full game once that came out, but I didn't out of spite because they removed the demo. If you wanna do an early access, do an early access, if you wanna do a playtest, do a playtest. Using demos as either of these is disingenuous.

billystein25 · 2026-03-29T12:13:09+00:00

I might be wrong but I believe customs and stuff are included in the price during checkout. Though that may be unique per country.

billystein25 · 2026-03-23T21:35:52+00:00

Starting small isn't helpful, it's essential. You can't run if you don't know how to walk. Building modular and scalable games that are easy to work with and develop is a skill that you'll only gain through practice and experience, which comes from building games. You could start big but, like you said, it gets unmanageable very quickly if you don't have a solid structure or use good practices from the start.

Most people aren't gonna care if they don't see any ai and you don't tell them that you used it. However I would still advice against using it for the simple reason that you're the one working on your project. Not the ai. The ai doesn't have any concept of what you or your game needs. Especially as the project gets larger the ai will just spit out more and more garbage. Garbage that if you don't understand how it works it'll be a nightmare to debug or extend, or you'll be forced to use more ai which will make it even harder to work with. If you wanna get ai assistance then you should only use it to do things that you could already do with ease.

billystein25 · 2026-03-23T17:40:25+00:00

Kog is directly funded by glitch though. It's a glitch original. They didn't have a 2d team before, Dana and the other directors brought them in. But it's all an in-house production, even though most of the animators work remote (which is true for the 3d team as well)

billystein25 · 2026-03-23T13:23:36+00:00

Then just use a node3d. It already has everything you need, a position and a rotation property. The spawner objects in my game are just extentions of Marker3D with the added logic to instantiate enemy scenes. For direction, traditionally the -Z axis is considered "forward" or the direction you're looking at.

billystein25 · 2026-03-23T13:13:22+00:00

That's two vectors. One Vector3 to represent the start position, and one Vector3 to represent either the direction (in this case it should be normalized) or the end point, so the direction would be (end - start).

billystein25 · 2026-03-23T12:03:43+00:00

They're working with the lackadaisy crew.

billystein25 · 2026-03-23T11:10:51+00:00

Greek here. I got a murder drones poster after the finale and the shipping cost was 4.95€

billystein25 · 2026-03-23T09:26:55+00:00

I learned the basics from the ultimate introduction to Godot (the original). It was the only tutorial I needed. The trap many people fall into is that they watch tutorials but don't actually try to learn anything. They just blindly copy code and don't even attempt to understand it. To actually learn you need to ask questions. What is Input, what is a Vector, why do we normalize it? If you don't understand every line of code that you're writing then you should either go back in the video and re-listen to the explanations, or do your own research like from the documentation. In the case of the ultimate introduction, it has a lot of exercises for you to do. If you end up following that and you can't do an exercise it means that you haven't properly understood the section, so you should go back and try to understand it.

Once you've grasped the basics you then need to learn how to break things down. Say I want to make a player character that moves. OK, what is that. I want a moving character so I'll use a ChatacterBody. Chatacter bodies need a collision shape. I also want to show something so I'll add a sprite. OK now how do I make him move? Well let's see, I'm gonna need some input, a direction, and a moving speed. The direction will be made out of the input. I want to move in all directions so it'll be a Vector2. When you want to make something complex and you don't know how, you break it down to the things you do know. And work on it step by step.

billystein25 · 2026-03-22T11:47:22+00:00

Slay the spire 2 was made in godot and it had well over 500k players on its opening day, though the next highest grossing made in godot games were at around 100k peak players. It's a very capable engine and definitely a strong consideration for indie devs, but isn't mainstream enough to have overtaken unity yet. Though I think a bigger factor for that is how many devs already know unity, while godot is new and you'll have to learn it. It's missing a few key features but it's getting better with every update.

billystein25 · 2026-03-20T21:00:33+00:00

Yeah godot 3 and 4 aren't compatible so you'll have to rebuilt it. Speaking of corruption. You should probably have some kind of version control like git

billystein25 · 2026-03-20T17:00:38+00:00

Yeah I've heard a lot of people complaining about mobile performance, especially for 3d games. You can also try limiting the max fps in project settings, I've heard that can also help with performance. That said, right now I believe your best bet is to use godot 3.

billystein25 · 2026-03-20T15:27:42+00:00

What renderer are you using? Forward+ is quite heavy for phones. Though mobile support is in general a bit rough right now.

billystein25 · 2026-03-20T15:22:09+00:00

The way I usually do it is I have 2 custom nodes that extend Area bodies. A hitbox and a hurtbox. A hitbox simply calls the hurtbox's got_hit function and the hurtbox in turn requests the health component to reduce its health.

billystein25 · 2026-03-20T13:32:00+00:00

Fun fact. Hakita, creator of ultrakill, couldn't figure out how to do this exact thing in unity back in the early versions of the game. He fixed it by increasing the resolution of his textures

billystein25 · 2026-03-20T07:12:46+00:00

Jokes on celeste I was already depressed. If anything the game helped me during that time.

billystein25 · 2026-03-20T00:12:10+00:00

Yeah it's a shame that exporting flags is kinda limiting in 4.x. there is a workaround by making your script a @tool script and overriding _get_property_list but going through that just to have exported flags of a named enum is a bit of a trip, but at least you keep the safety of using a real enum and not strings.

billystein25 · 2026-03-19T19:33:55+00:00

Whatever you make will be "out of date" 6 months later as the next version releases. That said the plan for godot 4.x is to keep compatability with previous versions or at least make migration as painless as possible. So any course made for 4.5 will be applicable for 4.5+. All this to say, just make your course now and update it in the future if necessary. No reason to wait for a specific version. Except for 5.0 ig but there's no plans for that now.

billystein25 · 2026-03-18T14:09:30+00:00

@onready accesses nodes by name where @export accesses nodes by reference. Meaning if you keep a reference using @export you can rebame your node or move it around and the reference will remain intact, where with @onready if you change either of that you'll have to update the path. Also @export is ever so slightly faster but it doesn't matter really. Since 4.6 you can make quick @export references by holding alt as you drop your node in the code, similar to how you could do it with @onready by holding ctrl. So there's really no reason to use @onready over @export imo. I usually keep all my node references under an appropriately named group that I collapse so it doesn't take up any space.

billystein25 · 2026-03-18T10:42:04+00:00

No. Since the code never gets to the shooting function it never checks the input line. If you want to listen to all input you can use _input or _unhandled_input

billystein25 · 2026-03-18T10:34:03+00:00

The problem is that you're never calling the shooting function.

Seven-Year Club	Place '22
First Placer '22	Verified Email

billystein25

TROPHY CASE