1.7.10 has not been getting much love, it might not even launch (I haven't tried). These kind of issues are generally easy to fix but requires starting the game on each version to find them (so don't be surprised if you start 1.10.2 and it immediately crashes not all versions are tested). We've been making more use of Mixins in general, this item has a broad range but should your game just crash when you launch it, then it's probably because of this. It should all be wonderfully compatible but better be safe than sorry: Backup your replays, you have been warned. There have been some changes to the replay file format. temporarily select a different encoding preset)
Video rendering (should now be a lot quicker on most cards), you might have to reset your ffmpeg arguments (i.e. Movement of the camera and triggering of keyboard shortcuts in replays Recording of server-side resource packs start of recording and loading of replays (until there's a world visible), with and without other mods, singleplayer and multiplayer The initial handshake at the start of a replay, i.e. Specifically these things have undergone significant changes compared to 2.1.4 and need to be tested on all versions: Also always make sure you're actually using the latest version (linked above). When reporting an issue for these, in addition to the usual guidelines, please clearly state your RM version in the title of the thread. Update: These snapshots are now outdated, use the ones from the Download page.Īll the usual Minecraft versions are available in addition to 1.14 1.14.1 1.14.2: Simply change the "1.14" "1.14.1" "1.14.2" in the url to whichever version you're looking for. Since we have a single codebase for all supported MC versions, any version may break when I touch something and I really can't test all 11 supported versions after every tiny thing I change.
There have been a few quite substantial changes to parts of the RM. I could use a bit of help testing the (soon to be) 2.2 version of the ReplayMod before putting out the first pre-release though. OK, I've more or less got the update to 1.14 at a point where one can actually run it, so I've decided to skip 1.13 for now (or maybe forever).
0 kommentar(er)
