« Quarterly Goals | Main | Cool Unity resources »

October 09, 2013

Comments

Happionlabs

After writing this, it occurs to me there is a way to "lock" those inspector values - at least for your own classes. Move the values back out of the prefab and into the defaults for your script and make them private. I might well want to do this for my character's movement parameters...

Chris Chapman

For locking things down: I found text scene files and extensive use of prefabs pretty good for spotting rogue / accidental changes. I.e. partitioning off bits of content you know are fine by making them prefabs, and maybe also leaving copies of them in a separate scene (or ideally referencing the content direct from that scene). If you then open up that scene later and it needs resaved, you can go look at it in source control and see if the changes made (maybe because a prefab was changed elsewhere) are all expected. Often I saw accidental restructurings, parameter changes that were leading to trailing / dead references, etc., that would manifest themselves as badness in the live build.

The comments to this entry are closed.

The Games

  • Energy Hook
    3D grappling-and-swinging-and-running-on-walls-and-doing-tricks ... with a jetpack ... for style!

Jamie's Bragging Rights

  • Spider-Man 2
    The best superhero games of all time Game Informer
    Top five games of all time Yahtzee Croshaw
    Top five superhero games of all time MSNBC
    Top 100 PS2 games of all time Official Playstation 2 Magazine
    1001 Games You Must Play Before You Die Nomination for Excellence in Gameplay Engineering Academy of Interactive Arts & Sciences
  • Schizoid
    Penny Arcade PAX 10 Award
    Nominated for XBLA Best Original Game
    Nominated for XBLA Best Co-Op Game