Back in October, there was an update to MQ to enable Actors to work across a network, as opposed to only on one PC (20251111). I run my group across 4 computers - I was wondering if this might help with curing and such, if RGL uses Actors, not sure if this is the case. I did what I think the update messages says to do, created a new [NetworkPeers] entry in macroquest.ini and populated it with the ips of the other computers in the format listed there (xxx.xxx.xxx.xxx>=0). Haven't noticed any different behaviour from any Lua/plugin/whatever that I use. If this SHOULD make a difference, did I maybe not grasp the format needed?
-
You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋
Question - MQ Actors network update
- Thread starter nitramneb
- Start date
If you are asking if RGMercs makes checks with actors for curing, yes, we do, if that data is available. We have fallbacks if not. It is decently faster than the dannet checks we fallback on, which are still plenty fast... haven't noticed curing needing any "help". This has also been live virtually since the networked actors change was, Derple was one of the testers that helped get it finished.
If you want to see actors in use by RGMercs, you can check the "Mercs Status" header on the main screen... if they are there, it is via actors (but this data is only part of the data we share across peers).
I can't speak for "Lua/plugin/whatever" that you use, you would have to ask them.
If you want to see actors in use by RGMercs, you can check the "Mercs Status" header on the main screen... if they are there, it is via actors (but this data is only part of the data we share across peers).
I can't speak for "Lua/plugin/whatever" that you use, you would have to ask them.
Yeah, that was what I was wondering. My Cleric and Druid are each on separate computers from tank, and I can't say I've ever seen them react to him being dotted. I know Actors didn't work across computers in the past, was hoping this update might actuallly assist in that. The mercs status line gives me the other 2 on the same computer as tank, but none of the other 4. Maybe didn't get the ini stuff right, will have to see if I can find some more info. Thanks.
We use dannet as a fallback (and it was the primary means before), so it sounds to me like you potentially had some issues to begin with? Hows the buffing? That also uses dannet.
Buffing has always worked fine, been using DanNet for a year or 2 now, I think - never had an issue. I see a message once in a while about a peer timing out, however, that has always been one of the ones on this computer, never the others. Just have never really seen anything do curing - Mule/Kiss in the past. I've made LeMs for events where it really mattered, and managed that way. The Curer's both cure themselves, so group stuff gets cured fine, just won't react to say the Shei Corruption DT dot in the mission on a toon on another computer. I know buffs on other toons has always been kind of an iffy thing, but had an idea that Actors might make that more responsive. I need to try putting the whole group on this computer, run Shei, and see if it all goes better that way.
I've had no issues with RGMercs curing the shei dot long before we had actor implementation or made improvements to the dannet checks we did, but I have never used multiple PCs.
Anything absolutely critical should always rely on outside scripting IMO.
To help with this funcionality you would also need to add the following to each of the computers you are running's macroquest.ini
For a four computer setup
eg. pc1
[NetworkPeers]
xxx.xxx.xxx.002=0
xxx.xxx.xxx.003=0
xxx.xxx.xxx.004=0
eg. pc2
[NetworkPeers]
xxx.xxx.xxx.001=0
xxx.xxx.xxx.003=0
xxx.xxx.xxx.004=0
eg. pc3
[NetworkPeers]
xxx.xxx.xxx.002=0
xxx.xxx.xxx.001=0
xxx.xxx.xxx.004=0
eg.pc4
[NetworkPeers]
xxx.xxx.xxx.002=0
xxx.xxx.xxx.003=0
xxx.xxx.xxx.001=0
The computers listed need to be the ones not on the machine with each particular macroquest instalation. I hope that makes sence. =0 means use the deafault port.
For a four computer setup
eg. pc1
[NetworkPeers]
xxx.xxx.xxx.002=0
xxx.xxx.xxx.003=0
xxx.xxx.xxx.004=0
eg. pc2
[NetworkPeers]
xxx.xxx.xxx.001=0
xxx.xxx.xxx.003=0
xxx.xxx.xxx.004=0
eg. pc3
[NetworkPeers]
xxx.xxx.xxx.002=0
xxx.xxx.xxx.001=0
xxx.xxx.xxx.004=0
eg.pc4
[NetworkPeers]
xxx.xxx.xxx.002=0
xxx.xxx.xxx.003=0
xxx.xxx.xxx.001=0
The computers listed need to be the ones not on the machine with each particular macroquest instalation. I hope that makes sence. =0 means use the deafault port.