Ambrosia Garden Archive
    • Ambrosia Garden Archive

    • Mission bit bug?

       EV Developer's Corner
      4 8 337
      A
      A

      I'm not sure if everybody views this as a bug, but shouldn't the retirebits of a ship be acted out when someone dies in that ship?

      I thought of this when my Leviathan was destroyed by Marauders, and I was left in a shuttlecraft which could see bulk deliveries and always got chased by heavy pirates.

      ------------------
      (url="http://"http://www.foresight.org/Conferences/MNT6/nanohook.mov")This(/url) is the most frightening video I have ever seen.

      0
    • J
      J

      Angel,

      I don't think that it would be possible to reset specific missions immediately when a ship is destroyed. The bulk deliveries, etc. are set by various missions. There is an OnRetire field in the shďp resource, but this field is set when the shďp is created, so there would be no way to know what missions you have enabled/completed.

      I suspect that the mission bits will be reset when you dock somewhere in your escape pod and buy a new ship.

      ------------------
      Excuse me - Shuttlecraft.

      (This message has been edited by JohnnyAndrews (edited 05-31-2002).)

      0
    • A
      A

      Quote

      Originally posted by JohnnyAndrews:
      **Angel,

      I don't think that it would be possible to reset specific missions immediately when a ship is destroyed. The bulk deliveries, etc. are set by various missions. There is an OnRetire field in the shďp resource, but this field is set when the shďp is created, so there would be no way to know what missions you have enabled/completed.

      I suspect that the mission bits will be reset when you dock somewhere in your escape pod and buy a new ship.

      **

      Sorry, I should have made it clear that I'm using a plugin which makes bulk deliveries mission-bit dependant (so you can use Leviathan variants for them). It just seems to me that the OnRetire bits should be set when your ship is destroyed, too. Otherwise you get b8888 set, and you're in a shuttlecraft. Bad news.

      ------------------
      (url="http://"http://www.foresight.org/Conferences/MNT6/nanohook.mov")This(/url) is the most frightening video I have ever seen.

      0
    • M
      M

      Use the require fields in the mďsn resource and the contribute fields in the shďp resource. The mission won't be available unless the ship you are currently in has the proper contribute fields setting.

      ------------------
      Moderator- (url="http://"http://www.AmbrosiaSW.com/cgi-bin/ubb/forumdisplay.cgi?action=topics&number;=9&SUBMIT;=Go")EV Developer's Corner(/url)
      All the good ways of saying I love pipeline were already taken...
      (url="http://"http://www.ambrosiasw.com/cgi-bin/vftp/dl-redirect.pl/TheChallenge101.sea.bin?path=evn/plugins&file;=TheChallenge101.sea.bin")The Challenge(/url): A deadly test of skill and power (new version 1.0.2 coming soon)
      (url="http://"http://homepage.mac.com/mrxak/Haikus/haikus.html")The Haiku Archive(/url): Collected Works of the Rabid Haiku Generator

      0
    • A
      A

      Quote

      Originally posted by mrxak:
      **Use the require fields in the mďsn resource and the contribute fields in the shďp resource. The mission won't be available unless the ship you are currently in has the proper contribute fields setting.
      **

      I know that. Everybody seems to be missing my point. Let me explain myself:

      Ships have mission bits that they require, ones that they set on being captured, ones they set on being bought, and ones they set on being retired (traded in or swapped for a captured ship). The way these bits are usually used is this:

      -you put bit X in the capture/purchase contribution fields
      -you put the opposite of bit X in the retire field

      This way, when you capture that capital ship, b8888 gets set, and bigger pirates come after you. If, however, you sell or swap that capital ship for a shuttle, b8888 gets un-set. This way, you don't have Manticores coming after you so often when you are unprepared for them.

      However, if your capital ship gets destroyed, you are put back in the shuttle, and because you neither sold nor swapped your old ship, b8888 is still enabled.

      So, with this background information, please take a look at my question:

      Shouldn't the retire bits be set when your ship is destroyed? Otherwise, there is no way to ensure that a bit is only set when someone has a specific ship: they can keep the bit by dying, and it stays until something else affects it. Is see this as a bug, or at least an omission.

      ------------------
      (url="http://"http://www.foresight.org/Conferences/MNT6/nanohook.mov")This(/url) is the most frightening video I have ever seen.

      0
    • A
      A

      Quote

      Originally posted by Angel:
      **I know that. Everybody seems to be missing my point. Let me explain myself:

      Ships have mission bits that they require, ones that they set on being captured, ones they set on being bought, and ones they set on being retired (traded in or swapped for a captured ship). The way these bits are usually used is this:

      -you put bit X in the capture/purchase contribution fields
      -you put the opposite of bit X in the retire field

      This way, when you capture that capital ship, b8888 gets set, and bigger pirates come after you. If, however, you sell or swap that capital ship for a shuttle, b8888 gets un-set. This way, you don't have Manticores coming after you so often when you are unprepared for them.

      However, if your capital ship gets destroyed, you are put back in the shuttle, and because you neither sold nor swapped your old ship, b8888 is still enabled.

      So, with this background information, please take a look at my question:

      Shouldn't the retire bits be set when your ship is destroyed? Otherwise, there is no way to ensure that a bit is only set when someone has a specific ship: they can keep the bit by dying, and it stays until something else affects it. Is see this as a bug, or at least an omission.

      **

      Yes, that seems like a bug. Send it to ATMOS and let them deal with it.

      Quote

      **
      This is the most frightening video I have ever seen.
      **

      Umm, what's so frightening about that video? I guess I don't understand because it's out of context, but what's it showing?

      ------------------
      Kevin Ballard
      (url="http://"mailto:kevin@sb.org")mailto:kevin@sb.org(/url)kevin@sb.org

      0
    • A
      A

      Send it to ATMOS? Where? My feeling is that they don't take kindly to bug reports.

      ------------------
      (url="http://"http://www.foresight.org/Conferences/MNT6/nanohook.mov")This(/url) is the most frightening video I have ever seen.

      0
    • A
      A

      Quote

      Originally posted by Angel:
      **Send it to ATMOS? Where? My feeling is that they don't take kindly to bug reports.

      **

      Why do you think they don't like bug reports? They need bug reports to find out about bugs! Why do you think they're releasing a 1.0.1 version?

      Oh, and you might try mburch@ambrosiasw.com. It seems like the best target for this report, seeing as the problem is in the engine.

      ------------------
      Kevin Ballard
      (url="http://"mailto:kevin@sb.org")mailto:kevin@sb.org(/url)kevin@sb.org

      0