Page 1 of 2 12 LastLast
Results 1 to 15 of 18

Thread: MySEQ 1.15.16

  1. #1
    Registered User MQSEQ2's Avatar
    Join Date
    Oct 2003
    Posts
    910

    MySEQ 1.15.16

    MySEQ 1.15.16 is now available at http://www.dvolve.net/EQ/MySEQ

    If are upgrading for the first time to the 1.15.x series you MUST download the SupportFiles.zip and place the 3 DLLs in the directory with the executable.

    Features Fixed:
    ============
    Auto Alert Loading - Tracked down a bug and it should now autoload the Alerts now.

    Random Lockups - Added some code to help prevent random lockups of the client. It it continues to happen please post your log files so we track the issue.

    Hunt Ring Color - This has been changed to a Lt. Blue for now until I can make the interface to allow you to set your own colors.

    Version - I add the Version number to the Log File and to the Statusbar.

    MQConsole / Command - Fixed the issue where if the cursor was in the Send box and you typed a /, it doesn't add the second / now.

    Server Offsets:
    ===========
    The following are the production offsets that needs to be used. You can replace everything in the sever ini with the following:

    [Memory Offsets]
    SpawnHeaderAddr=7518056
    ItemsAddr=7518060
    CharInfo=7518120
    TargetAddr=7518124
    ZoneAddr=7115292

    [SpawnInfo Offsets]
    NameOffset=1
    LastnameOffset=65
    XOffset=104
    YOffset=108
    ZOffset=112
    SpeedOffset=128
    HeadingOffset=132
    NextOffset=316
    TypeOffset=364
    LevelOffset=372
    HideOffset=376
    ClassOffset=378
    SpawnIDOffset=384
    RaceOffset=392

    [GroundItem Offsets]
    NextOffset=4
    SpawnIDOffset=12
    ZOffset=32
    XOffset=36
    YOffset=40
    NameOffset=44

    [CharInfo Offsets]
    SpawnInfo=3456

    The ZoneAddr=7115292 is the correct Zone Offset + 64 bytes to get to the Short Zone Name. If any maps are not working I need you to fully document what was happening, you will also need to set Logging to 1. The more data you can tell us the better chance we have to track down the issue.

  2. #2
    Registered User
    Join Date
    Sep 2003
    Posts
    13
    The map outline is not loading in LDoN atm.

    Log:

    12/27/2003 20:44:51:82 - MySEQ Version: 1.15.16
    12/27/2003 20:44:51:82 - Loaded Prefs.Xml
    12/27/2003 20:44:51:82 - Loading MacroQuestPanel
    12/27/2003 20:44:51:85 - Creating the Docking Manager
    12/27/2003 20:44:51:87 - Loading Bitmap into ImageList
    12/27/2003 20:44:51:87 - Creating SpawnList Window
    12/27/2003 20:44:51:98 - Creating Spawn Timer List
    12/27/2003 20:44:51:98 - Creating MQConsole Window
    12/27/2003 20:44:52:01 - Loading Position.Xml
    12/27/2003 20:45:00:34 - Zone packet recieved. Short Zone Name: (gukh_262)
    12/27/2003 20:45:00:35 - File not found loading .\maps\gukh_262.map in loadMap()
    12/27/2003 20:45:00:35 - File not found loading .\maps\gukh_262.txt in loadLoYMap
    12/27/2003 20:45:00:35 - File not found loading .\maps\gukh_262_3.txt in loadLoYMap
    12/27/2003 20:45:00:37 - File not found loading .\maps\gukh_262_2.txt in loadLoYMap
    12/27/2003 20:45:00:37 - File not found loading .\maps\gukh_262_1.txt in loadLoYMap

  3. #3
    Registered User
    Join Date
    Sep 2003
    Posts
    13
    It seems that a related bug is that if you zone into ldon again the map will appear static until you shut down myseq fully and reload it.
    Attached Files Attached Files

  4. #4
    Registered User
    Join Date
    Oct 2003
    Posts
    132
    JSG---which maps are you using?

  5. #5
    Registered User MQSEQ2's Avatar
    Join Date
    Oct 2003
    Posts
    910
    Try using ZoneAddr=7894600 in the Ini and post your Log file.

    The issue I see is gukh_262.map doesn't exist becuase of _262. If the ZoneAddr=7894600 works then I will update the offsets vs. having folks rename the map files (which is the better option).

    The problem with offsets are they move around too much and we try to locate the best offset to retrieve the data we want to look at.

  6. #6
    Registered User
    Join Date
    Oct 2003
    Posts
    132
    I had the same problem earlier this evening using v1.15.12 and v.1.15.16 and the latest offsets posted in this thread:

    http://seq.sourceforge.net/forums/sh...&threadid=4497

    However, I can confirm that v1.15.16 and the Server Offsets posted here worked fine in PoK and in a MM LDoN, including the map lines.

  7. #7
    Registered User MQSEQ2's Avatar
    Join Date
    Oct 2003
    Posts
    910
    I will add some code to search for a _### and will remove it. This will be used for the 2.x client/server.

  8. #8
    Registered User
    Join Date
    Oct 2003
    Posts
    25
    MQSEQ2, why do you hate ZoneAddr=7894600 so much?

    Old No Name

    P.S. - ZoneAddr=7894600 works. Been using it since the last offset change. It's the only offset I reliably find myself.

  9. #9
    Registered User
    Join Date
    Sep 2003
    Posts
    13
    Yep no problems with the higher offset so far...

  10. #10
    Registered User
    Join Date
    Nov 2003
    Posts
    55
    ZoneAddr=7894600

    Confirmed. Works for me.

    -Mixy!

  11. #11
    Registered User MQSEQ2's Avatar
    Join Date
    Oct 2003
    Posts
    910
    Becuase it's not the real location for the Zone information. The folks at MQ have created a structure with all the Zone Data, ie. Short Name, Long Name, Safe X,Y,Z loc, ZEM, etc.

    We want to use the same locations so when offset changes we can follow the Step By Step guide to figure out all the location that we need. The only problem I have is I don't do LDoN missions so I don't know what the Short Zone name is there and no one will actually post anything about them when I ask for the info .

    To make this project move in the right directions I need everyones help in testing and debugging the program when we have issues. I know most folks don't come here until the offsets are broken which is disappointing since we want everyones input on the direction of the project. You ask for features and one of the devs will get them in ASAP.

    All I ask in return for my time and efforts is a little bit of help when we have issues. I have a small handful of folks that I chat with online via Yahoo IM and ICQ on a daily basis. These are the folks that do all the hard work in testing and sending me error logs. Thanks to them we are getting them solved .

    I'm going to add the code to strip off th _### so that should resolve the zone issue, once and forall. I will be releasing 1.15.17 tomorrow which should fix some of the issues 1.15.16 tried to fix and/or help track them down some more.

  12. #12
    Registered User
    Join Date
    Dec 2002
    Posts
    55

    Smile Thanks for the hard work

    I upgraded to 1.15.16 and the latest offsets and I now have no problems with anything except the LDoN missions. Everything flow super smooth. The LDoN missions were loading the map and the mobs and then freezing. I had to restart MySEQ to get it to work again but it would not pull the map. I tried doing it manually and then realized that the message I was getting back was telling me the problem. For some reason it had added an extra "Maps" directory onto the directory to look for maps. Somethign like /windows/desktop/myseq/maps/maps. I went in and changed the map directory but it still looks in this location. So,...I just created maps/maps and copied all the maps there. Now it works in LDoN too.

    Thanks so much for all the hard work. I've been a long time user and contributed very little to the project. Now with your info on how to find offsets I hope to, in this small way, repay atleast a fraction of the effort that you guys have put into it.

    Cheers to the dev guys.

  13. #13
    Registered User
    Join Date
    Oct 2003
    Posts
    132
    NovaUSC---Did you try turning the Depth Filter off and then back on (F3--i think)?

  14. #14
    Registered User MQSEQ2's Avatar
    Join Date
    Oct 2003
    Posts
    910
    I added the check to remove the _### from the short zone name. Some major code changes has been done as well to get the client closer to the Server 2.0 structure.

  15. #15
    Registered User
    Join Date
    Oct 2003
    Posts
    132
    Did you add it to the existing 1.15.16 download or will that be in the next version?

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

You may post new threads
You may post replies
You may post attachments
You may edit your posts
HTML code is Off
vB code is On
Smilies are On
[IMG] code is On