Replay Mod Forums

Multiplayer day change/players not recorded.
    • User
    • 13 forum posts
    User326
    #1

    Aug 13 15, 09:19 PM | Last edited: Aug 13 15, 09:21 PM

    I have a 10:34 minute recording, and here are some the issues I ran into after looking at it in the Replay Mod. (This was done on multiplayer server).

    Only I am visible, the other players for some odd reason are simply not visible (They teleported to me after I joined the server, so may that be what caused it? There interactions are recorded, but not the player themselves).

    It also seems that with shaders (even when off, and I know its not a compatible thing atm, but I'll just mention it), is when a player has his personal time set on a server, like using /ptime . So for example if the server time is 6AM, and the player changes his personal time to 9PM, its going to at a 1 second interval go to 6AM and then back to 9PM, repetitively throughout the recording, until you start the game again without shaders mod.


    • Moderator
    • Beta Tester
    • 249 forum posts
    User20
    #2

    Aug 13 15, 09:22 PM

    I expired player invisibilty before as well. Please try to restart your minecraft and see if it is still a thing.
    You could also share the Replay with us, so we can see if we are having the same issues.


    • User
    • 13 forum posts
    User326

    in response to User20

    #3

    Aug 13 15, 09:32 PM


    I expired player invisibilty before as well. Please try to restart your minecraft and see if it is still a thing.
    You could also share the Replay with us, so we can see if we are having the same issues.

    Yeah, restarting does not help. Is it possible because they weren't at the location I was upon join? (I imagine this shouldn't be an issue, I'll try getting more recordings in multiplayer and see what happens).


    • User
    • 13 forum posts
    User326
    #4

    Aug 13 15, 09:39 PM | Last edited: Aug 13 15, 09:56 PM

    Okay, just attempted to create another recording, and it didn't even record my player movements/player.

    Test_1: (Leave server, enable record server, join server, (using Forge))
    Actions: Join X server, moved to a secondary hub server, then teleport to a "game" server. My skin isn't visible (recurring issue I had before when leaving a server and rejoining).
    No player data recorded (might not be related to ReplayMod because of the skin issue, but there are so many parties which may be causing the issue its not really something worth looking into I'd imagine.

    Test_2: (Relaunched MC, skin is shown in-game).
    Actions: I walk around, leave server.
    Recording: (My player movements are all recorded). No other players are recorded. V1.01 ReplayMod

    Test_3: Okay, just tested another server (Hypixel), and no issues are present with players in the recording. What could cause this?
    The server does do these modifications to player tags: http://i.imgur.com/CUqkqZr.png - But I highly doubt that causes an issue.


    • Developer
    • 1883 forum posts
    User10
    #5

    Aug 14 15, 11:10 AM

    What server are you talking about so we can try ourselves?



    • User
    • 13 forum posts
    User326
    #6

    Aug 14 15, 07:11 PM

    play.mcoldtown.com


    • Developer
    • 1883 forum posts
    User10
    #7

    Aug 14 15, 08:00 PM

    Thanks, I'll investigate once I'll find time to do so. We'll inform you once we know more / it is fixed.


    • Developer
    • 1883 forum posts
    User10
    #8

    Aug 18 15, 07:06 PM | Last edited: Aug 18 15, 07:07 PM

    The server at play.mcoldtown.com seems to send PlayerListEntry packets before sending the JoinGame packet which interferes with the modded negotiation of Forge. This is an issue of Forge (which can be solved by either, the server and/or Forge).
    Either way we will not actively try to fix this as it's an edge case of the protocol where both the server and forge act incorrect (It is general standard to not send the PlayerListEntry packets before the JoinGame packet even though the vanilla client seems to accept both, so Forge is probably not going to fix it)

    TLDR: This is up to the server (or less likely forge) to fix and affects all forge clients (though I haven't tested that).