Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Randomized Backstories

67 (25.9%)

Genetic Additions

98 (37.8%)

Mess Hall

50 (19.3%)

Revamped Area

44 (17%)

Total Members Voted: 257

[Thrain]

Connecting to byond://70.79.213.220:1522...failed

is it only me having this problem?

if its down why does it say its up?

[zchris13]

the server is down BRO.

EDIT: ▼WHO CARES RELAX BRO

[Thrain]

server still down?

[Dr. Johbson]

It is, Im surprised it crashed. Ill bring it up back up right now.

[Thrain]

can some one post a updated picture of the station?

[Farce]

Hrm.  I would like to try this, but it intimidates me slightly.

[Dr. Johbson]

Hrm.  I would like to try this, but it intimidates me slightly.

Don't let it, its really a fun game thats easy to get into. Very little drama nowadays too.

can some one post a updated picture of the station?

Ill try to find out how.

[beorn080]

REally, its far more user friendly then DF, though perhaps the same amount as lethal. Just try to remember not to run through any random airlock. That's a good way to get spaced.

[zchris13]

And the lag. Count your button presses.

[woose1]

I live like right next to Johbson, so I don't get any lag at all.
...
*Sticks out tongue*

[zchris13]

The game itself is lag.  It is composed of lag, written in C lag+.  Playing it is selling your very soul to the lag.

[immibis]

The game itself is lag.  It is composed of lag, written in C lag+.  Playing it is selling your very soul to the lag.

It's written in BYOND.

[head]

The game itself is lag.  It is composed of lag, written in C lag+.  Playing it is selling your very soul to the lag.

It's written in BYOND.

Incorrect its written in DM.

[Apple Master]

The game itself is lag.  It is composed of lag, written in C lag+.  Playing it is selling your very soul to the lag.

It's written in LAG

Incorrect its written in LAG.

fixd.
DM as a code is quite slow, so there's always some lag due to processing, I think.

[qwertyuiopas]

It's written in LagScript. All the fun of Lag++, but with the additional overhead of being a script language and running on an interpreter.

(What follows is only theory)

My theory on it: I believe that the game runs an update every tenth of a second. sleep() delays the code by the specified number of updates. 0 just puts it at the end of the list of things to do, or maybe puts it right after the current code.

The engine does networking at the end of each update, so if the code cannot fully complete within one tenth of a second, there will be lag.

So, if that is correct, breaking up a long loop with a sleep(1) in it, like I did for the power propagation, gives the engine time to update everyone on what has happened.

Other code that could be improved in this way:
Solar power updates
Airflow (spread it out among 5 updates?)

Though in both situations, the consequences should be considered first. Maybe an airflow tick for each Z-level?