Utility MQ2DanNet

MQ2DanNet
This plugin is designed to be a serverless peer network. It is (hopefully) mostly plug and play, and should automatically discover peers for most local network configurations.



Some Notes about Setup

• Some complicated network topologies won't be supported (a server interface is a better solution)
• If for some reason the peers aren't self-discovering on a local network
  • check the output of /dnet interface
  • set one of the discovered interface names with /dnet interface "<name>"
  • unload and then reload the plugin
  • failing that, I'll have to look into why, so contact me with as much info as possible

Use
There are 2 basic uses
1. Set up an observer

• Methods of setting up an observer
  • /dobserve <name> -q <query> [-o <result>]
• Reading an observer's data: ${DanNet[<name>].Observe[<query>]} or ${DanNet[<name>].O[<query>]}
• Dropping an observer: /dobserve <name> -q <query> -drop
• result is optional if no out variable is needed (or not executing from a macro)

2. Single-use direct query

• Submitting a query: /dquery <name> -q <query> [-o <result>] [-t <timeout>]
  • Combines /delay with /varset
  • timeout is optional, and the default can be configured
  • result is optional, will just write out the result to ${DanNet.Q} or ${DanNet.Query} if omitted
  • If not run in a macro, ignores result and just writes out to the TLO

Queries
A query is simply a normal TLO access from the perspective of the peer with the external ${} stripped
Examples:

• Me.CurrentMana
• Target.ID
• Me.Current$\{thing} -- this will evaluate ${thing} on the peer before sending a response

Names
A fully-qualified name is <server>_<character>, but if you only intend to communicate on your own server, you can ommit the first part and use just <charactername> in all these commands.
Examples:

• Locally talk to fatty: /dtell fatty You smell.
• Talk to fatty on the test server: /dtell test_fatty I can still smell you from this server!

Known Issues

• Proper workgroup permissions are needed for different network groups across PC's (specifically windows 10 with windows 7 machines)
• ZeroMQ has structural issues if something externally closes the TCP sockets that it is using for inter-process communication. If you are getting unexpected crashes after some time running, check your antivirus/firewall software to ensure that it's letting eqgame exist peacefully. Kaspersky is known to close these sockets.