Difference between revisions of "Server.met file"

Revision as of 23:36, 16 June 2005

File

Name: server.met

Location: ~/.aMule/

Description

Binary file containing the list of servers known to aMule.

Because its in binary format, it must be changed within aMule, or with other appropriate tools.

The format description below is for development information purposes.

Format

File Format

This file's fields are written in little endian order.

Note: All digit fields are unsigned unless stated.

• Met Header (1 Byte): With value Ox0E or OxE0, and is used in aMule to check for valid server.met files
• Server Count (4 Bytes): Lists the number of servers that follow
• Block of servers: Each server is constituted by the following fields:
  • Server IP (4 Bytes): Simply that. The server's IP.
  • Server Port (2 Bytes): Simply that. The port through which aMule will connect to the server.
  • Tag Count (4 Bytes): Lists the number of server tags that follows.
  • Block of Tags: Each server can have a list of associated tags with the format bellow.

Tags Format

General tags format

There are two tag identifiers: A name (string) and an ID (1 Byte)

Which one is used depends on the tag value type given or on the size of the tag name. If tag name length is 1, an ID is used.

• Tag value type (1 Byte)
• Tag Name Length (2 Bytes)
• Tag Name (size given above)
• Tag value (size depends on tag type)

Tag value types

(*): Systems with Unicode enabled have the same tag string defined twice, the first in Unicode, and the second in plain ASCII, which will be ignored by Unicode enabled clients, and used by non-Unicode ones.

Tag IDs

Tag Names

Example

More

For more information on tags used in emule files and protocol, check the ed2k tag documentation at the Hidranode project.