Ok people. I need to know several things. 1: How do I make a mission completable by landing at any of 2 planets? I select any stellar of X govt, and it only completes when I land on the planet I started it from. 2: How do I set mďsn bits with shmelta-v so I you recive 1 set when you goto 1 planet, and make it impossible to get the other, and then vice versa with the mission on the other planet? 3: With res-edit, how do I give a planet a bar?

Even if you don't know the anwser to all 3, please tell, I really need to know.

------------------
"...Cotton Mouse... to say that the plug is royally messed up is an understatement. I'm taking a look at it with Plug Checker, and some of these errors I have just never seen before..."-Obormot, debugger

ERA for EV:
www.geocities.com/rhysmctharin/erahome.html

(still in alpha stages)

Question number 3 is really easy. The hex string for a spaceport bar is $00000040. Can't help you any more.

------------------

Quote

Originally posted by Cotton Mouse:
**Ok people. I need to know several things. 1: How do I make a mission completable by landing at any of 2 planets? I select any stellar of X govt, and it only completes when I land on the planet I started it from. 2: How do I set mďsn bits with shmelta-v so I you recive 1 set when you goto 1 planet, and make it impossible to get the other, and then vice versa with the mission on the other planet? 3: With res-edit, how do I give a planet a bar?

Even if you don't know the anwser to all 3, please tell, I really need to know.

**

It's possible that you've messed up your flags somehow. Could you post the specific values you have for the problematic fields? I'd have to see it.

Also, I don't quite understand what you mean with number 2.

------------------
$ take -over=world
bash: take: command not found

AIM: obormot345

Well, what I mean, is liike the confed or rebel misn plot. You can choose one, but not the other. As soon as you complete one, the other is no longer available.

------------------
"...Cotton Mouse... to say that the plug is royally messed up is an understatement. I'm taking a look at it with Plug Checker, and some of these errors I have just never seen before..."-Obormot, debugger

ERA for EV:
www.geocities.com/rhysmctharin/erahome.html

(still in alpha stages)

Well... Whenever I change it to "stellar owned by govt X", it only completes by landing on the planet I got it on. I also checked the spöbs, and both have the same govt. What GIVES???

(This message has been edited by Cotton Mouse (edited 07-01-2000).)

Quote

Originally posted by Cotton Mouse:
**Well, what I mean, is liike the confed or rebel misn plot. You can choose one, but not the other. As soon as you complete one, the other is no longer available.
**

Ah, this is easy. Make mission A set bit 1; make mission B set bit 2. Now, make mission A unavailable if bit 2 is set, and make mission B unavailable if bit 1 is set.

Quote

Originally posted by Cotton Mouse:
**Well... Whenever I change it to "stellar owned by govt X", it only completes by landing on the planet I got it on. I also checked the spöbs, and both have the same govt. What GIVES???.
**

Hmm... tough one. Hey, I know what... send the offending mission (in a plug by itself) to me, I'll take a look at it. There's not much I can tell you.

------------------
$ take -over=world
bash: take: command not found

AIM: obormot345

Quote

Originally posted by Cotton Mouse:
**Ok people. How do I set mďsn bits with shmelta-v so I you recive 1 set when you goto 1 planet, and make it impossible to get the other, and then vice versa with the mission on the other planet?

**

Not sure abpout Shmelta (BTW, where do you get that?). With resedit, you give both missions an availbitclear of x, and a startbitset of x. (x being any number)
Hope that helps.

------------------
To each his own,
Kretschmer

(formerly U-99)

Quote

Originally posted by Obormot:
**Ah, this is easy. Make mission A set bit 1; make mission B set bit 2. Now, make mission A unavailable if bit 2 is set, and make mission B unavailable if bit 1 is set.
**

Not quite, Obor-wan Kenorbi (sorry). This would result in the following:
You accept mission A. It sets bit 1. However, you could get mission A over and over and over.

The EVO solution is quite simple, really (for the strands). Make both missions available when bit 1 is set, but unavailable when bit 2 is set.
In addition, mission A would set bits 100 and 2, and mission B would set bits 200 and 2. The second mission of mission string A would become available when bit 100 was set, and the second mission of mission string B would become available when bit 200 was set, and missions A and B wouldn't repeat.

------------------
Zacha K
(url="http://"http://users.aol.com/zachakplug/sigdir/index.html")The Zacha K Space(/url)
(url="http://"http://users.aol.com/zachakplug/sigdir/azach.html")Find out more about the Zachit(/url)
(url="http://"mailto:ZachaKPlug@aol.com")mailto:ZachaKPlug@aol.com(/url)ZachaKPlug@aol.com

Quote

Originally posted by Zacha K:
**Not quite, Obor-wan Kenorbi (sorry). This would result in the following:
You accept mission A. It sets bit 1. However, you could get mission A over and over and over.

The EVO solution is quite simple, really (for the strands). Make both missions available when bit 1 is set, but unavailable when bit 2 is set.
In addition, mission A would set bits 100 and 2, and mission B would set bits 200 and 2. The second mission of mission string A would become available when bit 100 was set, and the second mission of mission string B would become available when bit 200 was set, and missions A and B wouldn't repeat.

**

Correct me if I'm wrong, but isn't there a AvailBitSet AND and AvailBitClear fields in a misn resource? If so, you could simply use both of them as AvailBit Clear fields by inputing the AvailBitSet as 1000+the bit. That would achieve the effect I was talking about.

Anywat, Cotton Mouse, I'll email you today.

------------------
$ take -over=world
bash: take: command not found

AIM: obormot345