| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
- Aligned stuff
- Added style to use monospaced font in the code editor textarea
- Added label to the environment dropdown
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
digiline_send(), move on_updated_from_nodedb to advtrains table
|
| |
|
|
|
|
| |
distance-based approach or minetest.is_block_active() if available
See also https://github.com/minetest/minetest/pull/10897
|
| |
|
|
|
|
|
|
|
|
| |
If advtrains_train_track is disabled, don't register any tracks that use
its model like the LuaATC automation rail, point speed restriction rail,
station/stop rail.
For LuaATC, the definition for firing an event when a
train runs over the rail needs to be moved into the common defs so that
other mods like linetrack can use that as an interface.
|
| | |
|
| |
|
|
| |
for loops don't work with manipulating i
|
| |
|
|
| |
in luaatc rails
|
| |
|
|
| |
than the atlatc scheduler) and document new atlatc functions
|
| |
|
|
|
|
|
| |
After successfully registering newly-placed ATC rails in the nodedb, the rail's after_place_node() callback
(local apn_func()) immediately cleared it again by passing a "node" object that was actually a player object
and thus had no "name" or "param2" to ndb.update(), which it handled how it should not in this situation.
Since those ndb.update calls were unnecessary anyways, I removed them completely.
|
| |
|
|
|
|
|
| |
duplicate "message" to "msg"
make operation panel "cracky"
remove inexistent dtime_s parameter
add bones:bones to the list of not_blocking_trains nodes
|
| | |
|
| | |
|
| |
|
