Running VitaNex on Build 57.4 - MessagePump error

[ACME_INC]

I am not sure what the right way to fix this would be. When I try compiling VitaNex 5.3.1.0 on build 57.4, I get the below error. When I look at MessagePump.cs, it is now set as a static class in the latest build:

Current: public static class MessagePump
Previous: public class MessagePump

I am afraid that changing this back to a non static would undo some of the security fixes. What would be the recommended course of action and am I overthinking this?

 

[Voxpire]

You can delete the entire WebSockets folder - it will never be used (and isn't used).

I also recommend removing periods from folder names, it can cause issues with pathing.

 

[ACME_INC]

That worked. Thank you.

 

[Neraku34]

That worked. Thank you.

did u ever get the supergumps fixed? im having the same issue with that warning along with 1 error from vita nex View attachment 25712View attachment 25713View attachment 25711

 

[ACME_INC]

I get some of what you are getting but not the supergumps. I have not tried utilizing them as I have not had much time to test.

 

[Neraku34]

im just trying to get no errors when loading lol

 

[Voxpire]

If upgrading an existing Pub57, make sure to copy the new CSPROJ files from /Server, /Scripts, and /Ultima

 

[Neraku34]

it was a base pub 57.4 i delete the websocket folder got rid of the messagegump. still having the super gump and other vita nex error/warning tho

 

[ACME_INC]

I just did it again but with 57.4.1 this time as a fresh install and got the same errors. Have not had a chance to really test anything yet.

 

[Neraku34]

I went and remove Fireworks, Tools, and All Of SuperCrafts. I also went to line 36 of supergumpstooltips.cs and removed the word new from the line and its working 100% now

and now ive only got the 1 warning/error in Advanced Vendor which is fine as fixing it cause 37 errors lol..

I just did it again but with 57.4.1 this time as a fresh install and got the same errors. Have not had a chance to really test anything yet.

 

[Voxpire]

You don't need to delete all of that, it's just a case of ITool vs BaseTool, rename one to the other - whichever is causing the problem.

This shouldn't even be an issue if the `ServUO` tag is defined in Scripts.csproj - there may be an issue with the way it parses the node in the csproj.

Ex;

<DefineConstants>TRACE;NEWTIMERS;ServUO</DefineConstants>