About BYOND 340

ID:135483
 
Jul 22 2004, 2:01 pm
I just read the post about BYOND .340, and does that include the part where it freezes and then no one can log on anymore?
Jul 22 2004, 2:34 pm
Metroid wrote:
I just read the post about BYOND .340, and does that include the part where it freezes and then no one can log on anymore?

No, they fixed BYOND problems, not poorly-coded game problems.
Jul 22 2004, 2:38 pm
In response to Teh Governator
Teh Governator wrote:
Metroid wrote:
I just read the post about BYOND .340, and does that include the part where it freezes and then no one can log on anymore?

No, they fixed BYOND problems, not poorly-coded game problems.

Actually, it was a BYOND problem; games could be frozen and create such an effect.
Jul 22 2004, 2:41 pm
In response to Malver
Malver wrote:
Teh Governator wrote:
Metroid wrote:
I just read the post about BYOND .340, and does that include the part where it freezes and then no one can log on anymore?

No, they fixed BYOND problems, not poorly-coded game problems.

Actually, it was a BYOND problem; games could be frozen and create such an effect.

Yeah, but poorly coded games can be frozen and create such an effect too. :P
Jul 22 2004, 4:41 pm
In response to Foomer
Who said its a poorly coded problem? It seems to happen only after like 10 hours of DD being up which makes no sense why would it just suddenly start? I get no runtimes...
Jul 22 2004, 4:42 pm
In response to Metroid
I've had a very large game run for 3+ days straight before, and I didn't have any problems.
Jul 22 2004, 4:46 pm
In response to Teh Governator
FlashChat has been running for about 10 days without a restart, so :P.
Jul 22 2004, 5:23 pm
In response to Scoobert
But that doesnt always mean I have bad coding. It could be anything. Its always assumed instantly when theres a problem that my coding must be the worst ever and it must suck and I cant be a good coder if that happens, its not always the problem.
Jul 22 2004, 8:21 pm
In response to Metroid
Just because its caused by bad code doesn't mean the coder sucks. Bugs happen, its just a part of programming. Sometimes those bugs happen to freeze things up, such as an infinite loop that got put in there by accident. When you've got a big program, unexpected things can happen that result in a frosty outcome.

Unless of course you're basing you're entire "Its always assumed instantly when theres a problem that my coding must be the worst ever and it must suck" argument on what Teh Governator said. But who cares what he says anyway.