dev:proposals:door_indexes
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
dev:proposals:door_indexes [2022-08-07 21:19] 56independent Add response to response to response to advtrains (note: I'm in a bit of a jokey mood because i binged hermitcraft and also in light of minecraft's recent events (1984 by Orwell)) |
dev:proposals:door_indexes [2022-08-07 21:21] 56independent [2022-08-07 17:49, orwell] If you're going for ISO8601, go all the way (also BST because i am a maniac) |
||
|---|---|---|---|
| Line 40: | Line 40: | ||
| This relies on a carriage index algorithm existing, but this should be relatively simple to implement by copying some code and writing some others, given that trains need to count their carriages for the '' | This relies on a carriage index algorithm existing, but this should be relatively simple to implement by copying some code and writing some others, given that trains need to count their carriages for the '' | ||
| - | ==== 2022-08-07 17:49, orwell ==== | + | ==== 2022-08-07t17:49+0100, orwell ==== |
| Advtrains has the functions and tools required to implement the position lookups you describe. The main issue (and also the reason why we don't have doors opening on both sides) is how the door opening/ | Advtrains has the functions and tools required to implement the position lookups you describe. The main issue (and also the reason why we don't have doors opening on both sides) is how the door opening/ | ||
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
