Over watch for Conquer

[Epic-Chaos]

For any one that has played counter strike and knows what Over watch is thinking about making something sorta like that xD need some opinions.

[Spirited]

Originally Posted by Epic-Chaos

For any one that has played counter strike and knows what Over watch is thinking about making something sorta like that xD need some opinions.

It might help for those who haven't played to explain what over watch is.

[Aceking]

Ever played a game where after you died you then took the perspective of another player and could see everything they can? Pretty much that

TQ obviously had something similar with their arena system.

[Spirited]

Originally Posted by Aceking

Ever played a game where after you died you then took the perspective of another player and could see everything they can? Pretty much that

TQ obviously had something similar with their arena system.

Ohhhh - I see. I do something like that with my invisibility command. Basically, my screen system works where if a player isn't in the player's screen dictionary, the player is added an the players swap spawn packets. If the player is invisible, the invisible player simply does not send the spawn packet or any action packets.

[Aceking]

Originally Posted by Spirited Fang

Ohhhh - I see. I do something like that with my invisibility command. Basically, my screen system works where if a player isn't in the player's screen dictionary, the player is added an the players swap spawn packets. If the player is invisible, the invisible player simply does not send the spawn packet or any action packets.

Yeah pretty much. Except I assume he wants to have the invisible person basically 'share' the same character, just the visitor wont have any controls.

Almost like the ghost character would receive and send all the same packets (spawn packet etc) as the viewing character.

[Y u k i]

Originally Posted by Aceking

Yeah pretty much. Except I assume he wants to have the invisible person basically 'share' the same character, just the visitor wont have any controls.

Almost like the ghost character would receive and send all the same packets (spawn packet etc) as the viewing character.

I tried forever to achieve something like that, never found a way to make a packet do the client for example a jump

[pro4never]

There is a way to force the character to jump from new clients. I believe it had to do with how interactions function because 'holding hands' or w/e forced you to jump when your partner did the same.

I don't know of a way to make it work in pre interaction based clients but that would work.

You'd just spoof your character ontop of theirs basically and view all of their actions. It's kinda pointless though. best to just make yourself invisible to others and then teleport ontop of them to see what they are doing.

Hell even a /follow x command that teleports you wherever they go would be useful for following a botter/speedhacker that moves too quickly but regardless... OP has not been very clear about the exact functionality of the system he wants.

[Y u k i]

Originally Posted by pro4never

There is a way to force the character to jump from new clients. I believe it had to do with how interactions function because 'holding hands' or w/e forced you to jump when your partner did the same.

I don't know of a way to make it work in pre interaction based clients but that would work.

You'd just spoof your character ontop of theirs basically and view all of their actions. It's kinda pointless though. best to just make yourself invisible to others and then teleport ontop of them to see what they are doing.

Hell even a /follow x command that teleports you wherever they go would be useful for following a botter/speedhacker that moves too quickly but regardless... OP has not been very clear about the exact functionality of the system he wants.

Teleporting isnt smooth. Just my main point about having a forced jump.

[Spirited]

Originally Posted by Aceking

Yeah pretty much. Except I assume he wants to have the invisible person basically 'share' the same character, just the visitor wont have any controls.

Almost like the ghost character would receive and send all the same packets (spawn packet etc) as the viewing character.

Ohhh, I see. There are ways you can do that. You'd could remove the player's mesh so the character doesn't show on the player's screen, add invisibility to the player so the other people can't see it or it's shadow, and you'd send some type of movement packet to move the character.

[Aceking]

My thinking was adding a small method to the end of the process packet method.
Add in a check for someone 'ghosting' that player, if the check is true then also send the packet being processed to the ghosting player. Probably just change the UID of the packet to that of the ghosting player.

I would also probably add a check to the beginning of the process packet method, and if a character is 'ghosting', then to not process any packets originating from their client.

Obviously the system is a little more complicated than that, but I don't see why this wouldn't work in theory.
And because you are receiving every packet from the other client, you are essentially emulating their client.

I know of some other games that did something similar, where you could 'login' to any broadcasting player and watch what they do.

Hmmm, gives me a pretty fantastic idea for a broadcasting system that I may have to investigate.

[ImmuneOne]

Originally Posted by Aceking

My thinking was adding a small method to the end of the process packet method.
Add in a check for someone 'ghosting' that player, if the check is true then also send the packet being processed to the ghosting player. Probably just change the UID of the packet to that of the ghosting player.

I would also probably add a check to the beginning of the process packet method, and if a character is 'ghosting', then to not process any packets originating from their client.

Obviously the system is a little more complicated than that, but I don't see why this wouldn't work in theory.
And because you are receiving every packet from the other client, you are essentially emulating their client.

I know of some other games that did something similar, where you could 'login' to any broadcasting player and watch what they do.

Hmmm, gives me a pretty fantastic idea for a broadcasting system that I may have to investigate.

Sounds messy.

[Y u k i]

Originally Posted by Aceking

My thinking was adding a small method to the end of the process packet method.
Add in a check for someone 'ghosting' that player, if the check is true then also send the packet being processed to the ghosting player. Probably just change the UID of the packet to that of the ghosting player.

I would also probably add a check to the beginning of the process packet method, and if a character is 'ghosting', then to not process any packets originating from their client.

Obviously the system is a little more complicated than that, but I don't see why this wouldn't work in theory.
And because you are receiving every packet from the other client, you are essentially emulating their client.

I know of some other games that did something similar, where you could 'login' to any broadcasting player and watch what they do.

Hmmm, gives me a pretty fantastic idea for a broadcasting system that I may have to investigate.

Nothing wrong with your idea. however, the client sends packets if you jump not jumps if you send a packet :3

[ImmuneOne]

Originally Posted by Y u k i

Nothing wrong with your idea. however, the client sends packets if you jump not jumps if you send a packet :3

I'm seriously doubting you ever tested that lol..

[Aceking]

Originally Posted by ImmuneOne

Sounds messy.

It could be, then again it might not be too bad. Hard to say for sure without testing it. I think the messy part would be determining which actions are your own or the emulated client's.

[ImmuneOne]

Originally Posted by Aceking

It could be, then again it might not be too bad. Hard to say for sure without testing it. I think the messy part would be determining which actions are your own or the emulated client's.

You are all looking at it too complex while it's really simple, that's the problem here. The spectator shouldn't be able to view more than his public activity; movement, interactions and character modifications.