Replay Mod Forums

What's happening with replay mod development?
    • User
    • 10 forum posts
    User9460
    #1

    Mar 11 16, 01:48 PM

    The last published version was last year, it wasn't updated to forge 1.8.8 and neither to forge 1.8.9. It has many open bugs reported https://www.replaymod.com/forum/?category=2 and one of them corrupts our recording randomly when we leave the server (it won't transform the tmcpr file into a mcpr).

    Why aren't you updating this awesome mod anymore? Don't let it just die like RedPower, you created an awesome tool but it's not over, you need to update it...


    • Moderator
    • Beta Tester
    • 212 forum posts
    User26
    #2

    Mar 11 16, 02:01 PM

    Recent state of development progress has been mentioned in this post.
    1.8.8 or 1.8.9 versions are not planned (from what I know).
    I guess something like 85% of threads in bug reports category are not really Replay Mod bugs (most of them are repeated/not related to Replay Mod).

    Tl;dr Replay Mod is not dead.


    • User
    • 10 forum posts
    User9460
    #3

    Mar 11 16, 02:35 PM | Last edited: Mar 11 16, 02:36 PM

    Hm so the devs are working on replaymod 2.0, it would be nice to keep everybody updated on the homepage, an post informing the progress and what's happening every often.

    About the bugs, I don't notice many bugs myself only these two:

    1) Sometimes the replay is not saved to mcpr and remains on tmcpr forever, so we can't use it.


    2) When I'm working on a replay I tend to replay it many times to adjust the keyframe timings and camera angles, the problem is that replaymod gets heavier on every rewind, after some rewinds it starts getting huge fps drop and I have to reopen the game. It happens even if I set the game to use 10GB of RAM, this indicates a resource leak somewhere.

    That bugs exists for a long time, the resource leak is annoying but we can deal with it easily restarting the game, but when the replay isn't saved correctly it's a pain to make it work. This was reported many times but was never fixed