questions in Indie Game

#Devruary One thing I learned the hard way through devving is to never underestimate how sensitive code can be. I can't tell you how many times my games kept crashing cos of ONE space where an underscore should have been in a random file.


Which one do you all like the most? Lemme know in the comments.

Loading...I already finishe Neon Pulse FM
radio
[Electronic Music] (credits to @CLANYAGAMI
, Thomas Gaming, @Ramiro_LD
:
).
#Devruary The advice I would give a new dev is pretty simple: the more you like the act of testing things, the better off your mental health will be on a project - you'll have to do a TON of it.

#Devruary What advice would you give a new dev? 
I'd definitely recommend to reduce the scope of your first game so it can be finished in a month. Otherwise it can lead to burnout and loss of interest!
#Devruary As an [AS]-autistic game dev, my fixation on the content itself never wanes, so burnout comes from repeated failures. I usually cope by making an offshoot of it (art, video, or blog post) to remind me that I can see something through.
#Devruary Worst bug I have to deal with is an annoyingly common one: misplaced visual elements. It can persist even if the code for it produces no errors. I then have to figure out what to add to fix it without throwing off the existing non-error code.
#Devruary As a Ren'Py dev, the two things that could always break my games are (1) building a new feature incorrectly and (2) messing with the "screens" file too much!
I have since adopted a new game making rule: if it ain't broke, don't try to fix it.
#Devruary Biggest two dev mistakes I remember making so far are (1) not backing up my games when switching computers and (2) not testing my games in a browser before uploading them as web builds. Thank goodness I've broken these habits!!

















