A-20 Attack Destroyer Collision Issues

Program aborts? Network configuration? Graphic errors? Bugs? Post your question here.
posted on July 12th, 2009, 2:58 pm
I don't know if these two issues are intended, but I'm pretty sure they aren't:

If a Dominion Bug is selected to collide with a ship which then cloaks and the ship does not move out of sensor range after cloaking completely the Bug will still collide with it and explode, dealing damage of course (spelling doom for any cloaking ships slower than the Bug as well as stop and cloak actions).

If the ship moves out of sensor range by the time it has finished cloaking, the Bug will not follow it, but if the ship then decloaks anywhere on the map, the A-20 Attack Destroyer will chase it down and collide with it as normal.
posted on July 12th, 2009, 3:22 pm
thats indeed not intended. we will take a look. thanks for reporting
posted on July 12th, 2009, 3:30 pm
The first one I can understand; unless the ship moves in another direction when cloaking, it is still there and can still be hit even if the enemy doesn't see it.

I assume that your talking about following it as if it could see cloaked ships?
posted on July 12th, 2009, 4:52 pm
The first one I can understand; unless the ship moves in another direction when cloaking, it is still there and can still be hit even if the enemy doesn't see it.


As long as the targeted ship remains in sensor range it will still be impacted by the Bug. This means that you can move the ship anywhere around the Bug, and the Bug will follow it. This should not happen.

Yup indeed, it is as if the ship can see the cloaked ship.
posted on July 12th, 2009, 6:47 pm
Probably the same bug causing transporters to keep transporting onto cloaked ships, it's likely that cloaking doesn't reset enemy ai targets for teleport/ram.
posted on July 12th, 2009, 7:11 pm
Sounds accurate to me.
posted on July 12th, 2009, 10:24 pm
Personally, I think the collision exerts too much of a repulsion force on the ship it hits, which can cause the effect to look a bit wrong (target goes soaring backward while the bugship fizzles and explodes at the location it was when it impacted). Maybe some sort of big "flash" effect would be helpful to obscure some of that weirdness and make it easier to tell (because with this cosmetic bug, no pun intended, it's difficult) when a ramming attack has actually taken place.
posted on July 13th, 2009, 2:12 am
...especially considering the Bug ship explodes waaay before even hitting the ship  :crybaby:
posted on July 13th, 2009, 2:21 am
What do you mean lost all resources? Everything should be infinite. Have you tried reproducing it?
posted on July 13th, 2009, 2:27 am
If I remember correctly, in the shows, the bugships had a good track record for detecting and/or tracking cloak more effectively (still not 100%) than the other races.
posted on July 13th, 2009, 11:02 am
Last edited by DOCa Cola on July 13th, 2009, 11:17 am, edited 1 time in total.
stop talking sh*t 1337. that's at least the 3rd or 4th time you report or talk about an obviously non-existing bug or uber cheat. if you like to have attention, please do it another way.

i'll take a look into the ship tracker problem, should be fixable. thank you
Reply

Who is online

Users browsing this forum: No registered users and 21 guests

cron