diff options
| author | Y. Wang <y5nw@protonmail.com> | 2025-10-04 21:25:43 +0000 |
|---|---|---|
| committer | orwell <orwell@bleipb.de> | 2026-01-29 21:54:50 +0100 |
| commit | bb2e1241b73bb6250f3fa1778525eb58501e22b5 (patch) | |
| tree | 52c5201e333f9ed51e701c2d86204ca259c27036 /advtrains_interlocking/ars.lua | |
| parent | 862611d89b304c502dd600eed308eb4ad5fbf528 (diff) | |
Indicate routesetting trigger if a route is set
A player observed an issue with a certain setup where ARS is constantly
triggered and the route cannot (easily) be canceled. This patch helps
troubleshoot this issue by indicating the specific cause for
routesetting (in particular, which train triggered ARS).
Diffstat (limited to 'advtrains_interlocking/ars.lua')
| -rw-r--r-- | advtrains_interlocking/ars.lua | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/advtrains_interlocking/ars.lua b/advtrains_interlocking/ars.lua index 393878a..99401d4 100644 --- a/advtrains_interlocking/ars.lua +++ b/advtrains_interlocking/ars.lua @@ -70,6 +70,7 @@ ]] local il = advtrains.interlocking +local S = il.translate local function parse_trainlen(tlstr) mins, maxs = string.match(tlstr, "^(%d*)%-(%d+)$") @@ -385,7 +386,7 @@ function advtrains.interlocking.ars_check(signalpos, train, trig_from_dst) --atdebug("Ars setting ",rteid) --delay routesetting, it should not occur inside train step -- using after here is OK because that gets called on every path recalculation - minetest.after(0, il.route.update_route, sigd, tcbs, rteid, nil) + minetest.after(0, il.route.update_route, sigd, tcbs, rteid, nil, S("Train @1", train.id)) end end end |
