Pocket-Godot: Starter Kit for mobile game development using Godot
1–10 of 16 posts
Re: Pocket-Godot: Starter Kit for mobile game development using Godot
#2any links to examples?
Re: Pocket-Godot: Starter Kit for mobile game development using Godot
#3Maybe do a README at least before posting to HN? I compile Godot daily, but have been ignoring everything but GNU/Linux as a target platform. I don't see anything particularly unique about this being for mobile besides some pretty basic joypad and screendrag stuff.
Re: Pocket-Godot: Starter Kit for mobile game development using Godot
#4Maybe do a README at least before posting to HN? I compile Godot daily, but have been ignoring everything but GNU/Linux as a target platform. I don't see anything particularly unique about this being for mobile besides some pretty basic joypad and screendrag stuff.
Video overview:
Re: Pocket-Godot: Starter Kit for mobile game development using Godot
#5Maybe do a README at least before posting to HN? I compile Godot daily, but have been ignoring everything but GNU/Linux as a target platform. I don't see anything particularly unique about this being for mobile besides some pretty basic joypad and screendrag stuff.
Video overview: https://www.youtube.com/watch?v=jMBNfMqRb58
Here's the script for the first half of the video; second half kind of needs the video to make sense:
Hey, it's Lucky. Sorry for disappearing on you guys, but I've returned bearing gifts. This is my first project in Godot 4.3, called Pocket C. It's a small collection of touch-based controllers for mobile devices, which I think are a great starting point for building mobile SL touch-based games.
In this project, there are three demos included: a first-person demo, a third-person demo, and a top-down demo. These demos are inspired by popular mobile games like PUBG, Call of Duty Mobile, and League of Legends: Wild Rift. All these controllers are based on a joystick-touchpad combination, where the joystick is on the left side and a touchpad is on the right side. This layout is commonly used in many viable mobile games today, and it's at the core of all these demos.
We'll run through the code and the project so you can get started on making your own mobile games. All the source code and assets are included in the video description, along with a GitHub repository link. There's also a built APK, so if you want to test it on your mobile device, it's available there as well.
Re: Pocket-Godot: Starter Kit for mobile game development using Godot
#6As someone who has recently been doing Godot mobile development with Cursor as my IDE, this repo and the video in another comment gave me some quick thoughts.
1. The main thing the library seems to offer is some pre-packaged libraries for mobile touch controls in GDScript, the custom language for the Godot game dev framework.
2. I have recently come across similar problems to what that this library tries to solve.
3. However, the way I went about solving it was basically using Claude and ChatGPT as my co-developers and asking them to answer coding questions. Here’s a quick example prompt about coding GDScript similar to some of the attributes of the library: https://chatgpt.com/share/c8e713e3-0662-4c7d-8645-9a76b0c032...
4. An optimistic perspective from all the above is that AI coding assistants can make it easier for people to develop libraries like this faster.
5. A negative view would be that AI coding assistants mean people don’t necessarily need “libraries” like this if an LLM can spit out the same results in a couple queries (rather than hunting around Github or the internet for pre-packaged code).
Re: Pocket-Godot: Starter Kit for mobile game development using Godot
#7Step up your README game... at least link to your Youtube and say more docs coming soon.
Re: Pocket-Godot: Starter Kit for mobile game development using Godot
#8As someone who has recently been doing Godot mobile development with Cursor as my IDE, this repo and the video in another comment gave me some quick thoughts. 1. The main thing the library seems to offer is some pre-packaged libraries for mobile touch controls in GDScript, the custom language for the Godot game dev framework. 2. I have recently come across similar problems to what that this library tries to solve. 3.…
> 5. A negative view would be that AI coding assistants mean people don’t necessarily need “libraries” like this if an LLM can spit out the same results in a couple queries (rather than hunting around Github or the internet for pre-packaged code).
Why use a library when the LLM can spit of a unique reimplementation of the library logic every time you need it?
The future is terrifying.
Re: Pocket-Godot: Starter Kit for mobile game development using Godot
#9As someone who has recently been doing Godot mobile development with Cursor as my IDE, this repo and the video in another comment gave me some quick thoughts. 1. The main thing the library seems to offer is some pre-packaged libraries for mobile touch controls in GDScript, the custom language for the Godot game dev framework. 2. I have recently come across similar problems to what that this library tries to solve. 3.…
> 5. A negative view would be that AI coding assistants mean people don’t necessarily need “libraries” like this if an LLM can spit out the same results in a couple queries (rather than hunting around Github or the internet for pre-packaged code). Why use a library when the LLM can spit of a unique reimplementation of the library logic every time you need it? The future is terrifying.
An LLM that just replies with an executable?
Re: Pocket-Godot: Starter Kit for mobile game development using Godot
#10As someone who has recently been doing Godot mobile development with Cursor as my IDE, this repo and the video in another comment gave me some quick thoughts. 1. The main thing the library seems to offer is some pre-packaged libraries for mobile touch controls in GDScript, the custom language for the Godot game dev framework. 2. I have recently come across similar problems to what that this library tries to solve. 3.…
> 5. A negative view would be that AI coding assistants mean people don’t necessarily need “libraries” like this if an LLM can spit out the same results in a couple queries (rather than hunting around Github or the internet for pre-packaged code). Why use a library when the LLM can spit of a unique reimplementation of the library logic every time you need it? The future is terrifying.
People like having standards, that's why. They make processes more simply repeatable and experience more easily transferrable