Sharing ownership between two players
Mantenedores costumam responder em até 2 dias
@NoelStephensUnity já está trabalhando nisso.
Desde 10/5/2023.
Avaliação
Esta issue ainda não foi avaliada.
Descrição
This is a follow up question after #2512, where @NoelStephensUnity helped me a lot with making a solid and smooth movement of an object by a player.
But since multiplayer games are about cooperation, carrying stuff together is one of the essentials features in our game.
I'd like to make it that when one player tries to carry a large thing, it struggles, whereas two can do it easier.
The problem is, they both should be able to move the object they are carrying. And they are client-side authoritative.
So I can't just change the ownership of the object, because another player is going to have a delay.
The only idea I have is to let them simulate locally object's state, ignoring the correct one from the server. And once they drop the object, it switched back to updates from the server. I think this should work, at least, I can't tell why not.
But I think I don't understand the solution @NoelStephensUnity provided me with to 100%. I see that it disables server updates and lets client simulate rigidbody, but it also handles the jitter problem by making sure that the authority is completely switched, and I just don't understand how I can make it more generic, so I could just toggle it when I need it.
Do you think it's going to work or I am completely wrong about the approach? Maybe it can be achieved easily?
If so, could you please you elaborate on your solution? As I said, I'd like to make it generic.
Thanks a lot!
- Linguagem predominante
- C#
- Estrelas
- 2.3k
- Forks
- 464
- Merge médio
- 2d 18h
- PRs com merge (30d)
- 15
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de Unity-Technologies/com.unity.netcode.gameobjects
-
NetworkList changes made since the last tick are applied twice on a newly synchronized clientAbertastat:awaiting-triage stat:reply-needed type:bug
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 55/100
Unity-Technologies/com.unity.netcode.gameobjects#4179 ·
Mantenedores costumam responder em até 2 dias
-
Dedicated server: mixed-authority NetworkObject is removed from NetworkTransformUpdate, so its owner-authoritative NetworkTransform never updates server-sideTalvez já em andamento @NoelStephensUnity assumiu há 10 dias. Abertastat:imported stat:reply-needed type:bug
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 68/100
Unity-Technologies/com.unity.netcode.gameobjects#4159 · 5 comentários ·
Mantenedores costumam responder em até 2 dias
-
NetworkAnimator: Conditional triggered transitions to Exit node log false errorsTalvez já em andamento @NoelStephensUnity assumiu há 195 dias. Abertastat:awaiting-response stat:awaiting-triage stat:Investigating type:bug
Unity-Technologies/com.unity.netcode.gameobjects#3912 · 7 comentários · 1 responsável ·
Mantenedores costumam responder em até 2 dias
-
Tracking type:feature-2.x
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 35/100
Unity-Technologies/com.unity.netcode.gameobjects#3870 · 5 comentários ·
Mantenedores costumam responder em até 2 dias
-
Tracking type:feature
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 48/100
Unity-Technologies/com.unity.netcode.gameobjects#3830 · 7 comentários ·
Mantenedores costumam responder em até 2 dias
Todas as issues de Unity-Technologies/com.unity.netcode.gameobjects
Issues semelhantes
-
area:frontend bug FE P3
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
klasolsson81/jobbliggaren#2010 ·
Mantenedores costumam responder em até 1 dia
-
[aw] Upgrade availableAbertaagentic-workflows untriaged
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 65/100
Mantenedores costumam responder em até 1 dia
-
area: homeblaze type: bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
RicoSuter/Namotion.Interceptor#630 ·
Mantenedores costumam responder em até 1 dia
-
Akka.Hosting enhancement
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
-
bug needs-triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
microsoft/microsoft-ui-xaml#12158 ·
Mantenedores costumam responder em até 1 dia