GameDev

638 readers

2 users here now

A community about game development.

Rules:

Adhere to the general lemmy.blahaj.zone rules (#1 being no homophobia, transphobia, racism or other exclusionary content)
Self-promotion is fine as long as it's not spammy - share your progress, insights, techniques and mishaps! If you recently posted, update the previous post instead of filling the frontpage with your project
Hide NSFW/NSFL content behind a clear warning, for example: [NSFW Nudity]

More rules might follow if they become necessary; general rule is don't be a pain in the butt. Have fun! ♥

GameDev Telegram chat.

founded 1 year ago

MODERATORS

[email protected]

TeaHands

[email protected]

What's a small misake that you've made from not knowing better that's easy to miss? (lemm.ee)

submitted 1 year ago by [email protected] to c/[email protected]

11 comments fedilink hide all child comments

For me, I recently had to revamp something because I was taught to use PlayerPrefs for saving all game data and had to move everything to a JSON in order to make cloud saves work or even just transfering save files to other devices.

you are viewing a single comment's thread
view the rest of the comments

[–] smokedsalmon 9 points 1 year ago (1 children)

I'd say abstract, but only abstract as needed. It's easy to get deep in the weeds future proofing, but spending all your time on interfaces is a surefire way to burn out.

[–] ThatsMildlyRaven 1 points 1 year ago

Definitely. You'll probably be able to tell ahead of time if what you're building should be reusable in different contexts/projects (e.g. an input system). But for more gameplay-specific code? Just make it work for whatever your game needs it do right now. Who the hell knows if you'll ever actually use it again, and if you do it'll probably still need tweaking anyways.