Implement a hook point for when we're in game and fully received introductory information
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 1.5k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Some parts for AI (invetory and cart-related, for example) may not have a solid point where all the information is received. For example, if you have no stackable items, the related packet would not be received at all.
Things which already have its own guaranteed points (packets) where all the information is ready may use their own points to be more robust, or use this common point for more easy implementation.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by tracing the existing guaranteed packet points and the handling of introductory information in OpenKore. Determine where a common in-game hook could run after the introductory information is complete, including cases where packets for absent stackable items are never received; done means AI features have a reliable shared point to use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100