Idea: pakset server info

[poppo]

we can only access same pakset's server, so I want to leave a note of server info for each pakset folders.
pakset_server_info.patch
sample:

Code Select Expand

# pak_dir/config/servers.tab
# Lines starting with # are comments
# Format: display_name = address[:port]
My NS Server = myserver.example.com:13353


[Andarix]

What is the difference between that and server_name (simuconf.tab)?

[poppo]

This file is for clients.
Clients can easy find the sever which using this pakset.
(But I'm sorry I don't really understand how to use the `network_stuff` section in `simuconf.tab`)


Furthermore, this proposal allows you to make a note of information regarding multiple servers that use your current pakset

[prissi]

I still do not understand. The serverinfo has already a line where one can give a link to a pakset or any other info. And the paksetname is transferred with the server. And one can even get a list of mismatched/missing objects for the own pakset.

[Andarix]

This file is for clients.
Clients can easy find the sever which using this pakset.
(But I'm sorry I don't really understand how to use the `network_stuff` section in `simuconf.tab`)

You're mistaken. The network parameters in simuconf.tab are also for the server settings.

The client doesn't transmit the data to the server list; the server does.

[poppo]

This allows you to create shortcuts to access unannounced (open for limited members) servers or servers in your local network.

[Andarix]

This allows you to create shortcuts to access unannounced (open for limited members) servers or servers in your local network.

In my local network, I know the server's IP address and connect to it.

[prissi]

You can just open any server with "net:123.456.789.123" or net:[2f34::0012]" or "net:serves.simtrans-forum.de" Make a shortcut on the desktop for that containing "simutrans -obj pak.special -load net:xyz.org" as command in it.

Also, the info in such a a pakset folder might become stale very quickly, if it is an IP number.