Server Browser Rules: Difference between revisions
Jump to navigation
Jump to search
Fernando187 (talk | contribs) No edit summary |
Fernando187 (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
== | ==Information== | ||
"'''Server Browser Rules'''" are ''key-value'' string pairs defined server-side. These values are transmitted/announced/broadcasted by your MTA Server using the ASE (All-Seeing Eye) protocol, when queried on the main UDP Port (default 22003). The purpose of this data is to be received and parsed by MTA Clients in the Server Browser, to display the list of online MTA servers with custom information for each server. | "'''Server Browser Rules'''" are ''key-value'' string pairs defined server-side. These values are transmitted/announced/broadcasted by your MTA Server using the ASE (All-Seeing Eye) protocol, when queried on the main UDP Port (default 22003). The purpose of this data is to be received and parsed by MTA Clients in the Server Browser, to display the list of online MTA servers with custom information for each server. | ||
Revision as of 11:16, 3 January 2025
Information
"Server Browser Rules" are key-value string pairs defined server-side. These values are transmitted/announced/broadcasted by your MTA Server using the ASE (All-Seeing Eye) protocol, when queried on the main UDP Port (default 22003). The purpose of this data is to be received and parsed by MTA Clients in the Server Browser, to display the list of online MTA servers with custom information for each server.
Setting & Getting
These rules can be defined and obtained using these two server-side functions: