-
You've discovered RedGuides 📕 an EverQuest multi-boxing community 🛡️🧙🗡️. We want you to play several EQ characters at once, come join us and say hello! 👋 -
Question - DanNet vs EQBC (1 Viewer)
- Thread starter jsr09
- Start date
Solution
- Joined
- Oct 31, 2019
- RedCents
- 1,628¢
what I understood there is no "vs". Dannet for me seems much more reliable. I switched several month ago and am still happy with that decision. Somewhere on the boards here I found a table, which had a "translation" for any possible EQBC-command to the Dannet-syntax. After having translated my Hotbutton I was happy and never felt the urge, to go back.
As with many things the answer depends. You can run both side by side.
Nether EQBC or DanNet have a significant impact on your CPU usage.
If all you are using EQBC or DanNet for are issuing commands the differences are minimal.
The real question you need to ask is:
Do I need either or both for the tools I want to use?
To dive into the weeds the major differences are:
DanNet is more of a "on demand" service. It does not require a server so its easier to get started and go.
EQBC requires you to setup a server and have each MQ client connect to it so you need to know a little bit about network addresses to get it setup and running.
EQBC has been around a long time and the original author wrote several plugins such as MQ2NetBots which uses EQBC to pass data between clients. The data it sends is defined at compile time so if you want to add a new field you have to get someone to change the source code.
DanNet on the other hand is designed to flexible with regard to the data it sends. This means its only pushing the data you need for your script. This makes it lighter weight.
I've run EQBC with 40+ clients across 3x machines with no problems so neither one really pushes enough data to cause network issues.
Nether EQBC or DanNet have a significant impact on your CPU usage.
If all you are using EQBC or DanNet for are issuing commands the differences are minimal.
The real question you need to ask is:
Do I need either or both for the tools I want to use?
To dive into the weeds the major differences are:
DanNet is more of a "on demand" service. It does not require a server so its easier to get started and go.
EQBC requires you to setup a server and have each MQ client connect to it so you need to know a little bit about network addresses to get it setup and running.
EQBC has been around a long time and the original author wrote several plugins such as MQ2NetBots which uses EQBC to pass data between clients. The data it sends is defined at compile time so if you want to add a new field you have to get someone to change the source code.
DanNet on the other hand is designed to flexible with regard to the data it sends. This means its only pushing the data you need for your script. This makes it lighter weight.
I've run EQBC with 40+ clients across 3x machines with no problems so neither one really pushes enough data to cause network issues.
the older versions of eqbcs/eqbcs2/eqbcswhatever definitely did have some issues
the new eqbcs (which rg ships) had some work done by knightly and > for me < those issues went away.
I personally still use both - but if someone were to ask me which to use if just using 1, I would suggest dannet
If you’re new and learning, use dannet due to the low config and flexibility. (As dewey said, neither will give you CPU issues).
If you have a more complicated network setup and do things like spanning subnets you might need EQBC (since dannet is local network only).
They can both work side by side though, so it’s not a big deal, just no sense learning the EQBC commands if dannet works for you. If you already know EQBC then you’re likely only “switching” to dannet when there’s something you need or a script that requires it.
If you have a more complicated network setup and do things like spanning subnets you might need EQBC (since dannet is local network only).
They can both work side by side though, so it’s not a big deal, just no sense learning the EQBC commands if dannet works for you. If you already know EQBC then you’re likely only “switching” to dannet when there’s something you need or a script that requires it.
nope... Dannet is peer to peer, so no server to speak of.. whereas the EQBC server is the central server that each client communicates through..
So once you move to dannet , no more external eqbc server application needed..
