Skip to content

LTN Space Age - Rewrite #350

@Alzurana

Description

@Alzurana

TL;DR
Rewrite efforts for 2.0 SA should be considered when talking about LTN continuation to respect Opteras wishes.

What ?
Going through the issues and Opteras replies it feels to me as if nobody is really hearing what the original author expects from a continuation of the LTN Mod. So I'll list what I gathered to hopefully guide the discussion into the right direction:

  • A port with the old code is not desired as it would drag out old concepts that do not fit onto the new design of the game
  • Pull requests that just "make it work for 2.0" are also not desired (I think)
  • Optera mentioned that they have not been approached for a proper, formal takeover, yet. But I don't know if that is outdated by now.
  • 2.0 LTN should ideally rebrand slightly to differentiate it from the original and make it clear that it is a rewrite. Suggestion: LTN 2.0 Space Age
  • Performance considerations for a rewrite: Pathing is now the biggest cost. Trains that return to a depot are worse for performance, not better. The whole depot concept needs to be re imagined therefor. Trains could move to a provider station right away, waiting to be reloaded. I feel like this breaks LTNs feature that a single station could be both, provider and requester. I would propose that trains stay in their dropoff station either until another request is made or another train needs to enter it, only then going to a depot to make space. Maybe make this configurable so players have the ability to choose classic or new behavior.
  • It would be beneficial if a rewrite for 2.0 could make use of icons and art that 1.1 already provides.
  • An LTN combinator could be included or provided as a separate module.
  • An LTN interface could be included or provided as a separate module.

-> When I first thought about this I had the idea of setting up all LTN activity as train interrupts. However, when I looked over the lua documentation I did not see sufficient ability to insert, create, manage or trigger interrupts via the lua interface. Meaning classic LTN dispatch might still be the only option.

Why ?
I hope this is more aligned with what Optera would agree with.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions