6 ms·
OpenRCT2 was a direct derivative of RCT2 at first, to the point it would just directly call into the game executable everywhere. See e.g: https://github.com/Op
by Starlevel004 10mo ago
OpenRCT2 was a direct derivative of RCT2 at first, to the point it would just directly call into the game executable everywhere.
See e.g: https://github.com/OpenRCT2/OpenRCT2/commit/643db7ae017e04d13980031b449d747e3bf89c22 https://github.com/OpenRCT2/OpenRCT2/commit/643db7ae017e04d1...
- matheusmoreira 10mo agoI see. Yeah it's hard to defend that. The correct way to do it would be to reverse engineer the game and produce a clean room implementation.
- estimator7292 10mo agoThat isn't derivative. That's a plugin. At that point if OpenRCT2 is calling into the original, intact binary, there can be no infringement. You're just running the executable as provided and your computer just so happens to have another program running in the same memory space.