Framebuffer @framebuffer.cl · 03/04/2026I gave a panel at #SAFE2026 (almost 2 months ago lol) about my laser-cut cardboard badge with an e-ink display on a Raspberry Pi. One of my greatest achievements ever. Thanks to everyone that came to see me! 010 1
Framebuffer @framebuffer.cl · 21/01/2026I (the green lizardboi) spent 3/4 of the battle unconscious (as usual), but I lived to tell the tale. #dnd #drawing #painting 040 4
Framebuffer @framebuffer.cl · 25/12/2025I'm really digging this technique/brush of just gradient map, blending and wild brushing #art #furry #painting 030 3
Framebuffer @framebuffer.cl · 23/12/2025Here's all of my #dnd OCs: Erabus (the lion with the crossbow) Harbinger (the tiefling/foxxo at the bottom) Asher (catto with the sword) Moontracer (doggo at the front) Stock (catto, with the bandana thing) Aitken (the buff Dragonborn) Tarkus (the Dragonborn with the staff) #painting #art 071 7
Framebuffer @framebuffer.cl · 22/11/2025they doin surgery on a [cardboard] dog (with horns) #badge #furry 062 6
Framebuffer @framebuffer.cl · 19/11/2025laser goes nyooooooom #badge [Done at @amaqueta on Instagram] 020 2
Framebuffer @framebuffer.cl · 15/11/2025you know it's gonna get serious when you get the CAD software out. 000 0
Framebuffer @framebuffer.cl · 15/11/2025so, I had this issue where I moved the lines from Affinity to AutoCAD... and they were all destroyed. So I had to redo a lot of the badge 100 1
Framebuffer @framebuffer.cl · 06/11/2025Update on the #badge: - now supports text and QR code generation - it now runs a library that adds a buuuuuunch of things, like drawing shapes 120 2
Framebuffer @framebuffer.cl · 05/11/2025this one's gonna be the Experience(tm) of all time. (thanks @kiwa.space for being the bestestetstst ever) 110 1
Framebuffer @framebuffer.cl · 23/10/2025here's the start of my next adventure: making my new badge for #SAFE2026 ! so, here's the first piece: 110 1
Framebuffer @framebuffer.cl · 18/04/2025guess who absolutely annihilated its website database and didn't notice until now: this is not supposed to be this low. I have to piece together a backup from several sources and **I HOPE** that it has at least up to the last devlog. My most sincere: apologies. 000 0
Framebuffer @framebuffer.cl · 25/02/2025WOO 🥳🎉 100 FOLLOWERS AAAAA Thank you vvvv much to everyone that likes what I do (with lots of love and care) Let's keep this going, with more games and creative things. I love this and I'm glad you do too. Love y'all -frame #100followers #milestone #gamedev 092 9
Framebuffer @framebuffer.cl · 15/02/2025i went to college for 8 years to do this: #sims #simsultimatecollection 010 1
Framebuffer @framebuffer.cl · 30/01/2025well folks, I wanted to finish the #PirateJam but, well... Remember that food poisoning I mentioned before? Yeah that ate my whole safety margin and then some. The joys of #gamedev Picture: just me on an IV drip. CW'd just in case. 040 4
Framebuffer @framebuffer.cl · 24/01/2025📝 On day 6: well, more modelling. I have a new idea for a map, gonna have to rig up and try. I need to get to gameplay rn #gamedev #indiedev #PirateJam 070 7
Framebuffer @framebuffer.cl · 23/01/2025📝 On day 5: started to model the map and try some ideas out. I found it's a little bit cramped, so I'll try another idea today! #gamedev #indiedev #PirateJam 090 9
Framebuffer @framebuffer.cl · 22/01/2025📝 On day 4: I started doing the 3D modelling for the map itself. Gonna go with the same style I've been perfecting since I did my first game back in September. It's easier now that I have all the boilerplate done. #gamedev #indiedev #PirateJam 0132 13
Framebuffer @framebuffer.cl · 22/01/2025📝 On day 3: ...well I started from scratch. Why? I was spending way too much time trying to make some basic things. I felt that I would be able to go faster if I went with something tried and tested. So, this is the new game, I guess. #gamedev #indiedev #PirateJam 0131 13
Framebuffer @framebuffer.cl · 22/01/2025📝 On day 2: the game started to come alive! I did the code for the tilework and some basic movement between tiles. #gamedev #indiedev #PirateJam 091 9
Framebuffer @framebuffer.cl · 22/01/2025📝 On day 1: dev work on graphics started. The style: isometric tile-based 2D graphics, for a second-person game. You are controlling yourself from above. #gamedev #indiedev #PirateJam 0111 11
Framebuffer @framebuffer.cl · 20/01/2025testing testing 123 #gamedev #indiedev 📷 - Instagram @ framebuffer.svg ☕️ - ko-fi.com/framebuffer 170 7
Framebuffer @framebuffer.cl · 17/01/2025VERY IMPORTANT ADDENDUM: For your assets, inside src, add them all to a folder (let's call it resources) and add it to .gitignore. This is the one I have: if you put the name of a folder, and then a forward slash at the end, it'll ignore the whole folder and everything inside. 000 0
Framebuffer @framebuffer.cl · 17/01/2025Hey, remember the thread when we created a new repo? Now it's a great time to commit! Go back to GitHub desktop and create a new commit, preferably to main. This will be your ground zero from now on. 100 1
Framebuffer @framebuffer.cl · 17/01/2025When creating your project, make sure that: - You create it inside your src folder. Disable the **create folder** checkmark. It will make a mess if you don't. - If you're doing the #PirateJam or any web game, use the Compatibility renderer. Web only supports this one. 210 2
Framebuffer @framebuffer.cl · 17/01/2025Now, this is personal preference. My projects are **always** stored with the template and editor they were developed and released with. This is so I can open a project *as is* without having to redownload the engine and maybe face incompatibilities. 100 1
Framebuffer @framebuffer.cl · 17/01/2025git won't complain if your files don't exceed *I think* 50MB. Anyway, you shouldn't push files that large, anyway. In case you have money to spend, and you want to version control larger files, 100 1
Framebuffer @framebuffer.cl · 17/01/2025When all is said and done, you will have what's called a "merged pull request". This means the code has been committed to the branch, and now it contains all the changes made outside. You can press the Delete Branch button if you want. This is useful if you branched to develop a specific thing. 100 1
Framebuffer @framebuffer.cl · 17/01/2025The next page is a summary of the Pull request. Usually, this page is used for teams to review the changes being discussed before pushing. If you're all cool and good, a message saying "This branch has no conflicts with the base branch" will be displayed. This means we are ready to go! 100 1
Framebuffer @framebuffer.cl · 17/01/2025And finally, down below: the changes you're pulling! The detail of the whole branch being pulled onto main, plus the changes made are shown. In this case, a file was deleted, so no diffs (or "differences" are shown). 100 1
Framebuffer @framebuffer.cl · 17/01/2025You can then detail what you have done, for future reference. There's a lot of formatting options! The features on the side are not relevant, but if you want to know: you can assign the task to reviewing this to someone else, make it part of a dev milestone, and more! 100 1
Framebuffer @framebuffer.cl · 17/01/2025Pull requests work by comparing both the branch that's being merged and the target it's being merged onto. If everything's good, it'll say *Able to merge* If not, the stories differ a lot and GitHub doesn't want to mess up anything it shouldn't. Diffs are *differences* between commits. 100 1
Framebuffer @framebuffer.cl · 17/01/2025One of the cool things about git, is that you can have branches of *separate alternative* paths to your project. This is *insanely useful* for teams. If you go to "Current branch", you can create a new one and see which ones currently exist 100 1
Framebuffer @framebuffer.cl · 17/01/2025Congrats! You did your first commit! Make sure you do this often. Forgetting to do so **will** make this system useless. As you start pushing things, you'll start having a neat history of your project. Each commit has its own code, and you can go back and forth through it all! 100 1
Framebuffer @framebuffer.cl · 17/01/2025To upload to GitHub for the first time, you'll be prompted with this. This is where the *remote* site is going to be set up. Usually, leave it as is, and **make sure "Keep this code private" is checked.** You don't want anyone looking your super cool game for a jam! 100 1
Framebuffer @framebuffer.cl · 17/01/2025Whenever you change something, GitHub Desktop will notice "hey something's different!". It's going to display the *differences* between each commit you've done. To commit a change, you **have** to describe what you did. When you're ready to commit, press the "Commit to main" button. 100 1
Framebuffer @framebuffer.cl · 17/01/2025Click on "Create a new repository". - Give it a catchy name - add some description so you know what this repository is about - check the path, this is where your game will live - on "Git ignore" choose Godot from the dropdown. - If you don't plan to release your code, just skip license. 100 1