Opened 11 years ago
Last modified 11 years ago
#1844 new task
Change checkrefs.pl to pick up missing projectile attach points
Reported by: | Kieran P | Owned by: | |
---|---|---|---|
Priority: | Should Have | Milestone: | Backlog |
Component: | Non-game systems | Keywords: | |
Cc: | Patch: |
Description
(see subject)
If a unit has a Ranged attribute, make sure the projectile attach point is set for that unit.
Then use this each release to find and fix broken archers, towers, etc.
Change History (7)
comment:1 by , 11 years ago
Component: | Core engine → Non-game systems |
---|
comment:2 by , 11 years ago
comment:3 by , 11 years ago
What about changing the errors so they list the actor name that is missing the prop point?
comment:4 by , 11 years ago
That's what it does now :) But it's only the name of the actor file, not including the path, e.g. 'infantry_archer_b'
. It also doesn't mention the entity template, so the error could definitely be improved.
Example error:
ERROR: Unit with actor 'infantry_archer_b' launched a projectile but has no actor on 'projectile' attachpoint
comment:5 by , 11 years ago
Milestone: | Alpha 13 → Alpha 14 |
---|
comment:6 by , 11 years ago
Priority: | Release Blocker → Should Have |
---|
comment:7 by , 11 years ago
Milestone: | Alpha 14 → Backlog |
---|
Note:
See TracTickets
for help on using tickets.
This seems somewhat difficult to implement. Knowing an entity needs a projectile prop point is easy, but knowing if the actor will always provide one involves parsing the actor structure, including all variants and prop actors. Then there's always the possibility the model doesn't have one, which can't be easily checked by this script.
Also I can't reproduce the error we were getting the other day and it's not obvious from inspecting the templates where the error lies.