Jump to content

Kyler

Members
  • Posts

    1
  • Joined

  • Last visited

Posts posted by Kyler

  1. Hey, all.

     

    A long time player here, but first time posting.
     

    I'm finally coming out of the shadows to study the code base behind OpenRCT2 and contribute myself if possible.

     

    A potential feature I have in mind to implement while studying the code is to add an option where mazes can't be opened unless there's a way from the entrance to the exit.

    I know the algorithm for this feature is pretty straightforward, but I'm not sure if the current codebase can handle it.

    I was wondering if you could give me your thoughts on the following:

     

    • Whether the suggested feature is theoretically feasible with the current implementation of the data structure for mazes in OpenRCT2.
    • Whether it is possible to implement this feature as an option so that any current non-solvable mazes people have purposely made do not become "invalid" overnight.
    • Whether it would be better to develop this feature as a plugin rather than directly into the source tree. (and feasibility)

     

    I'm really excited to hear your input on this. Thanks for your time!

    • Like 1
×
×
  • Create New...