Jump to content

julman99

Members
  • Posts

    1
  • Joined

  • Last visited

Reputation

0 Neutral
  1. What if multiplayer timewarp is implemented as a shared timeline in this form: Imagine there are three players, A,B and C All three players start at the same time They can see each other and interact with each other, for example A can crash a rover into B and both of them will be affected by the crash. Now imagine the three of them go into Kerbin's orbit (without timewarp). Then A does a transfer to Mun and time accelerates to get into Mun Orbit While this was happening, B and C did not time accelerate, so they still see A doing the burn and then going away to the Mun in realtime. However, from A's point of view, he is already in the Mun. This is what each player would see at this point: A can see himself at the current time, and can see B and C positions in the past. KSP could render B and C indicating that is the position in the past for them. A is unable to interact with B o C since they are in the past, they are like ghosts. B and C can see each other and interact since they are in the same time, and they can see where A is in the future as well as A in the current timeline. KSP could provide an option for B and C to timewarp to A's current time, and that way they can catch up to A and interact with him. I think this mechanic could lead to very interesting gameplay. You can have a bunch of people trying to build a giant station in Jool, and each of them could be bringing pieces from Kerbin at their own pace, but in order to be able to dock to the station they need to timewarp to the "head" of the timeline. Tradeoff this approach has: What happens if B or C bumps into A while A is traveling to the Mun. KSP would be rendering A as a "past location of A", so it could actually make A to be completely on rails. Even if you crash into A with a huge ship, or even an asteroid, you will end up blowing up and A would be untouched If B decides to orbit the moon and timewarp to A's timeline, A will just suddenly see "past" B location catching up and then all of the sudden become "current B". I can't think about any other tradeoff now, but I am sure they may be more. What do you guys think?
×
×
  • Create New...