That’s… Kind of insane! I’ve been following Bitcraft every now since it got announced but I never expected them to go to this direction. The blog post makes sense but I’m curious what license they’re going to use. It could be a legal minefield to try and stop people from stealing the game, re-branding it, then profiting off of it.

It’ll be really curious to see how this plays out because there isn’t really any major games that went open source, much less one that’s going to be actively monetized like Bitcraft.

Our focus will be on a smooth and successful Early Access launch on Steam, which is our highest priority. Only once we are happy with the state of the game will we start the process of open sourcing BitCraft.

Anyway, it sounds like open-sourcing the game might take a while. I hope early access works out for them.

Isn’t Pangora dead? It hasn’t been updated in a year.

Don’t submit AI generated content to this community. Next time will be a ban.

Yup. I asked around in chat and we’re 99% sure it’s a joke. They don’t actually have a team big enough to transition to a whole new engine.

The project is for making unofficial drivers for Apple’s chips, which very few people are trying to do. Without Asahi, you can’t run Linux on Macbooks.

If your goal is to cash in on the blog, your best bet aside from ads is to look for sponsorship opportunities. You can look into services that align with your user’s interests and contact them to set up affiliate links for you (like how any decently-popular YouTube channel has a sponsored segment).

This can be in the form of an ad in the header/footer of your blog, an ad shown on the side of the screen, or affiliate links you put in your posts. If you’re going to casually recommend your affiliates, I think you’re legally required to add a disclaimer that it’s an ad, lots of blogs do this in a small text at the top of the post.

Taking a quick look at your blog, you can probably start shooting emails to popular vpn providers and ask if they’re interested in getting sponsored here.

You can create a Group for the planet then check in your code if that’s what the area is touching. Ex: if body.is_in_group("planet"): #do something

Sounds like you misconfigured your layers and masks. The collision mask determines which layers it can touch, so it sounds like you have the earth Rigidbody on layer 1 and are trying to detect the body.

I was actually considering Defold for the longest time, it’s another really great open-source engine, but I just found that Godot feels so much nicer to develop in. I may give it another try later, because I do enjoy making small webgames.

Performance testing is a whole can of worms. It’s hard to get an idea of how performance changes because it’ll depend a lot on the nodes and scripts being used. There could be huge regressions in specific cases and functions and no difference in others. Usually you’ll need a suite of tests to see what changed.

I haven’t checked since making this post but when the idea was floating around the devs said they preferred multi-communities (proposal 2). That’s still on the Lemmy roadmap but isn’t here yet.

That said, Piefed apparently implemented something similar to proposal 3 so maybe the devs can change their mind and copy them instead.

Oh hey, it’s been a while since I’ve written this. Thanks for sharing it again. When I posted it last year to the fediverse community, people were not ready for it.

Just make it not cost as much as top-end x86 chips in laptops and have the iGPU not be garbage and I’ll be in.

It doesn’t do anything by default, you have to go to settings > zen mods > click the settings icon next to the mod name.

If you set the options and nothing happened then I’m not sure, it worked for me instantly when toggling stuff off.

I’ve started using more Zen Mods recently too, the most important one I would say is Zen Context Menu - which lets you de-clutter the options when you right click anything. There are way too many options being shown when you right clicked the sidebar, but it’s a lot nicer to use now.

Thanks! It is a great replacement if you can handle some jank.

While we prepare for the stable release—no more than a week’s time from now—let’s enjoy one last roundup of changes.

Hype! Looking forward to updating my projects to the newest version.

but every job also says 100+ applicants

Most of them are spam or people testing their luck even though they’re underqualified since applying to jobs is usually just a click nowadays. Don’t worry too much about it.

I get people that make tutorials for “content” even if they suck at their job, but I CANNOT get over video tutorials where someone gets completely lost and doesn’t cut it out of the video.

Anyways we’ll go here-oh there’s an error. Uhm. Maybe we can do this? That didn’t work. Maybe that? Hang on, maybe it’s in preferences? Oh, it’s in tools, no, wait, oh I just wrote the name wrong

Would it kill you to edit that out and stop wasting my time?!

It’s not a thing and I totally agree it should exist, there’s a proposal for it on GitHub.

If you want to handle different types, the right way of doing it is giving your parameter a generic type then checking what it is in the function.

func _ready():
    handle_stuff(10)
    handle_stuff("Hello")

func handle_stuff(x: Variant):
    if x is int:
        print("%d is an integer" % x)
    elif x is String:
        print("%s is a string" % x)

This prints 10 is an integer and Hello is a string.

If you really, really need to have a variable amount of arguments in your function, you can pass an array. It’s pretty inefficient but you can get away with it.

func handle_stuff(stuff: Array):
    for x: Variant in stuff:
        if x is int:
            print("%d is an integer" % x)
        elif x is String:
            print("%s is a string" % x)

Then you can pass [10, 20, 30] into it or something. It’s a useful trick.