View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0021436 | AI War 2 | Gameplay Idea | Jul 31, 2019 4:04 pm | Dec 5, 2019 10:46 am | |
| Reporter | Chris_McElligottPark | Assigned To | Chris_McElligottPark | ||
| Severity | minor | ||||
| Status | closed | Resolution | won't fix | ||
| Summary | 0021436: Multiplayer: Make ship death scheduled. | ||||
| Description | One of the hardest things with desync-repair is going to be if a ship dies on a client and then we're trying to fix sync with it with the host that thinks it is still alive. For that reason among some others, we need to make it so that when a ship dies, it doesn't just get removed from the game right away. It should sit invisible and dead until the host generates a "this thing should now die and disappear for all of us" gamecommand that syncs things up. Assuming that such a command does NOT arrive for a client that thinks it has a dead unit on its hand, then the natural desync-repair process (detailed elsewhere) will come along and bring the unit back to life with minimal fuss. Note that we don't need to do this for shots or OtherEntities, because shots are not something that last long enough to worry about desyncs with, and OtherEntities are just wormholes that also should not possibly be able to desync since they don't change during gameplay. | ||||
| Tags | No tags attached. | ||||
| related to | 0021440 | resolved | Chris_McElligottPark | Multiplayer: ship desync detection code. |
| related to | 0022313 | closed | Chris_McElligottPark | Multiplayer: Make ship death propagate from any source (clients or hosts). |
| child of | 0021432 | resolved | Chris_McElligottPark | Multiplayer todo - parent issue. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Jul 31, 2019 4:04 pm | Chris_McElligottPark | New Issue | |
| Jul 31, 2019 4:04 pm | Chris_McElligottPark | Status | new => assigned |
| Jul 31, 2019 4:04 pm | Chris_McElligottPark | Assigned To | => Chris_McElligottPark |
| Jul 31, 2019 4:04 pm | Chris_McElligottPark | Relationship added | child of 0021432 |
| Jul 31, 2019 4:32 pm | Chris_McElligottPark | Relationship added | related to 0021440 |
| Dec 5, 2019 10:46 am | Chris_McElligottPark | Relationship added | related to 0022313 |
| Dec 5, 2019 10:46 am | Chris_McElligottPark | Status | assigned => closed |
| Dec 5, 2019 10:46 am | Chris_McElligottPark | Resolution | open => won't fix |
| Dec 5, 2019 10:46 am | Chris_McElligottPark | Note Added: 0054833 |
