Question - Linux EQBC/Dannet

[Lordchamp55]

I much prefer Linux to any Microsoft product. I'm trying my best to stay with Linux 100%. However, I find myself being drawn back into Everquest/Macroquest/Redguides.

I understand that at least currently and possibly indefinitely, dannet does not play well with linux which leaves EQBC for me. To this point, the only thing I have found a definite limitation on is MQ2Grind which definitively states it requires dannet. Currently, EQ itself runs great for me under Linux. MQ itself is also running fine as far as I have gotten, which is just to the point of beginning group combat. Still doing minor setup/tweaking and remembering how everything works again.

One of my main questions is, what else might I be missing, since I'm just beginning this reentry into this world, that will affect me at some point down the road? Or is my only realistic avenue forward to do all this on windows. Please say it ain't so for I hate the thoughts of that. I'm not by any stretch a linux guru but I am somewhat competent and constantly learning. So I'm not above tinkering, in fact I enjoy it. However, only to a point. If I want to game, I want it to work. I don't mind spending time setting things up initially but at some point I want stability so that...well...so I can game....not tinker.

All that being said. Do I have hope? Or does microsoft win this battle before it even starts?

 

[hytiek]

I pushed the issue of DanNet reliance because of my disappointment of EQBC performance in my setup (running a full raid force); no other reason. If I recall, EQBC did very well with a single group.

I have an update I need to apply to MQ2Grind (very soon), and while I do that, I'll look at relaxing my requirements of DanNet and see about adding support for EQBC. This isn't a promise that I'll enable it by the next update, but I will consider it very strongly. Part of the EQBC support is already present in the code; I just haven't completed the implementation.

 

[Cybris]

Yes, I’ve looked into this problem extensively and it’s a wine bug. Wine’s winsock implementation fails to detect UDP readiness correctly. This causes the EQ Client to freeze. Many plugins and Lua’s require MQ2Dannet to work correctly.

What you should do is reach out on the resource page for each Plugin/Lua that you like to see if the creator would be willing to add support for EQBC. In this case you are referring to MQ2Grind so go to the MQ2Grind thread and request a feature add there now the creator may state they do not plan to add that support just be aware.

 

[Lordchamp55]

Thank you both for your responses. I'm a retired network administrator so I'm very familiar with software development, etc. When I posted this I wasn't thinking of anyone else making any changes to anything but towards ME needing to possibly change to work within the established system.

Hytiek, that you would even consider making the changes you mentioned is way beyond my expectations but I tremendously appreciate you even considering it. I do think more and more people will continue to make the linux move though as they figure out it's really not that difficult. Mainly just a different mindset. Personal control rather than corporate control IMHO.

Cybris, thanks for the direction for how to handle suggestions for the long term. I had not thought that far down the road since others changing was not my initial intention but your thoughts are extremely valid and appreciated in light of a long term solution.

Right now, my focus is mainly around the cwtn plugins, along with kissassist, etc. That is where I was a few years back and so it's my point of of known reentry. Things may have changed enough for me to reconsider that as I relearn but from what I have seen initially, I suspect I will not move from that very far. So that somewhat narrows my focus of where problems might develop. To this point, as I said I have not really run into any problems I'm aware of except the MQ2Grind one which long term I would like to have but I have many lower characters I can work with to get to the point of them being able to use Grind and also rebuild/relearn my skills after years away.

So bottom line, if there are any definite problems I need to watch for with the cwtn and kissassist plugins pertaining to the eqbc/dannet issue I would appreciate a heads up. I currently only have mq2eskay and mq2bard but if there are no real roadblocks I will possibly move on to renewing others I had in the past.

 

[Chamallow]

Wine compatible DanNet attached.
Just rebuilt ZeroMQ with -DPOLLER=select -DZMQ_HAVE_IPC=0
build.yaml GH workflow attached to DIY.

 

[Sic]

Wine compatible DanNet attached.
Just rebuilt ZeroMQ with -DPOLLER=select -DZMQ_HAVE_IPC=0
build.yaml GH workflow attached to DIY.

Please don't upload random .dll files.

If you have changes that allow for something awesome, please do a PR on the actual resource

 

[boxbuddy]

I've had dannet work on and off for Linux... I prefer eqbc anyways. Actors work fine, too.

But you can compile eqbc yourself on Linux and it improves stability immensely. (if you're running a native EQBC you need to `sudo apt install libsafec3`, for compiling it I forget the exact steps but you can figure it out from the EQBCS documentation)

I'm mostly running custom scripts, but the few dannet scripts I have run into I've written some EQBC workarounds/reimplementation of in order to be able to run those scripts.

You know what they say, If there's a will there's a way, even if that means rebinding/aliasing certain commands a script is expecting with your own custom commands lol.