You've been told wrong. These bugs have nothing to do with mombot. This bug is entirely about the way TWGS and Tradewars handles the data on exit. Mombot can't cause missing prompts, locked up nodes, or data corruption.

Bugs go undiscovered and unreported for years even in big commercial projects with thousands of users. I deal with this every day at work. People have different expectations and different ideas. It may be that you have some unique ideas about how to fuzz the software.



Now that JP has time to fix them, maybe you could report the details on all of them. Detailed bug reports with steps to reproduce are how users gain cred in both the open-source and commercial software worlds. Dangling hints, not so much. Programmers don't have time for that.

how did this go from mapping programs and tools to beta testing trade wars?

This is how......

If you've seen them occur, then you know more than you've told us. And if you haven't seen them occur, then you're just peddling rumors.

I have seen all of them occur except for one of them which Locutis witnessed on re-entry. I don't know what caused the problems, or why they occurred. I've posted when they occur and why I thought it might have happened, but it's all speculatory. I can't see the code, so I have no clue why these things are happening. Most of them are related to re-entry. The ship cap bug was witnessed by several players in HHT, and the disconnect bug was also witnessed in HHT. Ask around maybe someone else can make a better guess as to why these things happened. I'm done with this thread, so either figure it out yourself or leave the bugs in the game, I really don't care. I especially like the one where KB crew capped several of our ships and one of them magically re-appears with full figs on it. LAFF I might have to figure out what causes that one.

And you're using TBH's Mombot that was written for v1. TBH hasn't upgraded it for v2. Xanox has upgraded the bot we use, and I don't have any problem playing v1 or v2 games.

You don't need to see the code or know the exact cause of something to write a good bug report. You can write steps to reproduce. If it's not deliberately reproducible, you can at least say what you were doing when it happened. If you actually wanted to be useful, you'd offer us something like, "If a player warps into a sector while another player is relogging to clear mines, one of the players will be kicked off." (Or whatever the problem might be.) Just saying, "Three new bugs associated with exit/re-entry into the game" is completely useless.

Believe me when I tell you this. These bugs absolutely CAN NOT be caused by mombot. ROFL. Ships with the same name don't reappear in the same sector with full figs after that are capped. Missing prompts and games that completely lock up forcing a hard disconnects on exit isn't caused by a script of any kind. TWGS node lock ups are NOT caused by mombot. Players able to get unlimited time in a time limit game is not caused by a script. Multiple players getting knocked offline at the same time isn't script related.
These are bugs in TWGS and/or Tradewars version 2, plain and simple.

Here's an idea to ponder... there are scripts specifically written for v1's lack of delay. i.e. burst macros that fully execute in the same ms (or dang near.)

So, trying to use those scripts in v2, which now has a fixed minimum delay (regardless of sysop settings), I would think all manor of silliness (bugs) may be happening.

Another way to look at this.. v2 can process X transactions, when you use a v1 script to send 10X transactions, things are bound to break. This is why I think the problem exists with the scripts more than the game. JP has made it abundantly clear that a fixed minimum delay is necessary to the integrity of the game data, and the reason why with faster computing capabilities that v1 games files became corrupt easily.

That would still make it a bug in the game, just one that happens to be triggered by scripts. A program is responsible for maintaining the integrity of its data, and it should not be possible for anything external to corrupt it (short of hardware failure).

i just posted a message.. if anyone knows of a place i can easily set it up

I just have mine on an old machine I'm not using any more. I use dyndns.org for the "static" IP.

i found a place to host it online for free using a windows server with remote desktop access...

Nothing is truly free... I wonder what the "cost" is?