|
Notes |
|
|
(0002915)
|
|
randomed
|
2012-08-19 09:03
(edited on: 2012-08-20 13:34) |
|
I've tested this and it's confirmed for all castles. The error message says that there's no (catapult) curve calculated for hex 95 or 96.
There's another problem, but it is closely related to this one. You can aim with the catapult at the gate's edges (small towers near the game), even though they are supposed to be indestructible.
I've just started looking over the code, but the problem seems to be in one of these functions: isCatapultAttackable, battleGetWallUnderHex, hexToWallPart. Can't pinpoint exactly what it is.
|
|
|
|
|
Well, for one thing, it seems that in runBattle(), wallHexes are defined like this:
wallHexes = 50, 183, 182, 130, 62, 29, 12, 95
and in hexToWallPart() like this:
wallHexes = 50, 183, 182, 130, 62, 29, 12, 95, 96 plus the indestructable parts.
In the second one, hex 96 is added. Not sure why. |
|
|
|
|
I added relation to 0000785.
But there are many more discrepancies. See 0001065. If you check the report, you'll see it seems there are even other files defining wall targets than those two wallHexes you mentioned above. At least that's how it looks like, because:
- hexes 45, 78, 112, 147 can be targeted as well, but they're missing from the files you quote
- if we hit hex 12, the turret is destroyed, but if we hit hex 183, the turret remains in place
So there seem to be multiple lists, some listing possible targets, others defining which/how should take damage, but they are not all in sync. |
|
|
|
(0004171)
|
|
beegee
|
|
2013-12-08 18:06
|
|
|
This problem has been fixed in the meantime. I don't know since which version you can shoot on castle gate. |
|