Author Topic: One million bricks.  (Read 2369 times)

Hmm... i reached 300k a day without problem, saved it but loaded 276K only lol
« Last Edit: June 06, 2012, 11:01:02 AM by Sylvanor »

yes but you said it would "crash" at over that limit. Clearly it doesn't
You didn't ghost more, so you didn't crash
Clearly

Edit: It's about 256k, not exactly so you can have a few more
« Last Edit: June 06, 2012, 11:05:54 AM by Treynolds416 »

if bricks were money.....

this is about bricks not IP's

  • start dedicated server
  • for loop with range 999999
  • inner contained for loop with range 999999
  • create brick inside previously mentioned loop
  • suddenly huge lag until crash
Fixed

Fixed

it wouldn't lag
it's a dedicated server, lol

just remember not to join it

just remember not to join it
What's the sense then


  • start dedicated server
  • for loop with range 999999
  • inner contained for loop with range 999999
  • create brick inside previously mentioned loop
  • suddenly 999998000001 bricks
That would probably crash the dedicated because Torque likes to execute code as fast as possible, and this is a for loop. Historically, for loops don't play nice with huge numbers.

That would probably crash the dedicated because Torque likes to execute code as fast as possible, and this is a for loop. Historically, for loops don't play nice with huge numbers.

Ticks

Torque likes to execute code as fast as possible

no stuff

this is a for loop

no stuff

Historically, for loops don't play nice with huge numbers.

that's why the loops are integrated

That would probably crash the dedicated because Torque likes to execute code as fast as possible, and this is a for loop. Historically, for loops don't play nice with huge numbers.
No, it will just freeze til it's done

My IP is 127.0.0.1, hack me!