ReplayMod

Replay Mod Forums

  1. Home
  2. Feature Requests
  3. Don't add certain Replay restrictions.
Don't add certain Replay restrictions.
    • User
    • 37 forum posts
    User668
    #1

    Aug 24 15, 12:25 PM | Last edited: Aug 24 15, 12:37 PM

    I think the Replay restrictions "no_noclip", "only_first_person" and "only_record_player" would destroy big parts of the Replay Mod.

    "no_noclip" is OK

    Link 1
    Link 2

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

    Aug 24 15, 12:43 PM | Last edited: Aug 24 15, 12:44 PM

    I don't think it will "destroy" parts of the Replay Mod. Big servers usually don't care about those restrictions, and some of them (restrictions) can be useful for medium/smaller servers. After this Replay Mod will be probably allowed on more servers as server owners will have more control. But feel free to change my view. :)

    • User
    • 37 forum posts
    User668
    #3

    Aug 24 15, 12:46 PM

    I think some little Server owners will just add this to their Servers without even thinking or knowing what the Replaymod does. And "only_first_person" and "only_record_player" would be a big restriction.

    • Moderator
    • Beta Tester
    • 212 forum posts
    User26

    in response to User668

    #4

    Aug 24 15, 12:58 PM

    User668
    I think some little Server owners will just add this to their Servers without even thinking or knowing what the Replaymod does. And "only_first_person" and "only_record_player" would be a big restriction.

    I don't think most of "smaller server" owners know how to send/edit custom packets to client. If they do, I don't think they will add anything without knowing what it does.

    • User
    • 37 forum posts
    User668
    #5

    Aug 24 15, 01:07 PM

    Thats right. But if it would get a Bukkit, Spigot, Sponge... Plugin almost everyone would be able to do it. And I think many bigger Server Admins also don't know hat to send/edit custom packets to clients.

    • Moderator
    • Beta Tester
    • 212 forum posts
    User26

    in response to User668

    #6

    Aug 24 15, 01:18 PM | Last edited: Aug 24 15, 01:23 PM

    User668
    Thats right. But if it would get a Bukkit, Spigot, Sponge... Plugin almost everyone would be able to do it. And I think many bigger Server Admins also don't know hat to send/edit custom packets to clients.

    Fair point! As long as there are no popular plugins to do it we won't see many servers with restrictions. But still i think every server owner should be able to restrict things like that. It's their server, their rules. :)

    Edit: Final opinions I will leave for devs. They decide about future of the Replay Mod.

    • User
    • 37 forum posts
    User668
    #7

    Aug 24 15, 01:20 PM | Last edited: Aug 24 15, 04:27 PM

    Thats what I also think, but the "only_first_person" and "only_record_player" things are a bit ... strange?

    • Developer
    • 1883 forum posts
    User10

    in response to User668

    #8

    Aug 24 15, 03:42 PM | Last edited: Aug 24 15, 03:56 PM

    User668
    Thats what I also think, but the "only_first_person" and "only_record_player" things are a bit ... strange?

    I added those with Wynncraft in mind. Wynncraft controls where the player can move / what they can see on may occasions (e.g. you may not climb over mountains or walk into certain caves) and the ReplayMod is not allowed because in the Replay Viewer you can just go wherever you want without getting teleported back.

    I'm currently building plugins for Bukkit, Sponge and BungeeCord (might also add LilyPad forget about that, that's not how LilyPad's supposed to be used, just use the Bukkit plugin for it). Due to the fact that server owners have to install an extra plugin to restrict the mod they for one have to know of its existence and also have to have a reason that makes it worth to install an additional plugin.
    You can currently divide servers into two groups: Those that allow the mod and those that ban it completely. With the plugins the second group is split into banning it completely and restricting it's functionality, the first group of servers stays the same because they have no reason to install one of the plugins.