including ballturrets in the trunk
Posted: Sat May 24, 2008 9:26 am
A small suggestion of mine:
I have occasionally come across an OXP which uses the ballturrets from Behemoth.oxp in a false reference. Which means: The OXP-author erroneously assumed that the ballturret is part of the Oolite distribution, not realising that in his case it actually came from behemoth.oxp. Which means that for somebody who hasn't installed behemoth.oxp, the turrets won't be there.
Faulty OXPing, I know.
But as ballturrets are used quite commonly I also can understand why somebody would mistakenly believe they are part of the game.
Therefore I suggest that the original ballturret from behemoth.oxp is included in the next release of Oolite itself, as sort of a resource for scripters. This requires the inclusion of the ballturret-entry in shipdata, ballturret.dat and turretskin.png. This would heal some broken references in a couple of OXPs, without doing any harm to those OXPs whose authors have taken the time to include (and hopefully rename!) the files themselves.
I have occasionally come across an OXP which uses the ballturrets from Behemoth.oxp in a false reference. Which means: The OXP-author erroneously assumed that the ballturret is part of the Oolite distribution, not realising that in his case it actually came from behemoth.oxp. Which means that for somebody who hasn't installed behemoth.oxp, the turrets won't be there.
Faulty OXPing, I know.
But as ballturrets are used quite commonly I also can understand why somebody would mistakenly believe they are part of the game.
Therefore I suggest that the original ballturret from behemoth.oxp is included in the next release of Oolite itself, as sort of a resource for scripters. This requires the inclusion of the ballturret-entry in shipdata, ballturret.dat and turretskin.png. This would heal some broken references in a couple of OXPs, without doing any harm to those OXPs whose authors have taken the time to include (and hopefully rename!) the files themselves.