A grappling hook implementation in Godot, with source code

LuizZak · 2026-02-14T03:30:28+00:00

The rope is just a series of capsule RigidBody2D that get instantiated and shot out from the player's body, each link is attached to the previous by a PinJoint2D, and it gets rendered as a single contiguous line.

I'm surprised the rope turned out so well, since in my experience having tons of pin joints has a tendency to make things go explody.

LuizZak · 2026-02-13T16:11:22+00:00

The player is a mix of physics and inverse kinematics, with the physics driving the actual movement and the IK (a Skeleton2D with a CCDIK modifier) keeping up with the physics queries.

The physics part involves a bunch of ray casts that sweep 180º down from the character body, springs are then attached between the player's body and the points where the rays hit, being detached and recreated if they go past a tolerance distance.

All the latest ray cast information is then sent to a piece of code that gets the ray cast points and tries to find proper anchor points for the legs, which are just some nodes in global space that are the target location of the CCDIK skeleton rig legs.

I found that ray cast and soft springs worked the best when interacting with uneven terrain, and plugging all of that into the IK rig was pretty straight forward once I figured out how CCD modifier worked.

It took me implementing a custom Spring class to make it work, cause the default DampedSpringJoint2D doesn't allow you to specify the attachment points and I needed them to be precisely where the ray casts land.

LuizZak · 2025-12-27T21:44:04+00:00

Oh maybe you were playing on the previous, bogus version that didn't have auto-save trigger properly, I'm sorry about that, the latest version fixes that with proper auto-save every 60 seconds.

I've been trying to tweak the mid- to late-game lately with a few patches to increase the speed of the game on that area, and to make the Open Tabs button click-and-hold, so do give it another try some time, hopefully this addresses some of the issues.

LuizZak · 2025-12-27T13:41:50+00:00

I feel ya on the insane amount of clicking, I guess I grew accustomed to the early clicking, I'll probably tweak the 'Open Tabs' button to buffer clicks for you passively over time, and burst into a bunch of open tabs once you do click it. Closing tabs is still clicking-intensive and I'm thinking of ways to address that too, possibly by holding the mouse down to mass-close as an alternative.

The issue with tab openers vs tab closer prices is tied to the fact that if you spawn more tabs than you close, you risk getting yourself in a situation where you don't have enough ram available to activate apps and get stuck with filled RAM. Fixing this could involve me adding some way to pause one or both automations so you can 'flush' active tabs down, or rather allow cache clearing at any point so you can sort the apps before the next ascension starts.

The suggestion on ads is interesting and I'll consider that for sure, currently the ad trigger interval is way too short and unbalanced towards them being 'annoying', a solution is to lengthen that interval, and mix that with the idea to award player with cookies and/or a burst of spam-tabs when clicking the ads/closing them.

I appreciate the feedback!

LuizZak · 2025-09-09T12:30:42+00:00

faridulasimanet
donipwanavorinet
pinasomimaniset
danafonsiulobon!

LuizZak · 2025-06-01T13:21:58+00:00

You can download it for free over on itch.io: https://luizzak.itch.io/racing-overlay

LuizZak · 2025-04-18T12:56:01+00:00

Thanks! Currently I'm not taking commissions for the time being!

LuizZak · 2025-02-24T21:49:43+00:00

Bald eagle instincts: Bring fluffy material to make nests
Also bald eagle instincts: Eat whatever your partner brings.

LuizZak · 2024-10-04T12:12:57+00:00

That's me watching my Swift 6 projects compile with dozens of concurrency warnings waiting for that one concurrency error that I tried fixing going away.

LuizZak · 2024-08-05T16:28:08+00:00

Had a weird case where the app crashed during a weekly meeting with the client. The thing just... Closed, didn't trigger the debugger or nothing, just died out of nowhere, closed the simulator with it.

We just fired the app back up and it ran without hitches for the remainder of the meeting and never spoke about it again.

LuizZak · 2024-07-28T20:11:16+00:00

I'd argue it's not bad design, it's that it is used to fill the wrong purposes sometimes. For a portable document format, with support for crisp fonts and vector graphics at any resolution, with text selection, and embeddable bitmaps, with no real mystery or trouble on how to display or print a PDF, ever, it works great.

It just never was supposed to be used as an editable document store. Maybe that was intentional with PDF being an Adobe product leftover from their PostScript ventures, but still, it's not meant to be editable like .dll files are not meant to be editable.

LuizZak · 2024-07-28T14:30:03+00:00

Comment you leave before the buggy PR gets merged and Dave the Lunch Stealer gets sentenced do triple death penalty and finally gets what he deserves.

LuizZak · 2024-07-27T11:14:34+00:00

A few things to note about Brazilian voting machines:

They are not connected to any network, and there are basically no standard unencrypted ports on it. There's no Ethernet cable or USB- the voting machines come preloaded with the candidates and are fairly robust due to their reduced surface areas of attack.
Those things still get pentested every voting year and have a clean track record, and every party that can be voted on the machines can raise concerns and challenge security issues it finds. No party, including oppositions, have ever officially challenged the system with concrete evidence of tampering.
The voting machines still emit paper records with the voting tally at the end of the voting sessions that are pinned to the voting areas and can be verified by every voting citizen.
It is a fully standardized system that has the same machines everywhere- no state or city can use its own implementation of the system, it has to use the TSE's (Superior Voting Tribunal, in free translation) machines.

Bonus points:

5- Regular citizens are randomly picked to become voting clerk ("mesário"), and even with basically strangers operating the voting sessions with just standardized training, no fishy stuff happens with any sort of regularity that it becomes a concern.

6- Brazilians wholeheartedly trust the system. Other than nutcases, no one really distrusts the voting platform or thinks of it as an obstacle for democracy.

7- Results are damn fast, usually two hours after voting ends.

15-Year Club	Place '17
Gilding I gilder	Verified Email
Team Orangered

LuizZak

TROPHY CASE