chrissicom wrote:I've just come to this thread the first time and find it cool to see someone else maintained a patch pack while I was gone! Also that PBS, passenger destinations and engine pools is added now rocks!!
I have to admit I want to remain faithful to ChrisIN, but I was quite balanced between both the ChrisIN and the Gonozal Pack, as both adds incredibly cool patches
chrissicom wrote:These were 3 of my most anticipated patches. I am not too up to date right now but are these 3 complete or are there still bugs in them?
PBS : In the current Gonozal Pack, there are a few bugs with the signals auto-build tool (sometime is doesn't build the right signals), but the main problem with PBS is the difference with classic signals. The firsts tentatives of use often result in many trains crashs, as PBS doesn't like the traks layout to be updated while a train is on the same area.
Engine Pool : I detected an error in the Gonozal Pack (see a few posts ago) and it looks like Peter did a fix about it. This patch is mostly bug free, but still need some work as told in the dedicated thread (3rd/4th tracks types, etc.)
PaxDests : I didn't noticed any problem except economy balancing (very hard to stard, and absolutely too easy when started). All features seems to work fine. The only problem is that new station screens are undocumented and some people like me just can't have any idea of what are some of the numbers displayed)
chrissicom wrote:When I made the new ChrisIN thread I didn't know we have another patchpack floating around already so maybe it's better if I just help out here or something. I actually had an idea for a new ChrisIN which I don't know yet would be possible.
That's something I just would like to suggest : work together to maintain a unique version, so I can remain faithful to the ChrisIN, and get advantage of the new Gonozal's Pack patches
chrissicom wrote:I intended to mostly use "external" files for adding patches, i.e. not modify the original OpenTTD files but at seperate header files and sources for the ChrisIN patches to be less intrusive and have an easier job when updating patch code, because it's not mixed up with a whole bunch of original code. Only problem is that some patches are not adding something but modify trunk code so I thought I would only add them if they are really very good and up to a high standard already. I know that this would require a lot of rewriting when implementing patches but on the other hand it's a lot easier to update patch code and sync trunk without mixing up too much code. For example the copy & paste patch is pretty huge and gives a good example of "external" files although it's not quite to the degree where I wanted to push it. Well I will just play around on my PC a little and see if this idea is actually realisable.
The dangerous thing with this approach is that you might get a lot of code duplication : each time a patch author wants to update the basic behaviour, he might duplicate the current trunk function, then update this copy, with a new name. Then updates to the trunk won't be in the duplicated functions, and it might become unmaintainable as well.
But I don't have better suggestions about this problem, let's try and prey
A suggestion should be opening a SVN repository for ChrisIN, then ask authors to sync themselves their patchs with the ChrisIN like we do with the trunk. But this might result in another problem the MiniIN had : the code will progressively become totally impossible to sync with the trunk.