Auto kill game process
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
The issue names no files or tests, so first locate the game and engine message-handling or process-lifecycle entry points. Verify how missed messages are detected, then confirm the intended ping and timeout behavior, including the unresolved 10-second value; done means an unresponsive process exits with an error after the agreed timeout.
Written by the indexing model from the issue text.
Description
If the game or the engine doesn't receive any messages for over a second then send a ping, if it doesn't receive a message for over 10? seconds, then exit with an error
- Dominant language
- C++
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Die4Ever/AsyncGameEngine
-
Better frameworkOpen
Difficulty 5/5 Over a week Newbie friendliness 18/100
Die4Ever/AsyncGameEngine#18 · 2 comments ·
-
Green threadsOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
Die4Ever/AsyncGameEngine#15 ·
-
ProxiesOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
Die4Ever/AsyncGameEngine#14 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Die4Ever/AsyncGameEngine#13 ·
-
FramePacer classOpen
Difficulty 5/5 Over a week Newbie friendliness 15/100
Die4Ever/AsyncGameEngine#12 · 1 comment ·
All issues in Die4Ever/AsyncGameEngine
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
(S1 - Need confirmation)
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
CleverRaven/Cataclysm-DDA#88974 ·
Maintainers usually reply within 1 day
-
comp-mysql
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ClickHouse/ClickHouse#124749 ·
Maintainers usually reply within 1 day
-
Status: Needs confirmation Status: Needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day