Making game building accessible to everyone with @GDevelopApp, the open-source #nocode game engine. Prev: Gaming @google.
"florianrival" too on other platforms
Looks like my baby engine is now a grown-up!
Now with 3D, 3D physics, multiplayer, prefabs - all open-source - but also an entire ecosystem (asset store, cloud builds, leaderboards, player accounts, 100s of extensions, premium templates). And it's just the beginning ⬇️⬇️
2024 is not finished yet but GDevelop already crossed 12k stars on GitHub 🌟
Thanks to everyone supporting, contributing and building with GDevelop 💜
Try #GDevelop a free, #opensource, 2D and 3D #nocode#gameengine
@BaldieAndBaldie I see! Maybe some profiling to do to improve things on the game engine side (50k objects is a lot! Glad it works :))... but for a more lightweight example, having something simpler should work.
@BaldieAndBaldie 5-10MB at most would be cool. I've not looked deep inside the existing example - it's possible that 70% of the size is from a few assets. Keeping them small/reusing them could help showcase how this extension could work even for "small" games.
@BaldieAndBaldie I'm including the extension in the changelog of the upcoming GDevelop version 👍 The example is quite "huge" (40MB) in terms of size and the instancing of objects at the beginning makes the game to stall for ~10 seconds. Maybe we can include a lightweight example in the future :)
@FilippoArtemis@GDevelopApp@DazzleDevTeam You're right. At the same time, we must integrate Steam payment APIs (in addition to Stripe, PayPal, Google and Apple on mobile that we already handle) so it's yet another system to maintain and a non zero maintenance cost (in time) now and later. Maybe we'll try one day!
One thing to note: disputes you win in Stripe are still counted in your dispute rate (you could win 100% of your dispute and still above the threshold).
Won or lost it does not matter: https://t.co/uF8aIVOjOQ
🏆 For the first time in a decade on @Stripe I've started winning disputes with my vibe coded dispute responder
I used to ignore disputes so I almost always lost them, now I've started winning, this one is the first big dispute for $1,199 USD!
Whenever a dispute comes in, my site gets a webhook notice from Stripe, it then starts collecting evidence and generates a PDF with entire user's details, when they signed up, and most importantly what they did in the app
In this case the user used the app for months, generated thousands of photos then tried to get the money back from their bank
The evidence has to be REALLY detailed, and REALLY good, which is why it's perfect to vibe code it, you can get quite detailed with different types of users and activity on your app, and put that all in the PDF
I'm shocked because I again I never would win disputes before
People in US especially abuse the [ chargeback ] or [ dispute ] en masse, unlike the rest of the world, it's easily built into their banking app next to every transaction, so it's one tap to get free stuff. And why not? You get free stuff!
It's destructive for business owners like me on many levels, if I get over 1% disputes on my account, I risk getting shutdown permanently by Stripe, Visa and MasterCard, like permanently for life, not just my business but on my personal name too, it's ruthless
Disputes are also super expensive for business owners: you don't just pay back the amount they disputed, for every dispute you pay $30, which you only get back if you win!
But with AI we can now create our own tools to fight back against dispute abuse and finally win! 🎉
@VicSlavy@BaldieAndBaldie@cettelune Others (official or community extensions) are loaded from a huge library of Apache 2.0 licensed icons. Impossible to redo them all, but the idea would rather to prioritize the most used objects and behaviors which would cover 90% of usage :)
@VicSlavy@BaldieAndBaldie Hello! There is a mix of icons in the engine indeed, some designed by @cettelune (our in house designer :)) for the app (toolbar, etc), other (the blue-ish icons) are fairly old and for "first party" objets => we could get some help here.
@BaldieAndBaldie The automated bot converting your extension issue into a "Pull Request" got some difficulties (I think because the example was included, but we should fix it).
But no worries, it's here and we'll take a look asap!
I tried the example and it works well!! 👍✨
@BaldieAndBaldie Let me know when you try one of these solutions? gdevelop-community-list might be the easiest and we will surface this in the engine soon hopefully.
@BaldieAndBaldie On the repository, you either open a new issue with the proper JSON file so that it's picked by the bot and a PR is opened to update the extension - or you just clone, update the extension Json file and submit a PR (might actually be easier and faster).
@ByronMinick@GDevelopApp Hey! Florian here (GDevelop founder). I see what you're saying, and that's why we created in the past many free materials for GDevelop (see "Learn" tab and youtube videos): https://t.co/NqPQ6FaeRR
@BaldieAndBaldie The second one (GDevelop-extensions repository) we're making reviews for basic usability for experimental extensions (and for "reviewed" extensions, we maintain them, so we're more careful about what get inside this list).
Yours could easily be an experimental extension I think!
@BaldieAndBaldie Congrats! 🥳 So you can:
- Easiest, done in a few minutes => add a link on https://t.co/QosjNNe1hV (list that will become at some point visible in engine)
- Ideally, submit it to https://t.co/YrTpjaMldD so we can review the extension and make it accessible from the engine itself