Looking to start a chatbot expansion

[Cody]

Agree with Rustybolts. I think this could be really good.

Kaks, you know it affects use of F5 to F7 in flight (in 1.73.4, seemed alright in trunk).
I love it. Maybe one more pic:



Regards

[pagroove]

Didn't see this either. So downloading now. Good Idea!

[Commander McLane]

How much of this WIP is supposed to be working? I can target a ship and get its identity with F8. However, I can't choose any of the options. Furthermore, once done this in flight, the background picture is all over every screen also when docked, and the F5-F8 screens are no longer usable.

Probably there is a connection with this error in the log, which I got when another OXP displayed a mission screen while commsdemo is installed:

Code: Select all

[script.javaScript.exception.noProperties]: ***** JavaScript exception ("kaks-commsdemo" 0.1): TypeError: mission.choice has no properties
[script.javaScript.exception.noProperties]:       /Applications/Spiele/Oolite 1.73.4/AddOns/CommsDemo 0.1.oxp/Config/script.js, line 152.

[drew]

This is a great idea, I and missed it too. More power to you on this, Oolite will really benefit from a working comms system - a lot of the writers on here can contribute 'appropriate' messaging...

Cheers,

Drew.

[DaddyHoggy]

This is a great idea, I and missed it too. More power to you on this, Oolite will really benefit from a working comms system - a lot of the writers on here can contribute 'appropriate' messaging...

Cheers,

Drew.

Absolutely!

[Cody]

How much of this WIP is supposed to be working?

I think Kaks wrote it as a proof of concept. It works fine in trunk, but in 1.73.4... well you saw the result.

[Kaks]

And me mucking about with trunk yesterday might have made it slightly unplayable in trunk too, at least in its present form...

The bad news: in 1.73.x (and trunk, until recently), mission screens while in flight are 'slightly' broken. You can't select the various options, like you would when docked, and the only way out of the mission screen would be to press keys (f)1 to (f)4. I had to do something quite evil to make them work semi-ok. the only way to choose the options would be to press the numbers written at the beginning of each option.

As it happens, I thought I tested that commsDemo with 1.73.4, while in fact I used a different one (early october trunk build. don't quite know how it happened!)

The good news: I'll have some time this weekend, so I'm going to try & make the comms demo really 1.73.4 compatible.

The very good news: in 1.74 mission screens will work properly while in flight (f1 to f4 will still exit the 'mission' screen, so you can still jump out of the screen the second you need to), so in future I shouldn't have to do some of the weird things I had to do to make the comms demo (almost) 1.73.4 compatible.

Guys, sorry for the mix-up! 1.73.4 & 1.74 compatible comms demo oxp coming up!

[Rese249er]

This would be a great OXP in my opinion. Question is, where's the 1.76.1-compatible versions?

[Svengali]

[wiki]Cabal_Common_Library[/wiki] offers comms channels, but as far as I know only the Vector uses it (and the MaterialsFinder).

[Rese249er]

So no offers to escort a trader? Couple that with Escort Formation Autopilot, sounds like it'd be good. Or asking a Viper if you can follow them insystem.

[Svengali]

So no offers to escort a trader? Couple that with Escort Formation Autopilot, sounds like it'd be good. Or asking a Viper if you can follow them insystem.

Nope. At least not yet.

CCL_Comms is there to give OXPs a way to create ship2player (and worldScripts2player) comms for specific situations and not for general use, because of the CommsDemo.oxp by Kaks and the WIP version Okti was working on. Probably I should think about it again.

[Rese249er]

Ah, slag.