Dr Brain

SubSpace? We don't use SubSpace. We use Continuum, as you are so fond of pointing out all the time. You're the one making it easy by using my name. If my zone is so bad, why are you copying it? They say imitation is the highest form of praise.

I'm glad you're taking the name anyway. If the zone is any good, I get to take all of the credit. If it's bad, I get to deny any relationship with it. EDIT: WAIT! Q2 '06? It's gonna take you more than a year to finish? LOL. Hyperspace, as it is, took about 4 months of work. Half of that was duplication of effort when we changed platforms.

Yah, HS is closed for the moment. It wasn't closed before. Hence, HS isn't what it used to be.

I was having issues with the position packet stuff. I believe all hyperspace mods who were around at the time recall what it did to the zone. The bots would lock up periodicly, depending on how many outgoing packets they would send. About every 6-10 hours, the hub bot itself would up and die. We worked around this by keeping 2 backups of each bot, for a total of 7 bots online at once. When one would die, you just kill it, bring in the next one, and go back to waiting for it to die (about every 10 mins at peak times). Note that the hub bot itself would die. This means that nothing we were doing in the spawn bots was causing the issues that we were having. The core itself was faulty. Yes, in all likelyhood, we turned on a buggy feature (spec hopping for position packets, to be precise), but the core itself had the bug. We lived with this for 4 months. Then I got tired of bugging the totally useless TWCore bot team about it, and moved to ASSS. Now, don't misunderstand me, ASSS is even more buggy than TWCore, but at least progress can be made. I've found Grelminar quite helpful in debugging Hyperspace issues. We, for one brief moment, had a quite reliable system going on under ASSS. Conclusion: If you want stability, stick with Merv. If you want untracable bugs that will never be fixed in the next release (because there will be no next release) and MySQL integration, go with TWCore. If you want to go insane tracking down numerous quite fixable bugs in a friendly dev envorment, go with ASSS.

I'm not bored enough to write a long reply to this, but I do have enough time to write this: 1. Good luck, you'll need it. 2. I think you're lying. You told me 1 month ago exactly what you said here. That's some fairily amazing progress being made! Also, at the time, you refused to divulge any details. This leads me to the conclusion that you're a liar. 3. "On a far superior engine" meaning Infantry, I'm sure. EDIT: It's Hyperspace, not HyperSpace.

It was when I was editing your post in the text area. I selected all of the newlines and pressed backspace. Next time around, I copied it into a text editor, and did the modifications, then copied it back.

Fixed. Killed my browser once doing it, though.

That wasn't the issue. It wasn't anything we were doing. The hub bot itself was experiencing the same issues.

TWCore killed Hyperspace a year ago. I doubt the problem we had was ever fixed, because, to the best of my knowledge, we were using the same revision that is currently out there. Beware.

WTF is gashi?

I think I will never ever trust code from you.

sexchange aka atadictomy. (sound it out)

belly button lint

That'll be on page 1045.

out

137 was like 41 pages ago.

Astarael, the Sorrowful. The banisher, the final bell. Properly rung, it casts everyone who hears it far into Death. Everyone, including the ringer.

1337 $$

1336

Let me be the first to say that it stopped something like three weeks ago. You bumped a dead topic and told it to STFU. Yes, that *does* make you look intelligent.

No, I've never heard of the edit button.

Yes, I know I tripple posted. Well, quadruple with this one.

As a side note, post 1337 will be on this page.

New page magic!

Old page magic!