Annotate TargetChaser category and InheritWork unit callback#7011
Annotate TargetChaser category and InheritWork unit callback#7011lL1l1 wants to merge 1 commit intoFAForever:developfrom
Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Description of the proposed changes
Some stuff I discovered in RE.
Testing done on the proposed changes
TARGETCHASERto 1 type of gunship.dbg navsin consoleTARGETCHASERwill chase in formation, while those with the category will all fly at the target.Additional context
This may be useful for fixing the undesirable behavior from the testing. I don't know the category was not in original units. Some more investigation would be desirable for side effects.
Checklist
- [ ] Changes are documented in a changelog snippet according to the guidelines.