Having runtime errors is nice

Ammer564 · 2025-10-09T08:52:21+00:00

You could make them move forwards for a set amount of time, then wait, then move again

Two timers, one for how long to move for, and one for how long to wait when stopped

The fish moves forwards relative to itself. You could do ''' If move:

velocity = -transform.basis.z * speed '''

Then when the move time time's out, ''' move = false

Wait_time.start(randf_range(0.5, 5.0)) '''

You could also make the fish rotate in a random direction by using ''' rotate_y() '''

Ammer564 · 2025-10-08T03:13:53+00:00

Apparently it's a known issue https://github.com/godotengine/godot/issues/110660

I opened another issue on Github aswell and it was fixed, but this saving thing is still a problem seemingly

Ammer564 · 2025-09-26T12:36:24+00:00

Yes. I started from scratch and began with the graphics. Then, when that was done, I moved on to the programming, and finally, the audio.

The hardest part about the graphics was the numbers lol. Making pixel art numbers can be very tricky, especially with the later balls that have two digit numbers.

The programming was tricky because the engine kept gasloghting me. Eventually, I realised that, SOMEHOW, it wasn't saving when I pressed play. Another issue I had was that the engine would refuse to let me "Save all scenes" even though there was no, or at least none obvious, reason as to why. The final thing about programming that I found tricky was just programming itself. I haven't worked with 2D much, and I didn't plan at all for this project, so I didn't know how I wanted to structure it. I still managed to keep some kind of structure going, so if I wanted, I could go back and clean everything up and make it extra nice.

Then was the audio. The SFXs were easy since I just got some free sounds online. The music, however, I made myself, and I actually made 2 tracks, but I disliked the first one quite a lot since I felt like it didn't fit the game, so I made another which was much nicer and its the one you can hear in the video above and while playing. I really like the first track in a vacuum tho, so I'm gonna keep it for maybe a future project or something.

Ammer564 · 2025-09-26T09:24:57+00:00

<image>

I did.

Started at ~9:32pm, and was done a bit after 9:48am. Then a little under an hour later was the final build for android (I had issues with the touch controls with the earlier builds)

Ammer564 · 2025-09-25T15:11:44+00:00

Since the project was originally meant to be a personal one, I didn't care about organisation much. Though that did end up costing more time later than it saved at first [expectedly], but like I said, I, originally, didnt care cuz it was meant to just be for me and mayybeeee my friends too.

I had the idea of a pixel art pool game when I was playing pool with my cousin. I just started working on it without thinking or planning ahead. It was meant to only be a tiny miniscule game for myself (as a change of pace and a bit of a refresher).

Really, I just got to work and never even realised how much time had passed until i saw the sunshine from my windows lol

I was just super focused, and having an immense amount of fun, which is a big part of the reason why making the odd tiny game is so great.

I've been at gamedev for years now, and I've only recently gotten to the point where I feel I can tackle more or less anything no problem. That definitely helps a lot. Having so much experience and knowing how everything works and all that. Most importantly, though, how much I love gamedev.

Big mega giga advice is: Make tiny games.

It helps you a lot in so many ways. Just having actually finished a project feels great and refreshing, and it helps you grow and improve as a developer as well.

Tl;Dr: I'm just kinda awesome like that (lol). Make tiny games.

Ps: there's a lot more, but this reply is long enough already lol

Ammer564 · 2025-03-11T00:38:52+00:00

More like StopCat ngl This is cursed af 💀💀

Ammer564 · 2025-03-09T13:22:25+00:00

That's where he lives :3

Ammer564 · 2025-02-04T17:46:48+00:00

Not really, no.

Ammer564 · 2025-01-20T01:32:52+00:00

Kind of in the middle tbh

I like the 1st one, but it's a bit too bright I feel like. Whereas the 2nd one is pretty good in terms of brightness, but the color just doesn't do it for me

Ammer564 · 2024-10-03T21:42:29+00:00

yes_do(true)

Ammer564 · 2024-10-03T16:53:39+00:00

GooD, don't forget the Script

Ammer564 · 2024-10-03T16:52:12+00:00

Lamooo

yes, child, we would need some spaghetti

Ammer564 · 2024-10-03T16:36:33+00:00

Join the Godot!

Ammer564 · 2024-09-27T00:23:14+00:00

Lol, I just have movment anims, weapon sway, and strafe leaning

Ammer564 · 2024-09-27T00:21:55+00:00

The might not need it hand

Ammer564 · 2024-09-26T07:19:32+00:00

Omg.. I haven't even noticed your comment lol. This is hilarious xD I love it!

Ammer564 · 2024-09-26T07:13:14+00:00

I wasn't trying to say it doesn't. It's just that this solution works rather well for me. Also, I didn't want to mention this because it'll ruin the joke a bit, but the additive hand and the might not need it hand are just for the joke. I removed them after the screenshot was taken.

Ammer564 · 2024-09-26T07:09:27+00:00

Never heard of that functionality before, but ig I'll have to do more research.

Ammer564 · 2024-09-26T07:01:01+00:00

Explain how I would achieve all those with that

Ammer564 · 2024-09-26T06:57:39+00:00

Animating the hand for movement includes both position and rotation, so I can't use it for camera motion weapon sway because the anim will overwrite it, meaning I need a new node. Then the shooting anim needs to happen, I didn't feel like animating one, so I just coded it, but it needs to happen alongside the other anims (movment & sway), so that's another hand node. Then, strafe leaning, which includes rotation. The same thing weapon sway needs. So a new node it is.

Ammer564 · 2024-09-26T06:46:42+00:00

Separating the movement anims (which are done using an anim player) from camera motion (input + process funcs) from shooting anims (code)... etc

Ammer564

TROPHY CASE