|2.0.5 release||16.95 KB||Sep 4, 2016||7.0.3||4,053||Download|
|2.0.4 release||16.96 KB||Apr 27, 2016||6.2.4||2,341||Download|
|2.0.2 release||17.50 KB||Mar 1, 2015||6.1.0||2,563||Download|
|2.0.1 release||17.63 KB||Feb 27, 2015||6.0.3||152||Download|
|2.0.0 release||17.19 KB||Nov 12, 2014||6.0.3||696||Download|
|1.0.16 release||17.02 KB||Nov 9, 2014||6.0.3||152||Download|
|1.0.15 release||16.77 KB||Jan 26, 2014||5.4.2||688||Download|
|1.0.13 release||16.10 KB||Jan 26, 2014||5.4.2||43||Download|
|1.0.12 release||16.10 KB||May 27, 2013||5.3.0||736||Download|
|1.0.11 release||16.11 KB||Apr 19, 2013||5.2.0||189||Download|
|1.0.10 release||16.12 KB||Apr 17, 2013||5.2.0||87||Download|
|1.0.9 release||15.95 KB||Mar 5, 2013||5.2.0||162||Download|
|1.0.8 release||16.02 KB||Feb 23, 2013||5.1.0||86||Download|
|1.0.6 release||15.67 KB||Jan 28, 2013||5.1.0||103||Download|
|1.0.3 release||5.08 KB||Jan 27, 2013||5.1.0||76||Download|
|1.0.2 release||5.46 KB||Jan 26, 2013||5.1.0||59||Download|
|1.0.1 release||5.07 KB||Jan 22, 2013||5.1.0||88||Download|
|1.0.0 release||4.83 KB||Jan 19, 2013||5.1.0||346||Download|
|1.0.7-beta beta||15.94 KB||Jan 29, 2013||5.1.0||111||Download|
|1.0.5-beta beta||15.10 KB||Jan 28, 2013||5.1.0||58||Download|
|1.0.4-beta beta||15.05 KB||Jan 28, 2013||5.1.0||52||Download|
|1.0.13-1-g414ee5d alpha||16.96 KB||Nov 9, 2014||6.0.3||36||Download|
|1.0.12-1-g0595349 alpha||16.03 KB||Sep 10, 2013||5.4.0||41||Download|
|1.0.11-1-g76ac2f9 alpha||16.03 KB||May 25, 2013||5.3.0||70||Download|
|r20130118021425 alpha||4.77 KB||Jan 18, 2013||5.1.0||65||Download|
|r20130115073720 alpha||4.70 KB||Jan 15, 2013||5.1.0||46||Download|
|r20130114101709 alpha||3.26 KB||Jan 14, 2013||5.1.0||35||Download|
This add-on provides cross-realm communication with other players through chat channels.
Channels are inherently local to each server and thus messages are not broadcast to other servers. On the other hand, Battle.net conversations are in fact cross-realm, but are restricted to players who share Battle.net IDs with each other. In addition, Battle.net conversations do not persist upon logout so players must re-join the conversation if they log on to a different character, which requires an invitation from other players.
FZ Cross-realm Communicator (FZXC) attempts to remedy this problem by providing cross-realm channel broadcasts:
- The add-on monitors messages within designated channel(s) and silently broadcasts them to receiving player(s) on different realm(s).
- If subscribed to the channel, the receiving player(s) will then mirror the message to the channel on their current realm.
- This process can be mutual, so that messages within a certain channel on one realm is synchronized with messages within the same channel on another realm, possibly with a different alias.
- These players act as servers and allow messages to be transferred across realms. These players must be mutual Real ID / BattleTags friends and have the add-on installed.
The add-on does nothing by default so it must be configured correctly to properly broadcast messages.
To set up a cross-realm channel, each server player must insert a special hashtag in the note of all the other server players. This tag establishes a one-way link between the source channel and the destination channel. The syntax of the tag is the following:
source is the name of the source channel and
dest is the name of the destination channel. The
:dest portion is optional: if omitted, the destination channel will be of the same name as the source channel. The channel name may not contain any spaces and are not case-sensitive.
To edit the note, right-click the player in the friends list and choose Set Note. Multiple hashtags may be used in one note and any other miscellaneous text in the note (anything that does not look like a hashtag) will be silently ignored.
Once the hashtags are set up properly, type
/fzxc info and it should correctly display the subscribed channels and players responsible for broadcasting the messages.
In versions 1.0.7 and above, a channel subscription feature has been implemented. This allows receiving players to selectively choose which messages to receive. Therefore, to receive messages, the receiving player must subscribe to a channel by having a corresponding tag (but reversed in direction). For example, in order to receive messages in a (local) channel "
foo", the player must have a "
#foo" tag somewhere on the friends list. If the player is not subscribed to the channel (i.e. does not have the tag), messages directed to the that channel will be silently dropped. This is done for privacy reasons.
Additional commands are available by typing
Example A: shared channel
As a simple example, consider 3 players, Alice, Bob, and Charlie, who would like to communicate through a common channel called "
foo". Whether these players are on same or different realms (or factions) is irrelevant; the configuration is identical. The 3 players are required to be mutual Battle.net friends (Real ID or BattleTag). For this setup,
- On Alice's friends list, "
#foo" must be included in the note of both Bob and Charlie.
- On Bob's friends list, "
#foo" must be included in the note of both Charlie and Alice.
- On Charlie's friends list, "
#foo" must be included in the note of both Alice and Bob.
After the notes are set correctly, each player must then
/join foo in order to post and receive messages from the channel. Any messages that appear in the channel "
foo" on one realm will then be copied to the same channel on the other realm(s) that the 3 players are on.
Example B: one-way link
Consider two players, Alice and Bob, who are on different servers. Alice is in a channel named "
foo" and regularly posts messages in it. Bob would like to receive those messages in a channel named "
bar" on his own realm, but does not wish to reply to any of those messages. Alice can broadcast the messages to Bob's channel "
bar" by inserting "
#foo:bar" into Bob's note on her friends list.
However, in order for Bob to receive the messages, he must insert "
#bar:noreply" into Alice's note on his friends list. The tag is necessary in order to subscribe to Alice's broadcasts, while the "
noreply" is a dummy channel (which presumably doesn't exist on Alice's realm), so that any replied messages are automatically dropped on Alice's end.
- If the configuration is incorrect, multiple players may broadcast copies of the same message. Workaround: Ensure that every server player has all the other server players marked correctly using the hashtag.
Feature wish list.