Computers should catch fire!
Started by Kingdaro, Feb 11 2013 06:05 AM
31 replies to this topic
#21
Posted 12 February 2013 - 09:43 AM
I very much like the current too-long-without-yielding behavior, as it does not affect other running processes on that computer.
#22
Posted 12 February 2013 - 01:29 PM
I like a config option for the computer exploding on any error.
Attempt to concatenate string and integer? Screw it, just set off a nuke instead!
Attempt to concatenate string and integer? Screw it, just set off a nuke instead!
#23
Posted 12 February 2013 - 01:33 PM
A config option would be pretty cool. Maybe not for exploding, but still.
#24
Posted 12 February 2013 - 01:40 PM
I want a computer to blow up a noobs house. There better be a config for this because of CCU......
#25
Posted 12 February 2013 - 03:15 PM
TheOriginalBIT, on 12 February 2013 - 04:32 AM, said:
But when a real computer over heats it just turns it off... try it, get your CPU to about ~90 degrees Celsius and see what it does, i bet there will be no BSOD... thats why i think RROD would be better 
#26
#27
Posted 12 February 2013 - 03:58 PM
i play at 95-103 bro.
#28
Posted 12 February 2013 - 08:18 PM
I play at 153, PixelToast.
And this would make a nice April Fools joke.
And this would make a nice April Fools joke.
#29
Posted 12 February 2013 - 10:50 PM
Only if it was purely graphical, if it spawned an actual fire block capable of burning a bunch of houses (orchards, farms, whathaveyou) down, it would fall into the not-so-nice category of joke.
#30
Posted 12 February 2013 - 11:39 PM
As I said - nah.
#32
Posted 13 February 2013 - 02:24 AM
ChunLing, on 12 February 2013 - 10:50 PM, said:
Only if it was purely graphical, if it spawned an actual fire block capable of burning a bunch of houses (orchards, farms, whathaveyou) down, it would fall into the not-so-nice category of joke.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users











