Legacy MacroQuest2 (Test server) 2021-12-15

[Rhino]

Is there a forum thread I missed for troubleshooting compile issues with the VanillaDIY solution? If not could someone provide some guidance for a relative noob to c++ / .vcxproj compilation. I've cloned the vanilla gitlabs repo locally followed the steps in the README but am unable to successfully compile.

Windows SDK Version: 10 (latest version)
Visual Studio 2019: v16.4.2
C++ Toolset: v142

Errors I'm receiving:
Error LNK1104 cannot open file 'MQ2Main.lib' MQ2AutoClaim C:\Source\VeryVanilla\MQ2AutoClaim\LINK 1
Error LNK1104 cannot open file 'MQ2Main.lib' MQ2TSTrophy C:\Source\VeryVanilla\MQ2TSTrophy\LINK 1

Error C2338 Windows headers require the default packing option. Changing this can lead to memory corruption. This diagnostic can be disabled by building with WINDOWS_IGNORE_PACKING_MISMATCH defined. (compiling source file TelnetServer.cpp) MQ2Telnet C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winnt.h 2482

Error C2338 Windows headers require the default packing option. Changing this can lead to memory corruption. This diagnostic can be disabled by building with WINDOWS_IGNORE_PACKING_MISMATCH defined. (compiling source file WinTelnet.cpp) MQ2Telnet C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winnt.h 2482

Error C1189 #error: The <experimental/filesystem> header providing std::experimental::filesystem is deprecated by Microsoft and will be REMOVED. It is superseded by the C++17 <filesystem> header providing std::filesystem. You can define _SILENCE_EXPERIMENTAL_FILESYSTEM_DEPRECATION_WARNING to acknowledge that you have received this warning. MQ2SQLite C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\include\experimental\filesystem 30

Not sure if it is safe to disable these using the mentioned DEFINEs.


Notes: Some of the .vcxproj are still targetting the deprecated v141_xp toolset even in the RELEASE configuration. Since I don't have these installed (they don't include the deprecated v141 toolset with the VS 2019 C++ package's default includes) I've changed these to target the v142 toolset. Not sure if this is an acceptable workaround or if I need to manually install the deprecated v141_xp toolset.

 

[Redbot]

Is there a forum thread I missed for troubleshooting compile issues with the VanillaDIY solution? If not could someone provide some guidance for a relative noob to c++ / .vcxproj compilation. I've cloned the vanilla gitlabs repo locally followed the steps in the README but am unable to successfully compile.

Windows SDK Version: 10 (latest version)
Visual Studio 2019: v16.4.2
C++ Toolset: v142

Errors I'm receiving:
Error LNK1104 cannot open file 'MQ2Main.lib' MQ2AutoClaim C:\Source\VeryVanilla\MQ2AutoClaim\LINK 1
Error LNK1104 cannot open file 'MQ2Main.lib' MQ2TSTrophy C:\Source\VeryVanilla\MQ2TSTrophy\LINK 1

Error C2338 Windows headers require the default packing option. Changing this can lead to memory corruption. This diagnostic can be disabled by building with WINDOWS_IGNORE_PACKING_MISMATCH defined. (compiling source file TelnetServer.cpp) MQ2Telnet C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winnt.h 2482

Error C2338 Windows headers require the default packing option. Changing this can lead to memory corruption. This diagnostic can be disabled by building with WINDOWS_IGNORE_PACKING_MISMATCH defined. (compiling source file WinTelnet.cpp) MQ2Telnet C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winnt.h 2482

Error C1189 #error: The <experimental/filesystem> header providing std::experimental::filesystem is deprecated by Microsoft and will be REMOVED. It is superseded by the C++17 <filesystem> header providing std::filesystem. You can define _SILENCE_EXPERIMENTAL_FILESYSTEM_DEPRECATION_WARNING to acknowledge that you have received this warning. MQ2SQLite C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\include\experimental\filesystem 30

Not sure if it is safe to disable these using the mentioned DEFINEs.


Notes: Some of the .vcxproj are still targetting the deprecated v141_xp toolset even in the RELEASE configuration. Since I don't have these installed (they don't include the deprecated v141 toolset with the VS 2019 C++ package's default includes) I've changed these to target the v142 toolset. Not sure if this is an acceptable workaround or if I need to manually install the deprecated v141_xp toolset.

Make sure you build MQ2Main first

 

[Rhino]

Thanks RedBot. That solved the first two errors cannot open file 'MQ2Main.lib'.

Tried a full clean and rebuild (cleaned my local repo with `git clean -dxf`, re-ran MQ2Auth.exe, opened the solution, cleaned the solution for good measure, built MQ2Main first, built the rest of the solution)

The error on MQ2SQLite occurred again even after the full clean + rebuilt.
Error C1189 #error: The <experimental/filesystem> header providing std::experimental::filesystem is deprecated by Microsoft and will be REMOVED. It is superseded by the C++17 <filesystem> header providing std::filesystem. You can define _SILENCE_EXPERIMENTAL_FILESYSTEM_DEPRECATION_WARNING to acknowledge that you have received this warning. MQ2SQLite C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\include\experimental\filesystem 30

The CS2338 error occurred again but on a different project, this time on MQ2Discord instead of on MQ2Telnet.

Additionally got this new error on MQ2ItemDisplay after the full clean + rebuild
7>MQ2ItemDisplay.cpp
7>C:\Source\VeryVanilla\MQ2Main\MQ2Main.h(43,10): fatal error C1083: Cannot open include file: 'windows.h': No such file or directory
7>Done building project "MQ2ItemDisplay.vcxproj" -- FAILED.

Not sure what, if anything, depends on those plugins. For now I'll try working with it without those three building.

 

[Redbot]

Sorry @Rhino, this is likely my fault. I need to make sure the public version is building correctly. I'll tag you when I get to it again.

 

[Redbot]

Redbot updated Very Vanilla MQ2 (Test server) with a new update entry:

20200429

Apr 29 2020 by RedGuides
- MuleAssist.mac (eqmule) More buff fixes
- MQ2AutoAccept (Knightly, alynel) code cleanup
- MQ2AutoForage (Knightly) code cleanup
- MQ2KissBuffs (ChatWithThisName) workaround for chain-casting issues after zoning
- CWTN plugins (ChatWithThisName, Sic) updated with new windows, reset camp options, and various fixes and improvements.

Apr 29 2020
- .CachedBuff now accepts = for exact match and if not specified it will do partial match
Example 1: Lets say you have...

Read the rest of this update entry...

 

[Multichar]

I managed to cause a chain crash of all loaded instances when trying to open a new window. I had added 2 accounts to the MQ launcher, and I messed up and put the same login on both. I realized the mistake when one window logged in, then the other got a 'login can not be validated' error. I right clicked and selected edit on the incorrect entry, corrected the username/login name, and hit save. I then told it to try loading that account again. The new window opened up, immediately crashed, then every other client currently running started crashing here and there with a ton of different popups (saying stuff from 'tried to detour from a NULL address check your code', etc.) My log folder has multiple dmp files but it seems entirely different things were claimed for each one (eg MQ2Main_xxxx.dmp , mq2nav_xxx.dmp)

 

[proutos]

The game work for you with redguide launcher? Because for me it is not working since thursday. I tried to reinstall the launcher and still doesnt work. The last launcher update is 29-04-2020 and there was an patch on test thursday the 7. We are the 10 and still no update...

 

[Redbot]

The game work for you with redguide launcher? Because for me it is not working since tuesday. I tried to reinstall the launcher and still doesnt work. The last launcher update is 29-04-2020 and there was an patch on test tuesday the 7. We are the 10 and still no update...

yes, it's still working. what error are you receiving?

 

[proutos]

yes, it's still working. what error are you receiving?

Just saw what was the problem... My wife played the live version on my cpu and i did not saw it... So the live patch was in lol...

 

[Redbot]

Just saw what was the problem... My wife played the live version on my cpu and i did not saw it... So the live patch was in lol...

Good detective work!
I like to keep Live and Test in different folders. Takes up more space, but it's worth it not having to re-patch

 

[WOnce]

FYI, Test just finished patching.

 

[Redbot]

Tomorrow afternoon eqmule should have us back up. It might be a little longer due to some hasty merges I made on git, which brainiac and knightly are helping revert.

 

[fyrebug]

eta on new version?

 

[bb4]

eta on new version?

Eqmule posted on twitter a few hours ago that he has released the Test update. Redbot should have it compiled sometime this morning.

 

[WOnce]

Having withdrawal. Or maybe it's the extra coffee.

 

[Redbot]

Eqmule posted on twitter a few hours ago that he has released the Test update. Redbot should have it compiled sometime this morning.

That version wasn't quite stable, we're waiting for something more solid. Still hoping for today.

 

[drawthow]

Having withdrawal. Or maybe it's the extra coffee.

Heavy drinking seems to help

 

[bb4]

That version wasn't quite stable, we're waiting for something more solid. Still hoping for today.

Ah. Reading comprehension was lacking for me this morning. Looks like he released a stable version about an hour ago!

 

[Redbot]

Just finished merging a few minutes ago. We have some permissions issues on our buildserver because Azure decided to push an update that broke everything. Once that's fixed we can release. ETA: ~2 hours

 

[bb4]

Just finished merging a few minutes ago. We have some permissions issues on our buildserver because Azure decided to push an update that broke everything. Once that's fixed we can release. ETA: ~2 hours

Thanks for keeping us updated! We all appreciate everything you do!

 

[Redbot]

Redbot updated Very Vanilla MQ2 (Test server) with a new update entry:

20200514

May 14 2020 by RedGuides
- MQ2AdvPath (Knightly, alynel, ChatWithThisName, brainiac) code cleanup
- MQ2AASpend (Knightly, Sic, brainiac) code cleanup
- MQ2Camera (Knightly) code cleanup
- MQ2FarmTest (ChatWithThisName) refactored, cleaned up, and various bugs fixed
- MQ2HUDMove (ChatWithThisName, brainiac) fix crash with /hudlist
- MQ2AutoLoot (Knightly, alynel) Minor code cleanup
- MQ2TsTrophy (Sic) This quick-fix eliminates trying to swap items that are no longer valid.
- MuleAssist.mac...

Read the rest of this update entry...

 

[bb4]

Redbot updated Very Vanilla MQ2 (Test server) with a new update entry:

20200514



Read the rest of this update entry...

Getting told that the following plugins are out of date with respect to main.
MQ2Autoaccept
MQ2Cast
MQ2Debuffs
MQ2EQBC
MQ2Exchange
MQ2Melee
MQ2Moveutils
MQ2Rez
MQ2Advpath
MQ2Twist
MQ2TributeManager
MQ2Posse
MQ2XPTracker

 

[Redbot]

Re-doing the compile. Permissions issues were worse than I thought.

 

[rounde683]

Definitely appreciate you guys. Looking forward to unwinding tonight with my boxed tunes!

 

[Redbot]

Ok, figured out the issues on my end.
1) Windows expired the password on the build user, which isn't a real user and is never logged on, so it took awhile to figure out.
2) MQ2Camera rebuilds MQ2Main, which breaks all plugins compiled after. This doesn't happen when building locally, only on Azure

Rebuilding now, ETA 45 minutes

 

[Redbot]

Redbot updated Very Vanilla MQ2 (Test server) with a new update entry:

20200514

May 14 2020 by RedGuides
- MQ2AdvPath (Knightly, alynel, ChatWithThisName, brainiac) code cleanup
- MQ2AASpend (Knightly, Sic, brainiac) code cleanup
- MQ2Camera (Knightly) code cleanup
- MQ2FarmTest (ChatWithThisName) refactored, cleaned up, and various bugs fixed
- MQ2HUDMove (ChatWithThisName, brainiac) fix crash with /hudlist
- MQ2AutoLoot (Knightly, alynel) Minor code cleanup
- MQ2TsTrophy (Sic) This quick-fix eliminates trying to swap items that are no longer valid.
- MuleAssist.mac...

Read the rest of this update entry...

 

[howlinhoss]

FYI - looks like test server was updated today.

 

[rounde683]

Yeah, I'm all broken again =(

 

[runcade]

I have always been curious. What actually changes in the game that makes you have to recompile MQ?

 

[Sic]

I have always been curious. What actually changes in the game that makes you have to recompile MQ?

the part of the program that points to a thing and says "this is where your name is", "this is a player", etc - the offsets - they have to be redetermined and reassigned

 

[runcade]

the part of the program that points to a thing and says "this is where your name is", "this is a player", etc - the offsets - they have to be redetermined and reassigned

Is that something that DBG does to make it hard on MQ or just a natural function of updating the game?

 

[Redbot]

Redbot updated Very Vanilla MQ2 (Test server) with a new update entry:

20200521

May 21 2020
- Updated for TEST

May 21 2020
- Updated for LIVE

May 19 2020 by RedGuides
- New Plugin! MQ2React (drwhomphd) Allows users to define actions, as well as conditions that will perform those actions. Think of it like the holyshit/downshit part of
mq2melee, without the melee. MQ2React also allows for complex conditions to be defined as global conditions and reused throughout multiple reacts, thus making reacts
considerably easier to maintain and reuse.
- CWTN plugins...

Read the rest of this update entry...

 

[Sic]

Is that something that DBG does to make it hard on MQ or just a natural function of updating the game?

just a natural function of when they re-generate the game - its like reaching in your pocket and grabbing all your change - the change is the same, but where the shiny nickle is compared to the dull dime is different places now

 

[ABDon]

Something funky started happening today after last patch... a split second lockup occurs, followed by 2 of my EQ clients closing.

No EQ error, no MQ error pops up, just... gone.

Happened 3 times tonight, any ideas?

Application Event log shows MQ2Main.dll faulting;

Faulting application name: eqgame.exe, version: 0.0.0.0, time stamp: 0x5ec6b11f
Faulting module name: MQ2Main.dll, version: 2020.5.21.0, time stamp: 0x5ec70938
Exception code: 0xc0000005
Fault offset: 0x000baeb9
Faulting process ID: 0x2658
Faulting application start time: 0x01d63063fdb8370c
Faulting application path: D:\daybreak\everquest\eqgame.exe
Faulting module path: D:\ProgramData\RedGuides\DesktopUtility\MQ2\Live\Release\MQ2Main.dll
Report ID: 00eb521a-f295-4b40-8e35-0cfd7a6920e1
Faulting package full name:
Faulting package-relative application ID:

 

[Sic]

Something funky started happening today after last patch... a split second lockup occurs, followed by 2 of my EQ clients closing.

No EQ error, no MQ error pops up, just... gone.

Happened 3 times tonight, any ideas?

Application Event log shows MQ2Main.dll faulting;

Faulting application name: eqgame.exe, version: 0.0.0.0, time stamp: 0x5ec6b11f
Faulting module name: MQ2Main.dll, version: 2020.5.21.0, time stamp: 0x5ec70938
Exception code: 0xc0000005
Fault offset: 0x000baeb9
Faulting process ID: 0x2658
Faulting application start time: 0x01d63063fdb8370c
Faulting application path: D:\daybreak\everquest\eqgame.exe
Faulting module path: D:\ProgramData\RedGuides\DesktopUtility\MQ2\Live\Release\MQ2Main.dll
Report ID: 00eb521a-f295-4b40-8e35-0cfd7a6920e1
Faulting package full name:
Faulting package-relative application ID:

in your Release folder, you should have another folder called "Logs" this is where your .dmp files go to after a hard crash like this - e-mail one of those from today to [email protected]
a couple people have reported some crashing on test atm, and the .dmps i took at a look at didn't have anything someone with my skill level could do with but if you want to email that to mule, feel free to PM it to me as well and i'll take a look right now in case there is something in there that i can assist with

 

[ABDon]

in your Release folder, you should have another folder called "Logs" this is where your .dmp files go to after a hard crash like this - e-mail one of those from today to [email protected]
a couple people have reported some crashing on test atm, and the .dmps i took at a look at didn't have anything someone with my skill level could do with but if you want to email that to mule, feel free to PM it to me as well and i'll take a look right now in case there is something in there that i can assist with

Cheers Sic, there's no dumps for today in the log folder though, last one was 16th May

 

[Sic]

Cheers Sic, there's no dumps for today in the log folder though, last one was 16th May

well that must be frustrating heh (reason i mentioned checking the folder even tho you said no popup/dmp etc, is someone else thought a similar thing but did have a dmp from today)

 

[WOnce]

Test going down for update today,12:00 PM PDT.

 

[rounde683]

Confirmed, My Test Very Vanilla is broke =/

 

[Rexlon]