You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The fix in #3882 fixes the reported problem. However, as it is now, there's another problem.
Use the savegame provided in #3882 and build a road over the crossing, then remove it again. Only the road up to the crossing is removed. In 1.0 the entire road, except the crossing, is removed.
The patch will make it that way again.
When building a similar crossing with rails 1.0 acted similarly. Now it will also stop before the crossing. However with rails this is a different thing since a train can't drive over such a crossing anyway. The behaviour matches that of building rails now. I think that part is fine as it is now.
For the next time, please try to keep each error independent. In this case, the title gives no clue what the issue is about, and neither did the description.
We had to re-construct the problem of #3882 first, understand the solution used then, before we could even read this error.
If you had made a better description, and given short summary of the situation and the thing you wanted to change, it would have saved us a few hours.
Of course, it is good (recommended even) to mention other issues in the text.
Summary:
In #3882, when removing a stretch of road, depending on the direction of removal, you got a different error. To preserve the important error 'road owned by other player', the removal was aborted when encountering that error.
Here, the aim is to continue removal again for roads only.
I first considered to request re-open of the old report since this really is a follow-up report, the issue reported here is caused by the fix used for the old report.
However I decided not to do that. While the decision was made I somehow was under the impression that I couldn't comment and attach into a closed report. I can't remember how that happened. Under that impression I would have had to wait for the re-open request to be processed, but I wanted to get the issue written down and done.
This caused the bad subject of the new report.
I didn't notice that the description of this report, combined with the description of the previous report, is also unclear. Of course everything was clear to me, but since you weren't involved with the previous fix it was all new to you.
So you want a completely separate report for every issue, even if it's directly related to a recent report?
Krille opened the ticket and wrote:
Attachments
Reported version: trunk
Operating system: All
This issue was imported from FlySpray: https://bugs.openttd.org/task/3971
The text was updated successfully, but these errors were encountered: