![]() ![]() This list is a reminder for the reviewers. Some things are not automated, and forgotten often. The "no buoy" and "no waypoint" should almost never be reached, but we already have error handling for this, so why not add a couple strings to be descriptive? Checklist for review ![]() I also added a ShowErrorMessage overload which simply takes a CommandCost instead of individual attributes of that object, per LordAro's request. This requires explicitly casting a few CommandCost arguments to determine which overload to use. Upstreams a JGRPP commit to add a specific error message, and builds off a commit to add a two-string error message. The same goes for sending buses to truck stations and vice versa. Using path signals here makes absolutely no difference in station performance.Players are often confused when they try and send an articulated road vehicle to a bay station, because the error message does not explain why the vehicle cannot use the station. Like with any other one-way track it is not necessary to use path signals in this case. This is due to the fact that this station is essentially incorporated into a single one-way track. This way trains delivering cargo will deliver it faster as well as loaded trains can leave faster.Īs you may have noticed, there are no path signals used in the example with path signals. It is a good practice to make the loading-exit and unloading-entrance lines to go straight into the station, while the loading-entrance and unloading-exit lines can loop around. While this benefit is very small in case of single stations, the Ro-Ro setup becomes far more effective with multi-platform stations (see below). The advantage of this station is that incoming trains don't have to wait for outgoing trains to leave.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |