How to crash a map! From bad ideas to short-sightedness
-outputting a floor button to push itself inwards, resulting in an infinite output overload.
-accidentally parenting two objects to each other as being both parents, breaking any notion of hierarchy.
-making cubes spawn where a previous has fizzled, thereby making infinite cubes fizzle and overloading the map.
-creating a scene where a cube is both killed and fizzled simultaneously, confusing the system on what to do.
-flooding a water area with physboxes and overloading both the friction interaction and splash particles.
I crashed maps/games by:
- Bad programming.
- In Portal 1, killing a soundscape.
- Just playing Portal 2 for me.
point_servercommand
command
crash
okay, here's one; Using improper textures/sprites for dynamic entities such as an env_laser with a non-sprite material
Trying to create a gelocity like map without knowing that the info_paint_sprayer's radius can change.
Also, most important. Area portal leaks.
Chilius03 wrote:
Pressing R with no portalgun.
To what command do you have R bound?
Spent a few hours with LoneWolf playing murder mystery, trying to figure out what was randomly crashing our level
Lpfreaky90 wrote:
Corrupt displacements!
Spent a few hours with LoneWolf playing murder mystery, trying to figure out what was randomly crashing our level
Oh yes, and non-quadrilateral displacements.