Page 1 of 1
Stuff that needs to be done before new release
Posted: 08 Jul 2004 19:23
by Darkvater
Features, fixes that should be finished before a new release should be added to the list below. We can just check them off when it's added.
- Language - Of course update all supported language files, such that there are no missing strings, or other problems.
- Network - GUI for Network play, complete with graphical player selection
- Network - Also transfer openttd.cfg for network play?
- Network - Change port from 12345 (known trojan) to 3979
- Network - perhaps [980799] Reconnect on network sync error ?
- Scenario - Give scenario's different extensions (scn?) so they can be easily identifyeable and starting money, year, vehicles, etc. can be set.
- Bug - Scenario - [963076] Scenario / starting date patch bug
These two bugs will be fixed with a new savegame revision (and a few other adjustments):
Of course all bugs should be fixed
, but I feel these 2-3 are the most important
Add your own to the list.
Posted: 11 Jul 2004 21:18
by dominik81
Here's an update on all the stuff that is finished/fixed:
These things are not done yet, but I think they shouldn't block a release:
Posted: 11 Jul 2004 21:37
by ChrisCF
Question. Why port 3979 for multiplayer?
Posted: 11 Jul 2004 21:46
by MYOB
ChrisCF wrote:Question. Why port 3979 for multiplayer?
Because its not a known trojan and hence less likely to be explicitly blocked.
Its assigned to "idps" by the IANA, in the name of Jean-Francois Rabasse, and has been since July 2003, however...
Posted: 11 Jul 2004 21:54
by ChrisCF
It's generally a good idea to use potrs which *aren't* already assigned
Posted: 11 Jul 2004 22:08
by minime
True, after all there are plenty of them available.
It would also be a good idea to have the port number user configurable (unless there already is an option to do so, I don't know that). That could come in handy trying to get the game working through firewalls in some cases or when for whatever reason the "standard" port is not useable.
Posted: 12 Jul 2004 16:12
by dominik81
Port 3979 was chosen, because it is not kown to be used by any other program. Please note that this is the default port only. You can change the it in openttd.cfg at any time by adding this:
MYOB wrote:Its assigned to "idps" by the IANA, in the name of Jean-Francois Rabasse, and has been since July 2003, however...
No, it's not. Quote from
iana.org:
Code: Select all
spw-dialer 3796/tcp Spaceway Dialer
spw-dialer 3796/udp Spaceway Dialer
# Patrick Fisher <pfisher@hns.com> July 2003
idps 3797/tcp idps
idps 3797/udp idps
# Jean-Francois Rabasse <jfr@idps.org> July 2003
minilock 3798/tcp Minilock
minilock 3798/udp Minilock
...
drip 3949/tcp Dynamic Routing Information Protocol
drip 3949/udp Dynamic Routing Information Protocol
# Dana Blair <dblair@cisco.com> June 2004
# 3950-3983 Unassigned
mapper-nodemgr 3984/tcp MAPPER network node manager
mapper-nodemgr 3984/udp MAPPER network node manager
Posted: 12 Jul 2004 17:55
by ChrisCF
Would it cost you anything to get the port assigned?
Posted: 12 Jul 2004 18:21
by MYOB
dominik81 wrote:Port 3979 was chosen, because it is not kown to be used by any other program. Please note that this is the default port only. You can change the it in openttd.cfg at any time by adding this:
MYOB wrote:Its assigned to "idps" by the IANA, in the name of Jean-Francois Rabasse, and has been since July 2003, however...
No, it's not. Quote from
iana.org:
Code: Select all
spw-dialer 3796/tcp Spaceway Dialer
spw-dialer 3796/udp Spaceway Dialer
# Patrick Fisher <pfisher@hns.com> July 2003
idps 3797/tcp idps
idps 3797/udp idps
# Jean-Francois Rabasse <jfr@idps.org> July 2003
minilock 3798/tcp Minilock
minilock 3798/udp Minilock
...
drip 3949/tcp Dynamic Routing Information Protocol
drip 3949/udp Dynamic Routing Information Protocol
# Dana Blair <dblair@cisco.com> June 2004
# 3950-3983 Unassigned
mapper-nodemgr 3984/tcp MAPPER network node manager
mapper-nodemgr 3984/udp MAPPER network node manager
Oops, read 3979 and 3797... fecking dyspraxia sometimes manifests itself that way