Fractal Softworks Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Starsector 0.95a is out! (03/26/21); Blog post: Skill Changes, Part 2 (07/15/21)

Author Topic: Infinite engage bug  (Read 2111 times)

Sutopia

  • Admiral
  • *****
  • Posts: 901
    • View Profile
Infinite engage bug
« on: September 26, 2016, 04:51:24 AM »

I found this happening when enemy have a good amount of fighters, and enemy owns carrier.
When an amount of them go into no-CR state?with few planes left and retreated?, you can only chose to engage or leave them be.
Leaving will make you unable to claim loots and capture enemy ship.
Re-engage will make enemy send nothing and you claim inatant victory and go back to first step.

This happened in an  IBB mission engage which I believe was from ship/weapon pack.

Dark.Revenant

  • Admiral
  • *****
  • Posts: 2700
    • View Profile
    • Sc2Mafia
    • Email
Re: Infinite engage bug
« Reply #1 on: September 26, 2016, 08:53:35 AM »

Were you using Starsector+?

Did the carrier have CR left?
Logged

Sutopia

  • Admiral
  • *****
  • Posts: 901
    • View Profile
Re: Infinite engage bug
« Reply #2 on: September 26, 2016, 12:43:46 PM »

Were you using Starsector+?

Did the carrier have CR left?
No, but I was using nexerelin.

The carrier was destroyed, leaving only helpless retreated wings.

Dark.Revenant

  • Admiral
  • *****
  • Posts: 2700
    • View Profile
    • Sc2Mafia
    • Email
Re: Infinite engage bug
« Reply #3 on: September 26, 2016, 06:10:53 PM »

That's a vanilla problem, actually.  SS+ makes a fix for it, which is why I asked.
Logged

Sutopia

  • Admiral
  • *****
  • Posts: 901
    • View Profile
Re: Infinite engage bug
« Reply #4 on: September 26, 2016, 06:18:46 PM »

Oh, thanks for the answer.

So does dev know about this bug and fixing it in next patch?

Alex

  • Administrator
  • Admiral
  • *****
  • Posts: 19088
    • View Profile
Re: Infinite engage bug
« Reply #5 on: September 26, 2016, 06:24:24 PM »

Yeah, with the fighter changes in the next release, this should be fixed. Thanks for bringing it up!
Logged