Seaxouri
01-06-2006, 02:11 AM
Hello, and welcome to the world of MySEQ! For those that do not know what MySEQ is, here is a little introduction.
In a Nutshell
MySEQ is a program that runs on Windows 2000/XP alongside of the popular game called Everquest, which is owned and operated by Sony. The program allows a player to view a map of the entire zone they are currently in, along with all the spawns (mobs, players, objects, etc) that are currently in that zone. As of the LoY expansion, there is already an in-game map (for most zones), however, there is no spawn information displayed.
Warning
If you decide to use MySEQ, please be forewarned that you run the risk of having your account banned. It is considered an illegal tool to use that violates the agreement between you and Sony regarding third party programs. If you do not want to risk having your account banned, then we suggest you not use this program.
Running the Risk
If you decide you want to run the risk of trying out MySEQ, then we offer the following suggestions:
Never mention the terms MySEQ, SEQ or ShowEQ while in the game. Not in private tells, channels, /ooc, or anything else. If you do, and someone reports you, you could be in trouble.
Never mention any of the above terms on any official Sony/EQ website where your username can be traced back to your account.
Never brag or even hint that you are running it.
Do not be too obvious. If you are waiting for a spawn to pop for three hours, and when it finally pops on the other side of a zone, don't get up and make a bee-line for the spawn. If you have a tracking skilled character, wait a minute or so, then wander in the general direction of the spawn until tracking locks in, and use tracking to hone in on the mob.
Do not shout out things that make it obvious you are using MySEQ. For example, if you are on one end of a zone, and a rare spawn pops on the other side of the zone, don't /shout to the zone that the mob is up. If you can pull it up on track, or see the mob directly, then it is probably okay.
Be nervous. Be cautious.
Never admit you are using MySEQ. If you do not want to lie, then just abstain from answering.
It is very easy to Sony to detect that you are running MySEQ. The problem is that it borders on a trust/legality issues. I do not know if it is illegal for Sony to scan the processes on your machine and report that information back to their databases. It would certainly seem like a privacy violation, but I am not a lawyer. From a programming standpoint, it is *very* easy to do. So if you are wondering "Can they detect that I am running the MySEQ server?", I am telling you right here and now, they CAN. Whether or not they can LEGALLY, I do not know. Whether or not they DO, I am not sure, although there is evidence to suggest that (at least at one time), they did.
The Program
The program consists primarily of two separate halves. One half is called the server, and the other half is called the client. The server must run on the same computer that Everquest is running on. The client has the option of running on the same computer, or a different computer. If the client is running on a different computer, than THAT computer must be running Windows 2000/XP and it must be on the same network as the first computer.
I will try and get some screenshots posted, but until then, here is basic description of each:
Server: A console application. Looks similiar to running Start->Run and entering 'cmd' and pressing Enter. There is no GUI (graphical user interface), and as such you cannot interface directly with the server. The server requires proper settings which are located a file called myseqserver.ini. These values are commonly referred to as 'offsets'. If the offsets are incorrect, the tool will have problems showing you information, or may not work at all. Usually after a patch, the offsets change, and you will need to re-visit these forums to obtain the new offset information. Once you obtain the new offsets, simply edit the myseqserver.ini file in any text editor (like notepad), make the changes, and save the file. On occasion, we may just post the whole file as an attachment, in which case you could download it and replace the old one with the new one. This INI/offsets file is located in the same directory that the server is in.
Client: A graphical application. The client is a Windows-type application with menus, buttons, mouse pointer and all that good stuff. It's main window is a large map of the zone you are currently in, with little colored dots representing each spawn in the zone. By moving you mouse over each dot, you can see detailed information about each spawn. As the spawns move around the zone, you can see their movement. There are lots of nice features that allow you to see or monitor information about the spawns, such as:
Spawnlist - this is a table like display of all spawns in the zone and their information. At a glance you can see all the information at once, if you desire. There is information on each spawn, like race, level, name, etc., each in it's own column. You can sort the spawnlist on any of the column headings.
Alerts - if you are hunting a particular spawn, you can add it to the 'alert' file. Doing so will apply special effects to that spawn, if it should appear in the current spawnlist. The dot on the map may be highlighted with a flashing circle, and the entry in the spawnlist will be moved to the top of the list and prefixed with a special character. There are different alert levels, like Hunt, Caution or Rare, each will apply slightly different effects. You may also apply sound alerts.
Depth Filter - in some zones, the passageways overlap each other in many places. So much in fact, that if you are looking at a map of the zone, all the passageways muck together to make the map look like a big mess. Depth Filtering allows one to highlight only the map lines (and spawns) that are closer to the player, while filtering out the ones that are farther from the player. A recent addition to the client, called Dynamic Alpha, is a much more powerful depth filter. The normal depth filter only relies on the Z-axis values, whereas Dynamic Alpha uses a true 3D 'sphere' around the player.
Radar - A small, radar-like, floating window that displays your position vs. other mobs in the vicinity.
Spawn Timers - some spawns will repop at nearly fixed time intervals and at the same location. If this type of spawn is detected, the client will mark the location and will keep track of when the next spawn is expected to occur. The spawn timer mark will blink yellow and then red as the expected 'repop' time approaches.
Mob Trails - this option is very cpu/memory intensive, and it is not recommended that it be used normally. However, if you are experiencing a new zone, and you want to see where the safe 'camp' areas are, you can enable collection of mob trails. Everywhere an NPC spawn moves to will leave a dot behind on the map. After awhile, the 'roaming' areas will start to fill in with these dots. The areas with no dots are likely candidates for safe camps.
There are no 'offsets' that you need to worry about with the client. All your preferences are saved in a special file for you, and loaded the next time you start the client. The only real thing you need to set in the client, is the IP address of the server (located under Options->General). To determine that, on the machine that runs the server, run Start->Run and enter "cmd /k ipconfig". You should see an entry called "IP Address" that looks something like "192.123.0.100", "10.10.0.5" or something of that nature. Use this value, including the dots, inside the client. The IP Address is basically like a phone number. You are telling the client "Hey, this is the server's phone number, go call him". The client will call and connect to the server, and the two start communicating with each other. If you tell the client the wrong number, he can never get through to the server.
MQConsole
You will see inside MySEQ is one window with MQConsole in it. This is the Macro Quest stuff. Macro Quest is a separate tool that is used to actually simulate keypresses, as if the user actually performed certain actions manually. I do not use MQConsole, nor am I familiar with it. From what I understand, it actually writes into the Everquest process, changing memory values. This is very dangerous because it can easily be detected by Sony, and if you are caught doing this, you will most likely get your account banned. MySEQ NEVER WRITES to the Everquest process! We ONLY read from the process, much like an anti-virus program would scan a process looking for viral signatures. Using MySEQ will not change your gameplay at all, and by that I mean, you won't run faster or be able to knit a thousand sweaters a minute. However, using MQConsole allows you to do things like this, but at a much greater risk. Most people that I read about getting caught, get caught using tools like MQConsole. My suggestion is to avoid it completely.
Updates
If MySEQ stops working, please visit the forums here and look for new posts regarding new offsets. They should be located here in the HELP forums.
From time to time, you may want to visit us to look for new updates to the client and/or server. These updates may provide performance enhancements or new features. Always keep your old client and server just in case something goes wrong.
Forums
We welcome you to participate in the forums. Provide feedback, help with finding offsets, spread the word. We would like people to know that there is an open source alternative, that will always remain free. If this project dies, then I can almost promise you you will eventually need to pay to use the commercial version.
Donations
Personally I do not want any donations. If you want to donate, give your money to those people who are paying for these websites. Donate to sourceforge.net or showeq.net.
Also, you will never see me posting "How much do you love me?" polls. That just makes me sick to my stomach. The best way you can thank me is by spreading the word. Tell your friends, tell your guildmates (just not in game).
MySEQ vs. ShowEQ
ShowEQ, also known as SEQ, is the original tool that was created way back before the in-game maps existed. SEQ differs from MySEQ in a few ways:
It runs on Linux, not Windows
There is no 'server'. It sniffs network traffic and decodes information being passed along to the machine that is running Everquest.
It is 100% undetectable
It shows a lot more information about spawns
Being a Linux tool, you generally need to build it yourself unless someone makes a binary release
Other than that, it provides similiar features that MySEQ does (ie: map with spawn information).
A Little History
MySEQ, a spinoff of SEQ, was originated by programmer CaveManBob and then taken up by SlartiBartFast.
http://www.geocities.com/slartibartfast1232000/index.html
It was added to sourceforge.net as a subproject under the SEQ project (SEQ admin is Ratt) in April 2003. Because SEQ was under the GNU Public License (GPL), and MySEQ was a subproject of SEQ, it fell under the same GPL license that SEQ did. Under GPL, anyone that changes the source code, and makes public those changes in a binary release, is bound by copyright laws to provide the changes to the source code if so asked by anyone (or at least provide a means to which the changes can be obtained). They may charge a 'modest' fee, to compensate for the cost of distributing the code. They may NOT add additional licenses to the product, nor charge any royalties for use of a GPL product. Anyone that obtains the GPL product can copy it and re-distribute it to anyone else free of charge.
In February 2004, MQSEQ2 (thats someone's username), posted this message:
http://www.showeq.net/forums/showthread.php?t=4670
Which basically stated that they had decided to 'move the forums' to a different website. MQSEQ2, xeerex, Mr Doh, magictiger and maybe a few others are the main folks who then became the primary developers of what I refer to as 'version two' or v2. To their credit, they invested a lot of personal time and money into continuing development of MySEQ, adding features, finding offsets, and basically making the tool a much more powerful one. They managed their forums continually. They added neat things like a Windows installer and an offset auto-updater. In the beginning, they would ship the source code with the binary releases, and everyone was basically happy. Users drifted away from these forums into the 'new' forums. I am unsure how much of the v2 code changes got checked back into the sourceforge.net CVS repository, but it was not all of it. Releases were no longer posted on sourceforge.net, but on the 'new' website.
In March 2004, I made my first request for a source tarball, because the source being shipped with the releases did not seem to jive with the release. There were missing files. I was told it would be fixed in upcoming releases. It never was. This was also around the time I first learned of MySEQ.
In August 2004, the v2 folks stopped shipping source with their binaries, because it was a waste of bandwidth. I agree 100%.
In December 2004, I posted a bug on the v2 forums and was told that there would probably not be any changes made to v2 because of certain 'issues'. The 'issues' seemed to be related to money. Somewhere in 2004, the v2 folks started accepting donations for use of the tool. This is perfectly fine, because until then they had been footing the bill for the website, and been donating their own personal time and money to the effort. Rumors arose, from where I do not know, that v2 was going to a subscription based plan, where you would have to pay a monthly fee to use MySEQ2. This sent the orginators into a frenzy. There was a demand for the v2 folks to surrender source code changes, stating that the original code was under GPL. The v2 folks claimed that there was no GPL clause in the source code itself, and that it was therefore not under GPL. There was also claims that the v2 folks had re-written so much of it, that in essence the original code was all replaced.
I do not know how much of this is fact, nor what is embellished. All I know is that as a result of this, a few things happened:
v2 did not go to a monthly based subscription plan
v2 never had any more updates (v2.1.3.0 was the last, iirc)
the originators spent a bit of effort trying to breathe life back into the v1 MySEQ line, which succeeded, but went mostly unnoticed by the masses
some of the updates that the v2 folks made went into v1
v2 folks created a 'donators family' group on their forums. If you donated, even the tiniest amount, you were tagged as a donator and offered access to special areas of their forums. In these areas, you would get first crack at new offsets if they changed. The offsets were made 'public' roughly two weeks later
v1 folks made a tool that could read the v2 offsets from the v2 website and reverse engineer them to work with v1
the number of v2 donators increased a lot
In October 2005, around the time of the DoD expansion pack release, support for v2 was removed. Donators could obtain a v3 beta from the special forums, but the public could not access it. It was at this time I decided to become involved with v1.
In November 2005, an EQ patch came along that broke all versions of MySEQ. MySEQ v1 was up and running in 2 days. v3 would not function until January 2006. I offered to help the v3 folks get their stuff running, but was refused. I posted on the v2 forums that I had a working version, but my posts were deleted within 15 minutes. Most of the v2/v3 community suffered for over a month without MySEQ, and my efforts to spread the word of a working alternative were thwarted at every turn. Day after day I would read post after post of people saying 'when can I use MySEQ again?' and I was powerless to help them (enter violins).
In January 2006, I read a message on the v3 forums that they will release a public version of the v3 beta in the near future.
http://www.rexpage.com/myseq/forum/forum_posts.asp?TID=2937
Please note that the person claiming there will be a 'public' release was Blaksmith, a forum moderator, but not one of the primary folks (like Mr. Doh or magictiger).
Note: For anyone who searches the v2/3 forums, they may find a post where it seems I flip flopped on my viewpoint. At that point in time, I did not know that the MySEQ project was originally a subproject of SEQ, and SEQ was clearly labeled as a GPL project. After much investigation, I have actually reversed my opinion more in favor of the CaveManBob/open source community side.. but that it me. My personal opinion is that there would be no MySEQ if it were not for CMB, and therefore any derivative of his work should fall under the license it was originally under. Since the v2 folks admitted that they got their original source code from sourceforge.net (the reason they moved to a new site was that SF was too slow, remember?), that *in and of itself* proves beyond any doubt that the source code was GPL. Now if the v2 folks can offer proof that the code was given directly to them by CMB and not under GPL, then I would reverse my opinion. Of course my opinion is worth nothing, but if someone did come across my flip-flop post, I wanted to explain why I flip flopped.
In a Nutshell
MySEQ is a program that runs on Windows 2000/XP alongside of the popular game called Everquest, which is owned and operated by Sony. The program allows a player to view a map of the entire zone they are currently in, along with all the spawns (mobs, players, objects, etc) that are currently in that zone. As of the LoY expansion, there is already an in-game map (for most zones), however, there is no spawn information displayed.
Warning
If you decide to use MySEQ, please be forewarned that you run the risk of having your account banned. It is considered an illegal tool to use that violates the agreement between you and Sony regarding third party programs. If you do not want to risk having your account banned, then we suggest you not use this program.
Running the Risk
If you decide you want to run the risk of trying out MySEQ, then we offer the following suggestions:
Never mention the terms MySEQ, SEQ or ShowEQ while in the game. Not in private tells, channels, /ooc, or anything else. If you do, and someone reports you, you could be in trouble.
Never mention any of the above terms on any official Sony/EQ website where your username can be traced back to your account.
Never brag or even hint that you are running it.
Do not be too obvious. If you are waiting for a spawn to pop for three hours, and when it finally pops on the other side of a zone, don't get up and make a bee-line for the spawn. If you have a tracking skilled character, wait a minute or so, then wander in the general direction of the spawn until tracking locks in, and use tracking to hone in on the mob.
Do not shout out things that make it obvious you are using MySEQ. For example, if you are on one end of a zone, and a rare spawn pops on the other side of the zone, don't /shout to the zone that the mob is up. If you can pull it up on track, or see the mob directly, then it is probably okay.
Be nervous. Be cautious.
Never admit you are using MySEQ. If you do not want to lie, then just abstain from answering.
It is very easy to Sony to detect that you are running MySEQ. The problem is that it borders on a trust/legality issues. I do not know if it is illegal for Sony to scan the processes on your machine and report that information back to their databases. It would certainly seem like a privacy violation, but I am not a lawyer. From a programming standpoint, it is *very* easy to do. So if you are wondering "Can they detect that I am running the MySEQ server?", I am telling you right here and now, they CAN. Whether or not they can LEGALLY, I do not know. Whether or not they DO, I am not sure, although there is evidence to suggest that (at least at one time), they did.
The Program
The program consists primarily of two separate halves. One half is called the server, and the other half is called the client. The server must run on the same computer that Everquest is running on. The client has the option of running on the same computer, or a different computer. If the client is running on a different computer, than THAT computer must be running Windows 2000/XP and it must be on the same network as the first computer.
I will try and get some screenshots posted, but until then, here is basic description of each:
Server: A console application. Looks similiar to running Start->Run and entering 'cmd' and pressing Enter. There is no GUI (graphical user interface), and as such you cannot interface directly with the server. The server requires proper settings which are located a file called myseqserver.ini. These values are commonly referred to as 'offsets'. If the offsets are incorrect, the tool will have problems showing you information, or may not work at all. Usually after a patch, the offsets change, and you will need to re-visit these forums to obtain the new offset information. Once you obtain the new offsets, simply edit the myseqserver.ini file in any text editor (like notepad), make the changes, and save the file. On occasion, we may just post the whole file as an attachment, in which case you could download it and replace the old one with the new one. This INI/offsets file is located in the same directory that the server is in.
Client: A graphical application. The client is a Windows-type application with menus, buttons, mouse pointer and all that good stuff. It's main window is a large map of the zone you are currently in, with little colored dots representing each spawn in the zone. By moving you mouse over each dot, you can see detailed information about each spawn. As the spawns move around the zone, you can see their movement. There are lots of nice features that allow you to see or monitor information about the spawns, such as:
Spawnlist - this is a table like display of all spawns in the zone and their information. At a glance you can see all the information at once, if you desire. There is information on each spawn, like race, level, name, etc., each in it's own column. You can sort the spawnlist on any of the column headings.
Alerts - if you are hunting a particular spawn, you can add it to the 'alert' file. Doing so will apply special effects to that spawn, if it should appear in the current spawnlist. The dot on the map may be highlighted with a flashing circle, and the entry in the spawnlist will be moved to the top of the list and prefixed with a special character. There are different alert levels, like Hunt, Caution or Rare, each will apply slightly different effects. You may also apply sound alerts.
Depth Filter - in some zones, the passageways overlap each other in many places. So much in fact, that if you are looking at a map of the zone, all the passageways muck together to make the map look like a big mess. Depth Filtering allows one to highlight only the map lines (and spawns) that are closer to the player, while filtering out the ones that are farther from the player. A recent addition to the client, called Dynamic Alpha, is a much more powerful depth filter. The normal depth filter only relies on the Z-axis values, whereas Dynamic Alpha uses a true 3D 'sphere' around the player.
Radar - A small, radar-like, floating window that displays your position vs. other mobs in the vicinity.
Spawn Timers - some spawns will repop at nearly fixed time intervals and at the same location. If this type of spawn is detected, the client will mark the location and will keep track of when the next spawn is expected to occur. The spawn timer mark will blink yellow and then red as the expected 'repop' time approaches.
Mob Trails - this option is very cpu/memory intensive, and it is not recommended that it be used normally. However, if you are experiencing a new zone, and you want to see where the safe 'camp' areas are, you can enable collection of mob trails. Everywhere an NPC spawn moves to will leave a dot behind on the map. After awhile, the 'roaming' areas will start to fill in with these dots. The areas with no dots are likely candidates for safe camps.
There are no 'offsets' that you need to worry about with the client. All your preferences are saved in a special file for you, and loaded the next time you start the client. The only real thing you need to set in the client, is the IP address of the server (located under Options->General). To determine that, on the machine that runs the server, run Start->Run and enter "cmd /k ipconfig". You should see an entry called "IP Address" that looks something like "192.123.0.100", "10.10.0.5" or something of that nature. Use this value, including the dots, inside the client. The IP Address is basically like a phone number. You are telling the client "Hey, this is the server's phone number, go call him". The client will call and connect to the server, and the two start communicating with each other. If you tell the client the wrong number, he can never get through to the server.
MQConsole
You will see inside MySEQ is one window with MQConsole in it. This is the Macro Quest stuff. Macro Quest is a separate tool that is used to actually simulate keypresses, as if the user actually performed certain actions manually. I do not use MQConsole, nor am I familiar with it. From what I understand, it actually writes into the Everquest process, changing memory values. This is very dangerous because it can easily be detected by Sony, and if you are caught doing this, you will most likely get your account banned. MySEQ NEVER WRITES to the Everquest process! We ONLY read from the process, much like an anti-virus program would scan a process looking for viral signatures. Using MySEQ will not change your gameplay at all, and by that I mean, you won't run faster or be able to knit a thousand sweaters a minute. However, using MQConsole allows you to do things like this, but at a much greater risk. Most people that I read about getting caught, get caught using tools like MQConsole. My suggestion is to avoid it completely.
Updates
If MySEQ stops working, please visit the forums here and look for new posts regarding new offsets. They should be located here in the HELP forums.
From time to time, you may want to visit us to look for new updates to the client and/or server. These updates may provide performance enhancements or new features. Always keep your old client and server just in case something goes wrong.
Forums
We welcome you to participate in the forums. Provide feedback, help with finding offsets, spread the word. We would like people to know that there is an open source alternative, that will always remain free. If this project dies, then I can almost promise you you will eventually need to pay to use the commercial version.
Donations
Personally I do not want any donations. If you want to donate, give your money to those people who are paying for these websites. Donate to sourceforge.net or showeq.net.
Also, you will never see me posting "How much do you love me?" polls. That just makes me sick to my stomach. The best way you can thank me is by spreading the word. Tell your friends, tell your guildmates (just not in game).
MySEQ vs. ShowEQ
ShowEQ, also known as SEQ, is the original tool that was created way back before the in-game maps existed. SEQ differs from MySEQ in a few ways:
It runs on Linux, not Windows
There is no 'server'. It sniffs network traffic and decodes information being passed along to the machine that is running Everquest.
It is 100% undetectable
It shows a lot more information about spawns
Being a Linux tool, you generally need to build it yourself unless someone makes a binary release
Other than that, it provides similiar features that MySEQ does (ie: map with spawn information).
A Little History
MySEQ, a spinoff of SEQ, was originated by programmer CaveManBob and then taken up by SlartiBartFast.
http://www.geocities.com/slartibartfast1232000/index.html
It was added to sourceforge.net as a subproject under the SEQ project (SEQ admin is Ratt) in April 2003. Because SEQ was under the GNU Public License (GPL), and MySEQ was a subproject of SEQ, it fell under the same GPL license that SEQ did. Under GPL, anyone that changes the source code, and makes public those changes in a binary release, is bound by copyright laws to provide the changes to the source code if so asked by anyone (or at least provide a means to which the changes can be obtained). They may charge a 'modest' fee, to compensate for the cost of distributing the code. They may NOT add additional licenses to the product, nor charge any royalties for use of a GPL product. Anyone that obtains the GPL product can copy it and re-distribute it to anyone else free of charge.
In February 2004, MQSEQ2 (thats someone's username), posted this message:
http://www.showeq.net/forums/showthread.php?t=4670
Which basically stated that they had decided to 'move the forums' to a different website. MQSEQ2, xeerex, Mr Doh, magictiger and maybe a few others are the main folks who then became the primary developers of what I refer to as 'version two' or v2. To their credit, they invested a lot of personal time and money into continuing development of MySEQ, adding features, finding offsets, and basically making the tool a much more powerful one. They managed their forums continually. They added neat things like a Windows installer and an offset auto-updater. In the beginning, they would ship the source code with the binary releases, and everyone was basically happy. Users drifted away from these forums into the 'new' forums. I am unsure how much of the v2 code changes got checked back into the sourceforge.net CVS repository, but it was not all of it. Releases were no longer posted on sourceforge.net, but on the 'new' website.
In March 2004, I made my first request for a source tarball, because the source being shipped with the releases did not seem to jive with the release. There were missing files. I was told it would be fixed in upcoming releases. It never was. This was also around the time I first learned of MySEQ.
In August 2004, the v2 folks stopped shipping source with their binaries, because it was a waste of bandwidth. I agree 100%.
In December 2004, I posted a bug on the v2 forums and was told that there would probably not be any changes made to v2 because of certain 'issues'. The 'issues' seemed to be related to money. Somewhere in 2004, the v2 folks started accepting donations for use of the tool. This is perfectly fine, because until then they had been footing the bill for the website, and been donating their own personal time and money to the effort. Rumors arose, from where I do not know, that v2 was going to a subscription based plan, where you would have to pay a monthly fee to use MySEQ2. This sent the orginators into a frenzy. There was a demand for the v2 folks to surrender source code changes, stating that the original code was under GPL. The v2 folks claimed that there was no GPL clause in the source code itself, and that it was therefore not under GPL. There was also claims that the v2 folks had re-written so much of it, that in essence the original code was all replaced.
I do not know how much of this is fact, nor what is embellished. All I know is that as a result of this, a few things happened:
v2 did not go to a monthly based subscription plan
v2 never had any more updates (v2.1.3.0 was the last, iirc)
the originators spent a bit of effort trying to breathe life back into the v1 MySEQ line, which succeeded, but went mostly unnoticed by the masses
some of the updates that the v2 folks made went into v1
v2 folks created a 'donators family' group on their forums. If you donated, even the tiniest amount, you were tagged as a donator and offered access to special areas of their forums. In these areas, you would get first crack at new offsets if they changed. The offsets were made 'public' roughly two weeks later
v1 folks made a tool that could read the v2 offsets from the v2 website and reverse engineer them to work with v1
the number of v2 donators increased a lot
In October 2005, around the time of the DoD expansion pack release, support for v2 was removed. Donators could obtain a v3 beta from the special forums, but the public could not access it. It was at this time I decided to become involved with v1.
In November 2005, an EQ patch came along that broke all versions of MySEQ. MySEQ v1 was up and running in 2 days. v3 would not function until January 2006. I offered to help the v3 folks get their stuff running, but was refused. I posted on the v2 forums that I had a working version, but my posts were deleted within 15 minutes. Most of the v2/v3 community suffered for over a month without MySEQ, and my efforts to spread the word of a working alternative were thwarted at every turn. Day after day I would read post after post of people saying 'when can I use MySEQ again?' and I was powerless to help them (enter violins).
In January 2006, I read a message on the v3 forums that they will release a public version of the v3 beta in the near future.
http://www.rexpage.com/myseq/forum/forum_posts.asp?TID=2937
Please note that the person claiming there will be a 'public' release was Blaksmith, a forum moderator, but not one of the primary folks (like Mr. Doh or magictiger).
Note: For anyone who searches the v2/3 forums, they may find a post where it seems I flip flopped on my viewpoint. At that point in time, I did not know that the MySEQ project was originally a subproject of SEQ, and SEQ was clearly labeled as a GPL project. After much investigation, I have actually reversed my opinion more in favor of the CaveManBob/open source community side.. but that it me. My personal opinion is that there would be no MySEQ if it were not for CMB, and therefore any derivative of his work should fall under the license it was originally under. Since the v2 folks admitted that they got their original source code from sourceforge.net (the reason they moved to a new site was that SF was too slow, remember?), that *in and of itself* proves beyond any doubt that the source code was GPL. Now if the v2 folks can offer proof that the code was given directly to them by CMB and not under GPL, then I would reverse my opinion. Of course my opinion is worth nothing, but if someone did come across my flip-flop post, I wanted to explain why I flip flopped.