Give all the examples that could crash SC. or as many as you know
Why? There are tutorials, text files, threads all over about this. Plus this isn't the forum for this kind of discussion. Moved to Games.
Scrolling over a disabled CC....And there's a whole load of way's...Im just to lazy to type all of them.
scrolling on any disabled unit
QUOTE(Illusion @ Feb 14 2005, 12:25 PM)
scrolling on any disabled unit
[right][snapback]145109[/snapback][/right]
There are a lot of disabled units that you can see without crashing.
Looking at the white dot (Spirite).
Looking at anything that will crash SC.
?Looking at a building that was stacked partially outside the map view? (I think)
Sending a character (Like a letter) that Starcraft does not support.
Here's my list:
Doing anything that crashes SC will crash SC.
Putting a unit only partially on the map, there are plently of ways mentioned on the site for anti-hacker triggers though so just get some off there.
QUOTE
?Looking at a building that was stacked partially outside the map view? (I think)
Looking isn't required, having it there is enough.
Humm... Here is all I think about:
Looking At a Unused Command Center,
Looking at a disiabled Turret,
Looking at the sprite 17,
Creating a unit in the Null terran,
Killing a probe (Or anything that can hold stuff) holding a hallucinated powerup,
I think this is all I could think about right know. I think 1 Is enought since you can't crash Sc a couple of times in a row...
if you really wanted to i think theres is about 50 different ways to kill starcraft.... all of the above mentoned plus more... it really not that hard
By the way why would you want to know?
• Some sprites are incomplete or are missing certain frames, and may crash you. Some are just gay and crash you anyway.
• Tank/Goliath turrets crash instantly when independantly placed.
• Incomplete units such as the Independant Command Center will crash.
• Using the Set Doodad State trigger on units that have incomplete sections of Iscript.bin will crash.
• Loading from non-existant strings.
• Displaying a wireframe that doesn't exist.
• Using an extended player and/or unit that stretches beyond what players/units were designed to read.
• Using illegal map dimensions and/or scrolling too far off the edge of the map.
• Trying to order units that don't exist on the map, or have moved off the specified map dimensions.
• Placing units off of the map.
• Using illegal order commands.
• Using certain sprite-units like the map revealer, that generates it as a physical unit..
• Doing any load+repair glitches.
• Doing the hallucinated powerup glitch, not creating units after, and killing the peon holding the powerup.
• Doing the hallucinated powerup glitch, and picking up a one-frame unit(buildings), and turning around with your peon.
• Doing the hallucinated powerup glitch and attacking with a unit that does not have an attack animation.
• Trying to execute non-existant Briefing Actions, Trigger Conditions, and/or Trigger Actions.
• Overloading the engine with 1700+ units stacked and using some type of spell on all of them, all at the same time.
Bah, if I wasn't so tired right now I could probably think up more.
Disabling units that cant be disabled
The only ways I am able to crash starcraft so far are:
1. Using black sheep wall in HBC
2. Using black sheep wall in Particle Man Bound
3 All in the above posts.