Replay Mod Forums

Uploading bug post-crashing
    • User
    • 9 forum posts
    User2806
    #1

    Aug 16 15, 12:04 AM | Last edited: Aug 16 15, 12:10 AM

    So, I was uploading a replay, and the game crashed while uploading (it was at 27%). When I came back on, it said the Replay was already uploaded, and refused to let me reupload it. I couldn't find any trace of it in the Replay Center, however (maybe it doesn't display your own uploaded replays?), much less a way to delete it so I could reupload. It might be listed as "Hypixel Warlords - CTF" in your database, should you want to delete it.

    EDIT: It says I am not using any storage on my profile page, and I have 0 uploaded Replays. Is there something you could do manually to unblock me?


    • User
    • 9 forum posts
    User2806
    #2

    Aug 16 15, 12:09 AM

    Things I've already tried:

    Cutting and repasting in the Replays folder.
    Copying to Documents folder, deleting Replay in-game, then inserting the .mcpr back in.


    • User
    • 9 forum posts
    User2806
    #3

    Aug 16 15, 12:13 AM

    Here's the crash report: http://pastebin.com/vbQXf3cn


    • Developer
    • 818 forum posts
    User1
    #4

    Aug 16 15, 12:35 AM

    Hello KiloGraham,

    thanks for the crash report, we'll investigate that. In the meantime, you can simply delete the file called "uploaded" from the config folder in your .minecraft directory to allow you to upload the file again (might need a Minecraft restart).


    • User
    • 9 forum posts
    User2806

    in response to User1

    #5

    Aug 16 15, 12:43 AM


    Hello KiloGraham,

    thanks for the crash report, we'll investigate that. In the meantime, you can simply delete the file called "uploaded" from the config folder in your .minecraft directory to allow you to upload the file again (might need a Minecraft restart).

    Thanks! That did the trick.



    • Developer
    • 1883 forum posts
    User10
    #6

    Aug 16 15, 10:24 AM | Last edited: Aug 16 15, 10:27 AM

    Do you remember what you typed into the description box? (more importantly how you typed it? when you placed new lines, how you removed them?)
    This kind of exception should be reproducible, however even though trying for 10 minutes I couldn't get it to crash.

    // Edit // Nvm, just got it to crash by spamming the keyboard, now I just have to find out what I spammed.


    • User
    • 9 forum posts
    User2806

    in response to User10

    #7

    Aug 16 15, 06:25 PM | Last edited: Aug 16 15, 06:27 PM


    Do you remember what you typed into the description box? (more importantly how you typed it? when you placed new lines, how you removed them?)
    This kind of exception should be reproducible, however even though trying for 10 minutes I couldn't get it to crash.

    // Edit // Nvm, just got it to crash by spamming the keyboard, now I just have to find out what I spammed.

    I had quite the long description when it crashed. I believe it was 5 lines long, and it was 7 lines when I collapsed lines 2, 3, and 4 into line 2. (All of the lines exceeded the box, and had to use the arrow keys to view all of it.)

    This, by the way, is after a failed upload of the same Replay, when it displayed the "Description is too long" error when it finished. I tried again after trimming some text from several lines (removing redundant/not needed words), and that was when it crashed.

    After I cleared my client's list of uploaded Replays , the Replay uploaded fine (this time, I used a much shorter description with only 3 lines).

    (All of the info above I'm recalling in retrospect, may not be 100% accurate.)

    Could you add the character limit for descriptions to the documentation? Would be appreciated


    • Developer
    • 1883 forum posts

    Spoiler: Quote


    The bug should be fixed with the next version (1.0.3).
    As for the character limit: @User1


    • Developer
    • 1883 forum posts
    User10
    #9

    Aug 16 15, 10:37 PM

    This should be fixed with the new version (1.0.3). If the crash doesn't happen again within the next few days, I'm going to assume it was fixed.