PickyBurrito49,
@PickyBurrito49@mastodon.gamedev.place avatar

The best advice @Cyzaine ever game me was to put print statements everywhere. Some times I get lucky and the 1st one shows me the issue. Today it was 3rd times the charm!

rokojori,

@PickyBurrito49 @Cyzaine Still doing them a lot ^^ Best combined with ifdef'ed logging that can be removed in releases ^^

hodgepodge_homonculus,

@PickyBurrito49 @Cyzaine it can be helpful to write a Logger class that takes in an integer log level with eat print. Then you can change the global log level to get tons of logs everywhere or just the ones you want firing on production, and you don't have to uncomment/add them back in everywhere when debugging (although I still add logs for debugging anyways for stuff I don't want to leave in)

PickyBurrito49,
@PickyBurrito49@mastodon.gamedev.place avatar

@hodgepodge_homonculus @Cyzaine I believe we have something like that for help troubleshooting gereneral game crashes etc. These were to help me identify why I was getting some odd behavior when pulling objects toward the player (line 90 was the fix), and I was trying to cipher where the issue was happening. But I do still have loads to learn about debugging and troubleshooting so I'll look into your suggestion, thank you!

Cyzaine,
Cyzaine avatar

@PickyBurrito49 One of these days I'll teach you how to use the debugger right to lol

PickyBurrito49,
@PickyBurrito49@mastodon.gamedev.place avatar

@Cyzaine let's not get far ahead of ourselves!

  • All
  • Subscribed
  • Moderated
  • Favorites
  • godot
  • DreamBathrooms
  • cisconetworking
  • mdbf
  • everett
  • Youngstown
  • rosin
  • slotface
  • love
  • khanakhh
  • kavyap
  • ngwrru68w68
  • ethstaker
  • thenastyranch
  • magazineikmin
  • provamag3
  • modclub
  • cubers
  • InstantRegret
  • osvaldo12
  • Durango
  • GTA5RPClips
  • tester
  • normalnudes
  • Leos
  • tacticalgear
  • anitta
  • megavids
  • JUstTest
  • All magazines