Combat - Basic syncing #652

starfi5h · 2024-02-10T02:14:50Z

This is a branch for combat framework and basic unit syncing.
Video demo: Ground Unit Syncing

The roadmap can be found here. The work includes in this PR:

Initial handshake

Sync battle settings
Rework the joining process to let the client load SpaceSector data from the host as it is imported from the save
Send SkillSystem data without projectiles during handshake to prevent error (CombatManager.SerializeOverwrite)

Basic syncing

Sync DF ground enemy create/destroy events (factory.enemyPool)
Sync DF ground units activate/deactivate event
Sync DF space enemy create/destroy events (spaceSector.enemyPool)
Sync DF space units activate/deactivate events
Sync DF planet base exp level and threat
Sync DF space hive exp level and threat
Sync loot and loot filter table

Mecha

Sync mecha shooting weapons
Sync mecha bombing
Sync mecha death and respawn animation
Sync mecha personal shield to block projectiles

Ground

DF aggro

Sync DF base awake events (player lock with weapon, player nearby, under attack)
Sync DF base threat and launch assault event
Patch DF unit to search for nearest alive mecha (sensor range)
Patch DF turret to search for nearest alive mecha (attack when within attack range or counterattack)
Sync the hatred targets changes so DF units are attacking the same target

DF/Building interaction

Sync building repair drone (not perfect)
Sync building kill event (server fully authorized)
Sync building reconstruct event

Space

Handle DFRelayComponent.RealizePlanetBase
Sync DFRelay ArriveBase/ArriveDock/LeaveBase/LeaveDock events
Sync Remove base pit event
Sync TryCreateNewHive, DispatchFromHive events
Sync Realize and open/close hive preview events

DF aggro

Sync DF hive awake events (player lock with weapon, player nearby, under attack)
Sync DF hive threat level and launch assault event
Patch DF unit to search for nearest alive mecha (sensor range)
Patch DF turret to search for nearest alive mecha (attack when within attack range or counterattack)

Temporarily Disable

Dark Fog communicator

Implement Detail

Dark Fog Ground Unit syncing

The goal is to let PlanetFactory.enemyPool stay in sync. So every function that call PlanetFactory.AddEnemyDataWithComponents and PlanetFactory.RemoveEnemyWithComponents need to approve by the server first.

For example, when a client sees an enemy reduce HP to 0, it will set the enemy to a frozen state and request the server to kill it. When the server receives the valid request, it will broadcast the kill event to clients. After receiving the event, the client will kill it and process the following effect.

Dark Fog Space Unit syncing

Similar to the ground unit, let SpaceSector.enemyPool stay in sync.

Here are patch to functions:

yellow check means it will broadcast in server and intercept in client.
orange block means it's disabled in multiplayer game.
prefix CSE_ is just for demo so they can be ignored.

Dark Fog Planetary Base Exp and Threat

The client doesn't update exp level and threat locally. It will wait for the server to send DFGUpdateBaseStatusPacket every 5s to update those values. The LaunchAsssult event is trigger by the server too.

Mecha

RemotePlayerModel.PlayerInstance now has controller member to use more vanilla properties.
The weapon is client triggered, that local will fire first then broadcast to other players.

CombatManager

This stores some players' variables that are frequently used in combat systems. For example, PlayerPosition cache the player position and states.
The positions of other players are using the delayed interpolated position therefore they may cause some distortion.

EnemyMananger

This stores the status of Dark Fog bases and hive, and sends updates to clients every 5 seconds.
Also, it has the common functions that will try to pre-assign the enemyId before creating the enemy.

Skill System

This system in the game manages all kinds of projectiles and stores the properties of the player.
The default player id is 1. In multiplayer it is changed to playerId. The local playerId will be Multiplayer.Session.LocalPlayer.Id.

Rework

GlobalGameDataRequest/GlobalGameDataResponse

When client join, after the initial handshake, it will now request the global data from the server first (History, SpaceSector, MilestoneSystem, TrashSystem). After those binary data are collected, the client will then proceed DSPGame.StartGameSkipPrologue to start the game loader sequence. Before GameData.NewGame, the client will import those binary data.

TrashSystem

Now trash will be separated into two types: Those that have lifetime (Dark Fog drop), and those that have no lifetime (normal). The Dark Fog drop are now partially syncing for clients to only sync on the drop on the local planet.

- Create/Remove of trash now have to approve by the server first - Planet trash will only send to the players on that planet

mmjr-x

I made it to file 116 of 152 however have to sleep soon so I will submit this as the first part.

Code looks good overall! Added a bunch of comments only almost everything are minor nitpicks, so take them with a grain of salt :)

NebulaModel/Packets/Session/GlobalGameDataResponse.cs

NebulaNetwork/PacketProcessors/Combat/DFRelay/DFRelayLeaveBaseProcessor.cs

NebulaNetwork/PacketProcessors/Combat/DFRelay/DFRelayArriveBaseProcessor.cs

NebulaNetwork/PacketProcessors/Combat/DFRelay/DFRelayArriveDockProcessor.cs

NebulaNetwork/PacketProcessors/Combat/DFRelay/DFRelayLeaveBaseProcessor.cs

mmjr-x · 2024-02-28T22:02:22Z