Determine how guided/seeking weapons will work in multiplayer.

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
game-dev, networking

Research direction

No files, tests, or entry points are identified in the issue. Start by tracing the multiplayer firing flow and the locking/seeking weapon behavior described in the repository, then define and document ownership, synchronization, and behavior for guided weapons; done means the multiplayer design is agreed and its implementation scope is clear.

Written by the indexing model from the issue text.

Description

Determine how guided/seeking weapons will work in multiplayer. I believe they will need to be controlled by the client that fired them.

Dominant language
C#
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NTDLS/AxisEngine

All issues in NTDLS/AxisEngine

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.