Talk:Comparison of OpenTTD and TTDPatch features

From OpenTTD
Jump to: navigation, search

The following is a template that can be used when adding sections to the comparison table. Edit this page's source and cut and paste the section you need. - Tobin 10:37, 20 Aug 2005 (CEST)

Comparison Chart
Feature OpenTTD TTDPatch Notes
Foo the Bar Done WIP Fooing the Bar conflicts with Widgeting.
Wuzzle increase Not done Done


Features done in both

Should we remove features that are "Done" for both? I don't see how they help people make a comparison. 04:41, 17 Nov 2005 (CET)

I think it's a good idea, since most people coming to this page is mainly intrested in the diffrences and not what they have in common. It's enough that they're under "TTDPatch features in OpenTTD". :) Ailure 11:00, 1 Mar 2006 (CET)
Are all those that were said to be "done" already included in the stable build? Because if not, i disagree with removing them. -- Jokes Free4Me 08:17, 16 June 2007 (CEST)
They will be, eventually. I'm not convinced the couple of months between the nightly and the stable is worth the argument. If this is such an issue, then maybe we could settle for an additional list below the table, "TTDPatch features in unstable OpenTTD releases". Jupix 13:35, 16 June 2007 (CEST)
I agree that all items that have been completed in both should be left until the next stable build but i think it really doesn't matter that much. L blue l 16:56, 16 June 2007 (CEST)
I support the list suggestion. Anyone opposing? -- Jokes Free4Me 19:16, 16 June 2007 (CEST)

Newgrf Features

Should we have a seperate table/list for newgrf features in both or WIP in OTTD.

I say we should. Born Acorn 13:13, 20 October 2006 (CEST)

Herectic idea

Mayby heretic idea, but why waste efforts to two (nerly) simmiliar projects ? Why not concetrate efforts to one project to speed-up new versions ? —The preceding unsigned comment was added by (talkcontribs).

They are done different ways, OpenTTD is a modification of the disassembled source code from the original game, whereas TTDPatch is a patch of the original game binary without any reference to the original source code. OpenTTD can run on many more platforms whereas TTDPatch is limited to the original game's ones, DOS and Windows. Bruce98 21:35, 29 December 2006 (CET)

New classification: Stalled

Several projects are currently listed in the comparison chart as "WIP", when in reality, nothing has happened on them in ages.

I propose a new category, "Stalled", for such projects. I have specifically chosen a word with a negative connotation; this stalled status, whatever it is called, is bad. "Planned", especially, is right out, as there would be nothing preventing people from changing all the "not done" projects to "planned", and "not done" would, for all practical purposes, vanish.

The demotions I propose are as follows:

Notes:"Changing the slope under bridges is currently WIP in TTDPatch." change to "currently WIP" to "stalled".
Custom bridge heads Open is stalled. I've heard nothing about this lately, and there's no link.
Working multiplayer Patch is stalled.
New Industries Open is not done. There is no publicly available code.
New Cargoes Open is not done. There is no publicly available code.
New Routes Patch is stalled.
New airports Patch is stalled.
PBS Open is not done. The publicly available code (MiniIN) has no future in the trunk.
New pathfinder Patch is stalled.
Routing restrictions Open is stalled. I've seen discussion in the past month, but not noticed a patch update.
Signal type selection GUI Open is stalled.
Yellow signal state Demote Open to not done. (And, as a result, remove.)

The general rule I'm using for stalled is "No publicly visible code updates in the past month." In the case of TTDPatch, "publicly visible code update" is "SVN commit". In the case of OpenTTD, it is "SVN commit or update to posted patch".

If the MiniIN or something like it re-appears, I would consider inclusion in MiniIN to be sufficient for "WIP" status, but since the MiniIN itself is in planned obsolescence, I don't think that presence in the MiniIN is indication of much of anything right now.

If I have specified a project that actually is being developed, please correct me here posthaste; I'll probably be committing these changes in the next week or so.

A "Patch against rXXXX" classification might be useful as an OpenTTD alternative to WIP, which would give a better idea of the stalled-ness of a project; and/or "Ready at rXXXX" for such things like Subsidiaries, which seem to perpetually "version after next". I am not, however, proposing these. Do the research yourself and make a proper proposal if you think these are a good idea.

Moving any of these changes to the TTDPatch users page will be considered official approval of all of them. Please don't do that unless you've given good reasons for rejecting all of the changes you didn't include.

—The preceding unsigned comment was added by DaleStan (talkcontribs).

I like the idea of stalled but some of your features have seen ideas about how to fix the problems that partialy caused them to be stalled. I think maybe a different term is needed for instances were RL has goten in the way rather than it being stalled ful stop. —The preceding unsigned comment was added by Roboboy (talkcontribs).

'Not in OTTD' vs 'Comparison'

I can't understand the difference between the 1st and the 2nd with "not done" mark. - Vano 23:58, 11 February 2007 (CET)

Column order in Comparison chart

Since we here port features from TTDPatch to OTTD, it may be more logical to make column order be "Feature - TTDPatch - OpenTTD - Notes". - Vano 23:58, 11 February 2007 (CET)

NewGRF Details

Shoul we have the main newgrf features listed and then the actions, callbacks and whatnot listed in more detail?

Roboboy 12:48, 26 March 2007 (CEST)


Would one consider a windows installer to be a feature or something to get a mention on this page. I think it is. Roboboy 03:38, 23 April 2008 (CEST)

Personal tools