View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004780 | Spring engine | General | public | 2015-05-14 15:10 | 2015-06-16 20:19 |
| Reporter | Google_Frog | Assigned To | hokomoko | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | resolved | Resolution | no change required | ||
| Product Version | 98.0.1+git | ||||
| Summary | 0004780: Feature: Old antinuke behaviour (no flyover target) | ||||
| Description | This request is a tag for interceptors which makes them only fire at targets which are going to impact inside their interception range. This makes the antinuke coverage behaviour predictable for players. | ||||
| Tags | No tags attached. | ||||
| Checked infolog.txt for Errors | |||||
|
|
I would like this also. Afaics the current behaviour is basically a bug, even if it was coded intentionally, and players also interpret it as a bug. |
|
|
just in case: https://springrts.com/phpbb/viewtopic.php?f=12&t=33575&p=570437 (tag vs callin) |
|
|
Change != Bug You can use Spring.GetProjectileTarget to only intercept projectiles of your choice and get the old behaviour. |
|
|
I can? How? Afaics I can't use GetProjectileTarget until the interceptor projectile has fired, at which point if I decide that I don't want to incept the target, one anti-something missile (which probably cost resources, and might be the last of a stockpile that takes time to replenish) was just wasted. |
|
|
GetProjectileTarget of the nuke |
|
|
hokomoko where are you suggesting to use Spring.GetProjectileTarget? In Script.BlockShot? Wouldn't that make no antinukes intercept the target? Provide a more complete lua solution to regain the old behaviour because I am not convinced. |
|
|
> GetProjectileTarget of the nuke That would require a tangle of lua to handle cases where multiple missiles are shot towards multiple interceptors, and to handle issues of reload timings + "can this interceptor reach a missile of this type from here to some guess at where the missile might fly too in this time". I don't rate that as a solution, it pointless hard work and there is low chance of exactly replicating the old behaviour in anything but the simplest case of "interceptor travels so fast that it can reach the missile whatever". |
|
|
Not if you use AllowWeaponInterceptTarget callin. It's a simple check of target distance from owner. |
|
|
Ok, didn't know that callin existed, thanks. |
|
|
AllowWeaponInterceptTarget seems to do what it needs to do. This can be closed. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-05-14 15:10 | Google_Frog | New Issue | |
| 2015-05-17 09:23 | silentwings | Note Added: 0014469 | |
| 2015-05-17 09:25 | silentwings | Note Edited: 0014469 | |
| 2015-05-17 09:26 | silentwings | Note Edited: 0014469 | |
| 2015-06-15 12:54 | abma | Note Added: 0014588 | |
| 2015-06-15 18:20 | hokomoko | Note Added: 0014589 | |
| 2015-06-15 18:40 | silentwings | Note Added: 0014590 | |
| 2015-06-15 18:40 | silentwings | Note Edited: 0014590 | |
| 2015-06-15 18:42 | hokomoko | Note Added: 0014591 | |
| 2015-06-15 18:51 | Google_Frog | Note Added: 0014592 | |
| 2015-06-15 18:53 | silentwings | Note Added: 0014593 | |
| 2015-06-15 18:54 | silentwings | Note Edited: 0014593 | |
| 2015-06-15 18:55 | silentwings | Note Edited: 0014593 | |
| 2015-06-15 18:55 | hokomoko | Note Added: 0014594 | |
| 2015-06-15 18:55 | hokomoko | Note Edited: 0014594 | |
| 2015-06-15 19:05 | silentwings | Note Added: 0014595 | |
| 2015-06-15 20:28 | jK | Changeset attached | => spring develop 3dfcc893 |
| 2015-06-16 20:02 | Google_Frog | Note Added: 0014600 | |
| 2015-06-16 20:19 | hokomoko | Status | new => resolved |
| 2015-06-16 20:19 | hokomoko | Resolution | open => no change required |
| 2015-06-16 20:19 | hokomoko | Assigned To | => hokomoko |
