This article may need to be updated. Please update this article to reflect recent events or newly available information, and remove this template when finished. Please see the talk page for more information.

For a list of games which took place on our Public Server, look at The Public Server Archive

If you heard of #openttdcoop and would like to make the first steps toward a membership in our community, simply read what you have to do at Membership and Public Server. Feel free to join our community of aspirants for #openttdcoop membership. Connection details are available on the [1].

rcon on the Public Server is granted to every full member of #openttdcoop.

Feature: If you want to display the #openttdcoop Public Server info in your forum signature/other, use this code (the wiki doesn't allow embedding images from other websites, so just test it out in your signature): [img]http://dan-masek.eu/ottd/ottd_info.php?address=91.198.87.142&port=3979&lang=en[/img]

The #openttdcoop "Public Server"

Since the most games were played on this server we renamed the server to the Public Server, new players have the chance to learn the very basic concepts of cooperative gameplay. On this page, you will find a guide for the first steps into our Public Server.

What are the keypoints of The Public Server?

• First of all: BE SURE TO CONNECT TO THE IRC CHANNEL! No games can take place if we do not meet up in the channel! If you are not willing to join us in the channel it is not possible for you to become a player/member of #openttdcoop due to the lack of communication between the community and you.
• New players will get some tutorial guidance by full members of #openttdcoop but start playing right from the start
• Smaller maps will be played (256*256 - max. 1024*1024). One map lasts until everything is connected and/or optimized.
• Generally we play 512^2 1024*256 or similar sizes.
• There will be some kind of "building convention" like a "coding convention" on programming. This convention consists of some basic rules of "clever building". Be sure to know this convention (as listed below).
• Feel free to build whatever you want - you'll see the errors coming up in a growing network. Our Guides will help you on the very basics of good networking etc.
• This server is run by an autopilot - basically an answering machine for OpenTTD servers. It is configured to keep the game paused unless at least two players are connected.

How / Where / When ?

First of all, be sure to join our IRC channel (#openttdcoop). You will get information on games and servers. Players find together in the channel and start new or continue existing games. for further connection details, look at the Public Server page. The password can be found using the command !password in the IRC channel, as the password changes on a regular basis.

An advantage of having a channel on the OFTC IRC network is the circumstance of being "next to" the Official OpenTTD IRC channel (#openttdcoop started there, when it was on Freenode).

If you live in the european part of this planet you probably will have no problem related to our usual playing times. We mostly play between 18.00 to 01.00 (sometimes open ended) GMT during the weekdays and some afternoon sessions on weekends.

The General Building Convention

• First of all: set your signaling length to "2 tiles" (Patch Options). Second: set "TTDPatch compatible nonstop handling" to On.
• React on the ingame chat, we are not typing for nothing.
• If you build a Hub, name it like "Slh number / username" for a Sidelinehub (which is, relating to our Guides, a Sideline-to-Mainline-Hub) or "Bbh number / username" for a Mainline-to-Mainline-Hub. Be sure to use exactly this string (with spaces etc) - if you view the signlist, the Hubs will be sorted in the right way then and only then. Also: if we are talking about Hubs and you want to discuss about them too, simply follow the signlist to the corresponding Hub. Example: Bbh 01 / Mucht
• Cooperation is about communication! Always tell your collegues what you are doing and discuss planed tracks/junctions etc. Our members can - of course - help you on some decisions.
• Unilateral decisions by players are against the rules. Major changes to landscape, network and so on are to be discussed with other players beforehand, and agreed upon before implementation. Players should use the IRC channel if the in-game chat is insufficient.
• There could be a network plan. In this case, the network plan should be followed. If players decide to do something different, the plan has to be changed first.
• After you build new station and connect it to the sideline say "station_name connected".
• If you build big and complicated station like pick up or drop off, place a sign with your name near it.
• Take care about the rating at primary industry stations. It should be between 65 and 75 per cent. Not more, since the production of the industry would fall down.
• If you need depot and no one is nearby, build service center. Never build depot at side line.
• Don't log in as player. Change your name before connecting to our server.
• Network takes precedence over trains. Don't build hundreds of trains until the network is proven.
• Enjoy the cooperation.

Overview of Games so Far

Visit the PublicServer:Archive !

Sandbox Server

The #openttdcoop community does not have a dedicated sandbox server, but we do encourage players to experiment with new designs and layouts on our Public Server. We do ask you respect a few basic guidelines:

• There are certain times where experimentation is NOT encouraged. Generally, these times are at the beginning of a new game where funds are low. There may be other times, so ask if you're unsure.
• Flattening huge areas of land (or creating land by raising it out of water) should be done with caution, and only when absolutely necessary.
• Experimentation should never negatively impact the game's transportation network. The game should almost always take precedent over any testing.
  • For example, if you sandbox where a ML, BBH, or major station is scheduled to be built, expect your design to be removed.
  • Exceptions may be made (on an individual basis) for network plans, complex constructions that would take too long to rebuild, or cases where the test requires long-term observation.
• When in doubt, ask another player before doing experimentation.
• Always mark your experiments with a sign indicating your name and the purpose of the design. That way, people understand what it is and are less likely to consider it obsolete and delete it.
• If you do not need feedback on your design, consider running a local sandbox game instead.
  • Retrieve a final savegame from the archive, load the save game locally, find an empty space, and experiment!
  • Create or download a Sandbox Scenario.