Valid Record & Replay feature (NOT video)

[Maf 32,300]

 

Topic merged

 

Video recording isn't possible due to technical limitations. If your PC is powerful enough, you can do it yourself using external software.

[Okami 3,041]

Replay System

 

I got this idea from the Nintendo Switch. On the Nintendo Switch, there's a special button where if you click and hold it for a short time, the 30 seconds before you pressed the button are saved to a gallery.

 

I think Tanki can do something like that. If you want to record a great killstreak, a perfectly executed parkour stunt, or anything else, you can save it to your personal gallery.

 

In the personal gallery, you can add some as favorites, post them on social media (YouTube, Twitter, Facebook, Insta, etc.), or upload it to an online library.

 

What's this online library? A system where players can post their replays, and other people can like/dislike and comment on those replays.

[Hate 5,582]

 

Topic merged.

[Aigaion 636]

...screen recorders ain't that hard to get, on windows 10 just hit WIN+G, but I do see the point of having some sort of "server replay" 

Edited June 22, 2019 by Aigaion

[pro-AGFR 32]

A record & replay system could help the game in many ways. I'm not talking about recording a video of the game, there are other programs to do that already. The system I suggest will have many applications beyond recording videos for youtube, as well as solve the trust problems with spectators. I'm talking about recording what actually happens in the battle, every single event (key presses of players, location updates, boxes dropping and getting picked up, etc). The result should be a code that looks somewhat like what's in the spoiler: (simplified)

 

 

 

[00:00:00:00] Join: SwiftSmoky Blue (Viking, Thunder...)

[00:00:00:00] Join: Nives Red (equipment...)

[00:00:05:00] Spawn: SwiftSmoky (x:10.0, y:12.0125, z:-40.0, r:3.14159265359)

[00:00:05:00] Spawn: Nives (x:23.5, y:12.0125, z:20.0, r:1.57079632679)

[00:00:05:42] Move: SwiftSmoky (Hold:Down,Hold:Left,Hold:Z)

[00:00:05:58] Leave: Nives

[00:00:07:21] Move: SwiftSmoky (Release:Down,Release:Left,Release:Z)

[00:00:09:33] Chat: SwiftSmoky TeamChat " :("

[00:00:09:40] Join: Nives Spectator

[00:00:10:02] Drop: RepairKit (x,y,z)

[00:00:14:14] Leave: SwiftSmoky

 

Of course this is just a simplified human readable version of the code just to demonstrate the concept. Basically a log of a bunch of the info the server receives from the clients and sends to them.

I don't know how big these logs will get though, so the server might have to regularly delete old logs, maybe with an option to save battles and prevent them from deletion (with a limit of how many battles one player can save, and a delete option)

 

 

 

To avoid fake codes, the recorded battle codes should be saved only on the tanki server (not visible to the client at all) and should only be possible to load in the game using the battle ID (which is a part of the battle link). This is vital to prevent players from editing codes and making fake evidence to report players for cheating, fake chat announcements that look like the CM wrote them, etc...

There can be a button for loading recorded battles somewhere at the small buttons in the top bar. Then simply enter a battle ID / link, and the game will load the battle with the observer being in spectator mode.

There should be some video-like user interface so players are able to navigate to specific time in the battle without waiting and be able to replay it as many times as they want. Pressing P should freeze the battle. Or if no navigation interface, then at least chat commands.

 

Possible applications of this feature:

 

• Spectator mode is impossible to abuse since there's no advantage to be gained after the battle is already over. This means it's ok to make this feature publicly available and allow everyone to use spectator mode through it.
• The amount of special spectator accounts can be reduced to a minimum required for special helper positions such as streamers and mods which really need the ability to watch battles in real time. The rest will be doing great with the replay battle feature, spectator applications for youtubers won't be needed ever again. Spectator mode will become widely available while spectator violations will be completely eliminated.
• Players will be able to report cheaters without having to record a video of their battle, a link to the battle will be all the evidence they need. That makes reporting cheaters much more effortless (comparing to the way it's done now) which will encourage more players to report cheaters and will lead to much more effective elimination of cheaters from the game. Also, this way of reporting will be more reliable than a video which can be VERY EASILY faked (I won't explain here how since everyone will be able to see it and use this method. Sergei or mr.stiffler - you can contact me privately if you want to hear it).
• People will have the option to watch battles, events, parkour sessions, etc after they are over, from their preferred view (can focus on certain players or areas).
• Contest organizers can use this feature to check if someone used cheats in his contest entry. From the server's view cheaters will always be noticeable, as opposed to the way it looks in a video recorded from the cheater's view. (I could use this in the Parkour Survival contest, already caught one cheater without it but this feature would make my life much easier)
• Everyone will be able to record videos (and take screenshots) from spectator mode, and without worrying about finding a good time for a spectator to join their battle. People can have a clan battle and keep the battle link, and later replay the battle and record a video of it from spectator mode, that way they don't have to bring spectators to record the battle in real time and won't risk the possibility of the spectator helping one of the clans with useful information that he can see. Parkourists will be able to spend hours working on a trick without having to make their spectator spend so much time on recording their trick, they will only need to replay the battle and go to the time when they completed the trick successfully, and spend just a few minutes on recording it from spectator mode instead of watching hours of fails before it's finally done successfully.
• It will improve people's ability to get better recording since they will have an unlimited number of attempts to experiment with different ways to record their video and succeed in getting perfect timing and smooth motion with the spec camera.
• The ability to freeze the battle will be useful in videos and might have some other applications too.

EDIT:

 

Some good points people made in this topic:

• Recording every single battle can cause a lot of lag. So better make it off by default and make it possible to enable it for a battle upon creation or turn it on using a chat command inside the battle. And when reporting violators, using the /vote command will also turn on the recording. That way only very few battles will be recorded, the ones that really need to be recorded.
• People will be able to see private conversations from the opposite team if they use this feature, which means people should have some indication or warning before they join a recorded battle, like an icon in the battle settings row (though that one isn't very visible) or a warning message like before joining a parkour battle.

Yo, good idea. The same like on Wot and wotb. Edited June 22, 2019 by pro-AGFR

[Potdindy 866]

Great idea. Doing something like this might allow people to cast games, which might bring an older population into it, who enjoy the competitive aspect.

[Incorp 2,084]

This hadn't been a big problem, but with the extra spooky contest going on requiring you to get a triple kill with one shot it is a problem. Scenario: oh yes, you are juggernaut and killed three noobie wasps with a shot! You're about to take a pic but a viking was spamming kills. Your heart went down as the kill feed went up with the viking's kills. I suggest to let us scroll the kill feed like in the chat. What do you think?

[Spy 14,687]

12 minutes ago, Incorp said:

 

Topic merged.

[Incorp 2,084]

6 minutes ago, Spy said:

Topic merged.

I don't see what is similar to this idea. Mine doesn't record the battle...

[Spy 14,687]

Just now, Incorp said:

I don't see what is similar to this idea. Mine doesn't record the battle...

Did you read his idea?...

[Incorp 2,084]

7 minutes ago, Spy said:

Did you read his idea?...

I did but I didn't understand it

[Spy 14,687]

1 minute ago, Incorp said:

I did but I didn't understand it

All actions in battles will be "recorded" and presented via text, and that includes the triple kills you were talking about in your idea.

[pocrettttt 277]

Some times i dont know what exacly did so much damage to me, because multiples enemies shot me at once

It would be interesting if there was a mini graphic or damage numbers that lasts from the moment of your death to respawn and then disappears and appears again every time you die in this cycle

The "relevant" numbers will only be those of your damage received in the last 3 seconds

For example:

You died-

damages from 6 seconds ago : 1300 thunder: Not in graph

3 seconds ago: 200 firebird(normal turret damage type)

3 seconds ago: 600 tesla(normal turret damage type)

2.3 seconds ago: 900 railgun(crit type)

1 second ago: 3000 shaft(normal turret damage)

 

[Spy 14,687]

6 hours ago, pocrettttt said:

 

Topic merged.

[I_Lauv_You 221]

Would it ever be possible to "save" certain games you play in such a way you can go back and basically spectate the "replay" for whatever reason? But there would be a time limit so the files aren't so big? Whether it's to record your own rank, Parkour, game play, etc.

[NikmanGT 4,362]

44 minutes ago, I_Lauv_You said:

 

Post Moved