#openttdcoop wiki - User contributions [en]

User:Glevans2

2022-02-04T18:37:43Z

Glevans2:

Born: 1968

Current Home: Tulsa, OK USA

Email: ask me

Favorite Saying: It is pitch black. You are likely to be eaten by a grue.

Started playing OTTD: ~2007

Discovered #openttdcoop : ~2009

Joined #openttdcoop: October 2010

Specialist on: avoiding other peoples drama

Prefers: clear, concise planning, effective communication

Dislikes: R/L interfering with other interests

Best at: avoiding actual work

Quickstart/Stable

2017-06-18T21:27:14Z

Glevans2: Undo revision 28220 by Fabianezequielgallina (talk)

Welcome to the Quickstart for the Stable competition server.

==SAFETY HINT==
Server restarts when is the right time to do it (when map is full or people get bored). Questions when exactly that happens are considered evil!

==Goals==
* The goals of this server are manifold:
** To test new releases of game.
** To test new versions of and new additions to the NewGRFs.
** To allow newcomers to the game to learn how it works while enjoying themselves.

The goal is also to pose a challenge, so certain things available in the normal game have been made all but impossible here, to see people use their heads and indeed learn how things work best. Anyone can use planes to transport stuff across the map, it requires no more intelligence than a rock needs to stay in place. Boats, similarly, require little effort in planning, normally. On this server they are either hard to come by or impossible to maintain.

==Rules==
*Keep it fair
**Do not block other players
**Do not intentionally sabotage
**Respect general [http://wiki.openttd.org/Multiplayer_Rules Multiplayer rules]
**Do not use "teleports", that is, if station spread is (accidentally) left high, link two remote places by stations near maximum spread with a short commute between them.
*Be friendly, Play friendly
**This means not just behave in a kind way, but we are also used to sabotage others as low as possible.
**As a result, you should attempt to build as far from anyone else as possible.
**If you have to build close to others, try to approach near their smaller stations, not large junctions.
**Golden rule: Communicate!
*Stealing and competiton
**Generally No stealing and no competition
**Ask if you want to service an industry or town serviced by another player
*Towns
**Do not destroy towns on the map. However if a town becomes a major obstacle near your big station/junction, it is allowed.
**When you are growing large towns, make sure most of the passengers are taken to inter-city transports. Otherwise the city is "just local" and only wastes cpu, without any use for your network.
**When growing a town, make sure majority of the buildings are covered. Otherwise you are growing it for no use. An indicator of satisfactory transport is around 50% transported passengers per month (or more).
*Keep the terraform to a minimum
**See [[Terraforming#Low-Terraforming|the Low TF page]] for examples
*Please, oh please, use the chat system! You can start a chat by pressing "Enter" and entering text
*Use decent nick, no vulgar/inappropriate nick names
**You can change your nick via the console (press the key to the left of '1' to open it). Type: <code>name <new-name></code>
**You can also use the !name <newname> command
*Ask for an admin to mediate, if you have issues with another player

==Version==
We use a stable or testing version, download it from [http://openttd.org/download-testing openttd.org]

==Recommended==
*[http://wiki.openttd.org/OpenTTD OpenTTD Manual]
*[[IRC]] on [irc://irc.oftc.net/openttdcoop.stable/ #openttdcoop.stable] 
*:In addition to just connecting to the IRC channel, it would be wise to pay attention to the 'topic', as it is often updated with FAQ info about the current game on the Stable Server. The topic is usually shown in the main chat window upon channel joining, and at the top of the chat window in most GUI clients. ([http://irc.openttdcoop.org:6677/?channels=openttdcoop,openttdcoop.stable Webchat])
*http://wiki.openttdcoop.org/GRF Sometimes we might happen to make a game with especially nice newGRF configuration without limiting ourselves to the online content. It is recommended to obtain the #openttdcoop newGRF pack so you don't miss those games!

Game Creation

2017-06-18T21:19:54Z

Glevans2: Undo revision 28221 by Fabianezequielgallina (talk)

{{merge|Map Preparation}}
The time between the archival of a game and the start of the next game is generally quite large. This is because there are always a lot of different propositions and requests for the new map, and someone has to make a scenario trying to meet all those requirements. You can imagine this isn't done in a jiffy.
[[Image:gcg_mainscreen.png|center]]

Therefore we'd like to encourage all people to consider setting up a nice new game and providing a savegame from which a new [http://ps.openttdcoop.org Publicserver] game (or possibly also [[Pro_Zone]] game) might start.

== GRFs ==

Before you actually start creating a map, you have to choose from the main OpenTTD screen the newgrfs you want the new game to use. Subsequent modification may work, but it may also introduce all kinds of bugs which can render a game unplayable. When choosing grfs, mind that some grfs require a certain climate - especially important for industry and train set grfs.
<ul>
<li>first grf is always the #openttdcoop [[GRF]]pack version grf</li>
<li>then add grfs which modify landscape like trees, OpenGFX,...</li>
<li>then add station grfs, preferably quite alot*</li>
<li>add grfs which modify the infrastructure like depots, tracks, roads, bridges, foundations, town replacements</li>
<li>add grfs for ships*</li>
<li>add grfs for planes*</li>
<li>add grfs for road vehicles*</li>
<li>add ONE grf for a train set, unless you know what you're doing.</li>
</ul>
Entries marked with * are entries where more than one grf may be chosen. In all other cases stick with one grf.

You can pick your grfs from our grfpack or from the ingame content distribution BaNaNaS. Make sure that you have the latest version of a GRF from BaNaNaS and try to avoid grfs from the z_obsolete folder in our grfpack, as they are obsolete for a reason.
Also included in our grfpack are 6 spacer GRFS, shown below, which should be used to keep the grf-list neat and ordered.

[[Image:gcg_newgrfs.png|center]]

Now, check the grf list in a game whether there are any incompatibilities or requirements like one grf comes before another - fix those. At this stage you also might want to set grf parameters for some grf. Most road, town and vehicle sets take grf parameter to modify their behaviour. Have a look at the supplied readme files for details. E.g. the [http://users.tt-forums.net/2cc/index.html 2cc train set] allows to [http://users.tt-forums.net/2cc/readme.html control] the pricing and running costs as well as the choice of available trains via grf parameters.

Use the grf presets to save your selection of grfs for future reference - it's a nice selection which you may want to refer to later :). Don't forget to apply the changes you made.

== Advanced settings ==

Now, that you have chosen the grfs, make sure you use appropriate config or [http://wiki.openttd.org/wiki/index.php/Patches advanced settings]. Many can be changed on the fly during the running game, but some cannot, they're marked in bold.
Here are the settings which I use when creating a map:

[[Image:gcg_settings1.png|center]]

Important settings:
<ul>
<li>Allow building on slopes and costs: On.</li>
<li>Allow terraforming under buildings, etc: On.</li>
<li>Allow removal of more town-structures: On.</li>
<li>Pathfinders: as shown in the image.</li>
<li>Forbid 90 degree turns: On.</li>
<li>Autorenew vehicle when it gets old: Off.</li>
<li>Disable servicing when breakdowns set to none: On.</li>
<li>New orders are 'non' stop by default: On. Not really a server setting, but should still be on at every player, including you.</li>
<li>Plane speed factor: 1/1.</li>
<li>Enable timetabling for vehicles: On</li>
<li>Enable multiple NewGRF engine sets: On.</li>
</ul>
[[Image:gcg_settings2.png|center]]

Important settings:
<ul>
<li>Stations tab: exactly as shown, with the exception of noise levels.</li>
<li>Town growth speed: Slow.</li>
<li>Manual primary industry construction: anything but off.</li>
<li>Inflation: Off</li>
<li>Multiple simliar industries per town: On</li>
<li>Max distance from edge for refineries: Anything between 20 and 40.</li>
</ul>

== Difficulty settings ==

Next to these advanced settings, you need to define the difficulty settings:

[[Image:gcg_difficulty.png|center]]

<ul>
<li>Maximum no. competitors: 0</li>
<li>Initial interest rate: 2%</li>
<li>Vehicle running costs: Low</li>
<li>Disasters: Off</li>
<li>City council's attitude towards area restructuring: Permissive.</li>
</ul>

== Creating the map ==

Again, save those settings and then, finally, we can go to actually creating the game.
[[Image:gcg_generation.png|center]]
There are a few things to consider when choosing a map:
<ul>
<li>Map size: a map should not be smaller than 256 tiles squared and should not have more than 1 million tiles at most.</li>
<li>Climate: anything but toyland is acceptable</li>
<li>Number of towns: rather low, even for PAX games. They clutter the map and hinder building</li>
<li>Number of industries: except for PAX only maps you want it high. They'll mostly start closing down already during the time plans are built and voted for</li>
<li>Other terrain options are completely up to your liking. Mountainous and smooth will not result in a very hilly countryside, though. Rather make the map not too smooth, if you want some contrast.</li>
<li>Our usual starting date is 1st January 1950. But this may be varied, e.g. if with the [http://users.tt-forums.net/2cc/ 2cc] and [http://www.tt-forums.net/viewtopic.php?t=33415 egrvts] grfs vehicles become available way before this date.</li>
</ul>

If you want a more custom made map, feel free to use the scenario editor. Keep in mind though that you have to upload a save file, not a scenario file. This means you'll have to play the scenario first and upload a savefile of it. Sadly the editor does not allow prospecting of one indsutry type. This can be solved by playing the scenario in singleplayer, get some money from the cheatmenu and prospect them there.

You may also certainly look around in the [http://www.tt-forums.net/viewforum.php?f=60 scenario section] of the forums or the [http://wiki.openttd.org/index.php/List_of_player-made_scenarios scenario wiki] and shop around for a good map which might be modified a bit to suit your - and our - needs. Mind also, that we like to play our games without any of the options in the cheat menu activated - with the possible exception that money might be cheated for certain scenario purposes.

All rules on how to make a good game are, of course, only rules in so far, as they serve well in 98% of the cases. There is always the odd occasion where one well-established game creation rule is rather not suitable. But if you bend those, be really sure that you know what you do :) - they need a sound explanation.

== Finalizing the scenario ==

Now you have your map, you might want to set up boundary conditions, such as a fixed train length, [[:Category:Gametypes|gametype]] or game requirement. You can also add a small story or map explanation, to detail the rules used. Please put these condition somewhere on the map in signs, preferable in a lake.
Now before you save the game, please put the camera fully zoomed in above a lake. If you put in any boundary conditions, make sure the camera is above those. The camera position when you save your game will be used for the entire game and will also be the place for the message board. A zoomed out state here is not desirable as it will make joining for slower computers way more difficult, if not impossible.

If you have finished building a scenario, you can upload it to the [[Premade_Scenarios|ready-to-start maps]] collection page with a suitable description (an example entry exists). You can ask a member at the [irc://irc.oftc.net/openttdcoop #openttdcoop channel] on irc to review your map and if it is ok, chances are good that we add it to the server for inclusion in the next game. You can also ask us for some feedback on irc when you are unsure about some of the above points!

Public Server

2017-06-18T20:36:27Z

Glevans2: Undo revision 28222 by Fabianezequielgallina (talk)

'''For a list of games which took place on our [[Public Server]], look at [[PublicServer:Archive|The Public Server Archive]]'''

If you heard of #openttdcoop and would like to join our community, feel free to join our Public Server. Connection details are available on the [http://www.openttdcoop.org/?page=servers&s=ps Public Server Page]. Building at our public server is the first steps toward a [[membership]] in our community as well.

''rcon on the Public Server is granted only 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):
<code>[img]<nowiki>Needs replacement</nowiki>[/img]</code>

=<center>The #openttdcoop "Public Server"</center>=

At our Public Server, new players have the chance to learn the 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 active players of #openttdcoop, but can start playing right from the start
* Smaller maps are played (256*256 - max. 1024*1024). One map lasts until everything is optimized.
* Generally we play 512^2, 1024*256 or similar sizes.
* We have 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 those rules (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 and in the company.

===How / Where / When ?===

First of all, be sure to join our [[IRC|IRC channel]] ([irc://irc.oftc.net/openttdcoop #openttdcoop]). You will get information on games and servers there. Players find together in the channel and start new or continue existing games. For further connection details, look at the [http://www.openttdcoop.org/?page=servers&s=ps 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 [irc://irc.oftc.net/openttd 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) UTC during the weekdays and some afternoon sessions on weekends.

===The General Building Convention===

* First of all: set your signaling length to "2 tiles" (Signal GUI).
* React on the ingame chat, we are not typing for nothing. (Do not use Team Chat, as this does not show in IRC)
* If you build a Hub, name it like " SLH number / username" for a [[Sideline Hub]] (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 (beginning with a space) - 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. [[Communication | You can read more]] on this topic.
* Cooperation is about communication! Always tell your collegues what you are doing and discuss planned 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.
* Usually, we choose a network plan via voting first. In this case, the network plan should be followed. If players decide to do something different, the plan has to be changed first.
* If you build something, place a sign with your name near it.
* Avoid depots which can be reached by trains
* 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]]!

===Basic Rules===

We do ask you respect a few basic guidelines on all of our servers:
* Flattening huge areas of land (or creating land by raising it out of water) should be done with caution.
* 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.
* 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 [[PublicServer:Archive|archive]], load the save game locally, find an empty space, and experiment!
** Create or download a [[Sandbox Scenario]].
* We have [[Ruleset | comprehensive rule set]] here.

=== Stable Server ===

The #openttdcoop community does have a dedicated sandbox server. It can be found at [[IRC|IRC channel]] ([irc://irc.oftc.net/openttdcoop.stable #openttdcoop.stable]). This is a much better place to start than the public server for new players. Members are still arround to help you there, but the building style is much more relaxed than the public server.

Public Server

2017-06-18T20:34:41Z

Glevans2: Undo revision 28413 by Glevans2 (talk)

quickbooks enterprise payroll support phone number, quickbooks enterprise solutions support phone number, quickbooks enterprise support phone number, quickbooks enterprise support phone number canada,quickbooks for mac tech support phone number, quickbooks help support phone number, quickbooks installation support phone number, quickbooks intuit technical support phone number,quickbooks live support phone number, quickbooks mac support phone number, quickbooks merchant services support phone

Public Server

2017-06-18T20:33:20Z

Glevans2: repairing a possible troll edit

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 join our community, feel free to join our Public Server. Connection details are available on the Public Server Page. Building at our public server is the first steps toward a membership in our community as well.

rcon on the Public Server is granted only 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]Needs replacement[/img]
Contents

1 The #openttdcoop "Public Server"
1.1 What are the keypoints of the Public Server?
1.2 How / Where / When ?
1.3 The General Building Convention
1.4 Overview of Games so Far
1.5 Basic Rules
1.6 Stable Server

The #openttdcoop "Public Server"

At our Public Server, new players have the chance to learn the 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 active players of #openttdcoop, but can start playing right from the start
Smaller maps are played (256*256 - max. 1024*1024). One map lasts until everything is optimized.
Generally we play 512^2, 1024*256 or similar sizes.
We have 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 those rules (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 and in the company.

How / Where / When ?

First of all, be sure to join our IRC channel (#openttdcoop). You will get information on games and servers there. 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) UTC during the weekdays and some afternoon sessions on weekends.
The General Building Convention

First of all: set your signaling length to "2 tiles" (Signal GUI).
React on the ingame chat, we are not typing for nothing. (Do not use Team Chat, as this does not show in IRC)
If you build a Hub, name it like " SLH number / username" for a Sideline Hub (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 (beginning with a space) - 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. You can read more on this topic.
Cooperation is about communication! Always tell your collegues what you are doing and discuss planned 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.
Usually, we choose a network plan via voting first. In this case, the network plan should be followed. If players decide to do something different, the plan has to be changed first.
If you build something, place a sign with your name near it.
Avoid depots which can be reached by trains
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!
Basic Rules

We do ask you respect a few basic guidelines on all of our servers:

Flattening huge areas of land (or creating land by raising it out of water) should be done with caution.
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.
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.
We have comprehensive rule set here.

Stable Server

The #openttdcoop community does have a dedicated sandbox server. It can be found at IRC channel (#openttdcoop.stable). This is a much better place to start than the public server for new players. Members are still arround to help you there, but the building style is much more relaxed than the public server.

Community:Members

2015-09-02T20:13:03Z

Glevans2: /* The usual suspects around the Public Server (add yourself) */

__NOTOC__
==Active Members of #openttdcoop [19]==
*{{User|Ammler|ch}}, the one who dances with the newgrfs '''*'''
*{{User|dwarf|us}}, big brainmelt comes in small packages!
*{{User|Hylje|fi}}, the silent guy always and never around.
*{{User|Jam35|uk}}, who?
*{{User|KenjiE20|uk}}, the master of puppets, pulling your strings '''*'''
*{{User|LoPo|nl}}, the guy who does random shit.
*{{User|Maraxus|dk}}
*{{User|Mark|nl}}, occasional world traveler
*{{User|Mazur|nl}}, the senile one, who know nothing, no-thing! '''*'''
*{{User|mfb|de}}, always wants to try something new
*{{User|planetmaker|de}}, Make(file), newgrfs and patches '''*'''
*{{User|^Spike^|nl}}, the last Dutchy '''*'''
*{{User|StarLite|nl}} master of the magic roundabout that everybody fears ;-)
*{{User|Sylf|us}}, the oblivious, always getting into troubles
*{{User|Taede|uk}}, the Dutchy that decided to live in Scotland '''*'''
*{{User|tneo|nl}}, the spelling angel '''*'''
*{{User|V453000|cz}}, are you NUTS?
*{{User|Vinnie|nl}}, still needing a proper description here
*{{User|XeryusTC|nl}}, Rebellous doing-stuff-differently-from-convention type of guy '''*'''
''Note: '''*''' Admins have shell access to our servers, all others have rcon access''

==Honorary Members of #openttdcoop [3]==
*{{User|Brianetta|uk}} (our amiable host who is responsible for making #openttdcoop to such a vital community it is today) '''*'''
*{{User|Phoenix the II|nl}} (our host for the most busy [http://www.openttdcoop.org/blog/public-server/ PublicServer], thanks to him, we don't need to finish a game, because of the server limits.)
*{{User|TrueLight|nl}} (for being a bugfixer over ... a long time ;-) )

==Currently Inactive Members of #openttdcoop [20]==
*{{User|Adm.Spock|nl}} still too busy with other things in life, but "I'll be back"!
*{{User|Combuster|nl}} joins and parts the whole day '''*'''
*{{User|dihedral|de}}
*{{User|dp|de}}
*{{User|e1ko|cz}}
*{{User|Guru3|se}}
*{{User|Kommer|nl}}, we lost his exclusive love to openttd
*{{User|Mucht|at}}, the oldie who controlls our community from background.'''*'''
*{{User|ODM|nl}}, the innocent ''black'' lamb of #openttdcoop '''*'''
*{{User|Osai|de}}, doctor of the web and autopilot, who can hit back, if needed '''*'''
*{{User|ottd-king|uk}}
*{{User|Phazorx|iru}}, what does a communist in the tycoon world?
*{{User|Piratejerk|ca}}
*{{User|Progman|de}}, builds bigger networks on his Pentium2 at home, than 20 members on publicserver. '''*'''
*{{User|SmatZ|cz}}, pest-controller on all levels of OpenTTD(coop) '''*'''
*{{User|thgergo|hu}}, the one who builds bridges
*{{User|Thraxian|us}}, makes some little members
*{{User|uliko|se}}, omnipresent
*{{User|valhallasw|nl}}, BOFH, Wiki-god and mainly werkloos '''*'''
*{{User|xahodo|nl}}

==The usual suspects around the Public Server (add yourself) ==

{|
|-
| valign="top" |

*{{User|AlphaSC|de}}
*{{User|Absolutis|fi}}
*{{User|Benny|no}}
*{{User|britboy3456|uk}}
*{{User|Chris booth|uk}}
*{{User|Damalix|fr}}

|                  
|valign="top" |

*{{User|Djanxy}}
*{{User|Dom|at}}
*{{User|Glevans2|us}}
*{{User|James|uk}}
*{{User|mitooo|fr}}
*{{User|Maxtimbo|us}}

|                  
|valign="top" |

*{{User|MrD2DG|uk}}
*{{User|Plonka|uk}}
*{{User|Sian|dk}}
*{{User|Sistabossen|se}}
*{{User|scshunt}}
*{{User|ZxBiohazardZx|nl}}

|}
''And of course all the others above!''

== Exsuspects & retired members ==
If you are on the ex-suspects list and you start playing again, please move yourself up to the suspects list !
If you are still active and on the ex-suspects list, sorry for the moving :) we sometimes cannot find an IRC log of you while you are still active

{|
|-
| valign="top" |

*{{User|A3aan|nl}}
*{{User|Addi|ch}}
*{{User|Alanin|de}}
*{{User|Alendo|no}}
*{{User|AlexanderB|nl}}
*{{User|Andyp|us}}
*{{User|AntB|uk}}
*{{User|Avdg|be}}
*{{User|Bob27|us}}
*{{User|Barbaar|nl}}
*{{User|ChrisM|de}}
*{{User|Cipri|nl}}
*{{User|Clifs|us}}
*{{User|csuke|uk}}
*{{User|Dark_Link|se}}
*{{User|Davil|at}}
*{{User|DCritic|us}}
*{{User|DJNekkid|no}}
*{{User|Doke|de}}
*{{User|Dopefish|de}}
*{{User|draconnier|lu}}
*{{User|einKarl|de}}
*{{User|eJoJ|no}}
*{{User|Elske|nl}}
*{{User|EmiT|cz}}
*{{User|F223|us}}
*{{User|Farden|fr}}
*{{User|Floffe|se}}
*{{User|fmauNeko|fr}}
*{{User|Franco|hu}}
*{{User|Fuco|sk}}
*{{User|Gamer|nl}}
*{{User|Giles|uk}}
*{{User|Gleeb|uk}}
*{{User|Godde|no}}
*{{User|Green-devil|dk}}
*{{User|Hans|nl}}
*{{User|hdp|us}}

|                  
|valign="top" |

*{{User|h3rzb1ut|de}}
*{{User|HanziQ|cz}}
*{{User|hzzzln|de}}
*{{User|Ichi|nl}}
*{{User|Ihmemies|fi}}
*{{User|Intexon|cz}}
*{{User|itsnotvalid|hk}}
*{{User|Jinx|be}}
*{{User|John|sk}}
*{{User|jondisti|fi}}
*{{User|Juustro|fi}}
*{{User|Kejhic|cz}}
*{{User|Kirov|ar}}
*{{User|Kolbur|de}}
*{{User|Kolo|pl}}
*{{User|Kul|nl}}
*{{User|Levi|de}}
*{{User|LittleMikey|au}}
*{{User|Logix|us}}
*{{User|LordAzamath|ee}}
*{{User|Macha|ie}}
*{{User|MDGrein|se}}
*{{User|mensi|ch}}
*{{User|Microshit|nl}}
*{{User|mixrin|ru}}
*{{User|MooUK|uk}}
*{{User|mrruben5|nl}}
*{{User|N101|au}}
*{{User|narc|ro}}
*{{User|Nazirro|pl}}
*{{User|Nickman|be}}
*{{User|Nitehawk|us}}
*{{User|OwenS|uk}}
*{{User|Petert|us}}
*{{User|Pikita|uk}}
*{{User|Phil|uk}}
*{{User|pugi|de}}
*{{User|RaWt|no}}

|                  
|valign="top" |

*{{User|Red|us}}
*{{User|RichK|uk}}
*{{User|RMJ|dk}}
*{{User|Rob|us}}
*{{User|Satyap|in}}
*{{User|sbn|be}}
*{{User|Sedontane|uk}}
*{{User|SerriaRomeo|us}}
*{{User|Shader|pl}}
*{{User|Skasi|at}}
*{{User|Skidd13|de}}
*{{User|S m w|de}}
*{{User|Spectre100|us}}
*{{User|Stoffe|se}}
*{{User|strstrep|us}}
*{{User|Talonius|uk}}
*{{User|Tautrimas|lt}}
*{{User|Teddy|no}}
*{{User|Thijs|nl}}
*{{User|thomashauk|uk}}
*{{User|Tim|de}}
*{{User|Torben Paw|dk}}
*{{User|Tussengas|nl}}
*{{User|UnderBuilder|ar}}
*{{User|Vinni3|uk}}
*{{User|Vitus|cz}}
*{{User|Volny|cz}}
*{{User|Walle|be}}
*{{User|welterde|de}}
*{{User|Wouterr|be}}
*{{User|Yso|ch}}
*{{User|Zakjan|cz}}
*{{User|ZarenorDarkstalker|us}}
*{{User|Zavior|fi}}
*{{User|Zerpa|dk}}
*{{User|Zuu|se}}

|}

User:Glevans2

2010-10-21T03:06:00Z

Glevans2:

Born: 1968

Current Home: Fort Worth, Texas USA

Email: ask me

Favorite Saying: It is pitch black. You are likely to be eaten by a grue.

Started playing OTTD: ~2007

Discovered #openttdcoop : ~2009

Joined #openttdcoop: October 2010

Specialist on: making chocolate disappear

Prefers: clear, concise planning, effective communication

Dislikes: R/L interfering with other interests

Best at: avoiding actual work ...

User:Glevans2

2010-10-21T03:04:37Z

Glevans2: Created page with 'Born: 1968 Home: Fort Worth, Texas USA Email: ask me Favorite Saying: It is pitch black. You are likely to be eaten by a grue. Started playing OTTD: ~2007 Discovered #ope…'

Born: 1968

Home: Fort Worth, Texas USA

Email: ask me

Favorite Saying: It is pitch black. You are likely to be eaten by a grue.

Started playing OTTD: ~2007

Discovered #openttdcoop : ~2009
Joined #openttdcoop: October 2010

Specialist on: making chocolate disappear

Prefers: clear, concise planning, effective communication

Dislikes: R/L interfering with other interests

Best at: avoiding actual work ...