Good at programming in Visual Basic?

[Dr Brain]

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.

[Rifleman]

what I would do for the above situation is just jump back and forth between hill spots because thats actually how I made mg-style ctf

 

modinfo...? Are you using it on an ASSS server?

<{POST_SNAPBACK}>

 

That sounds like a good solution... Should`ve thought of that

 

 

As for custom alert commands, we use subgame.

 

Server.ini :

AlertCommand=Cheater,Help,Illegal,Host,Advert,die

 

Rifleman>?die All of you!

Die: (Rifleman) (Public 0): All of you!

Message has been sent to online moderators

 

-Rifle

[★ Maverick]

! (eek!)

 

It could give it a nice advantage over mervbot when it comes to conserving bandwidth/avoiding packet flooding when multiple bots are hosted by one person.

That I believe the most. Mervbot has problems when its hosting about 5 bots by the same external host (Catid himself speaks of a 3 max). Where as TW Core doesn't have problems because of the number of bots' date=' but has other problems.

 

Conclusion: If you want stability' date=' 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.[/quote']

The big conclusion of this whole story

[★ D1st0rt]

What I'm trying to say is that the TWCore development group is being restructured, so there WILL be new releases. When, however I don't know.