the curse of video game programming is sometimes you come up with a word like 'pickuppable' that becomes a cornerstone of your class structure and you feel yourself die inside a little bit every time you have to type it out
- he/him
- vecderg.com/
✨SFW Artist + Gamedev✨
🔥Red panderg up to no good🔥
Mostly using Cohost for rambles, check links for Content!
✨mi ken toki e toki pona!
Bluesky (New Home)
bsky.app/profile/vecderg.bsky.socialMain Website
www.vecderg.com/Itaku (Art)
itaku.ee/profile/vecdergHTML Website (has RSS)
vecderg.github.io/Youtube (Videos)
www.youtube.com/@VecdergDeviantArt (Gallery)
www.deviantart.com/vecdergItch (Games)
vecderg.itch.io/You must log in to comment.
in reply to @trashbang's post:
with due sensitivity to name fatigue here, how much better or worse would "Grabbable" be as a name for this? that would be my first instinct, if it's representing the concept, in the -able / -er form of component naming, that it sounds like it is here...
I fear it is far too cemented by this point 
at the time I was trying to be very pedantic about what behaviour it actually represented (i.e. a physics object that can be picked up and held in the player's hands, or put in the inventory) so 'grabbable' may have been rejected for its ambiguity
that is such a classic, understandable bit of game dev path dependence. [salutes]
Or, in my case: Sometimes A Guy came up with terminology fifteen years ago that you know is just wrong but you have to live with forever
...I've spent the past five minutes trying and failing to find:
1.) that one 3D engine with a weird portmanteau name for the pill shape because the people who originally wrote it couldn't remember the word "pill."
2.) the weird portmanteau name in question.
cursed with having GroundCollectable legacy objects in a game that literally doesn't have ground
bool canPickUp;
bool isPickuppable; // only for objects using the new interface
bool canPickUpNEW; // FIXME: consolidate with isPickuppable
this is not a curse it is power.
every item in my game has a "basketabilityDifficulty" variable for how hard it is to turn that item into a basket.
Just make sure it isn't also unputdownable or the player's in trouble
My curse is that I name things silly things a lot and then I have to live with those decisions like naming a class "Fuit" instead of "Fruit" because as I was naming it my brain went "fuit gummy... hehehe..." About 80% of the time, I slip up and start typing "fr" and then have to back it up when I realize my mistake.