For information and discussion about Oolite.
https://bb.oolite.space/
I think there has popped up a little bug in the regular part of the default comms. When choosing the option "demand 5t.." from a random NPC that doesn't have anything about it customised, the expected transmission doesn't show up, (or rather my ship's name: and then blank) but the target replies as if it got the message. I'm pretty sure this is unrelated to the tinkering I'm doing.
Cool.
Well, it's confirmed. The same code that would allow me to customise a taunt transmission and reply onto a regular ship will not appear on a dockable. Both Scrubs and Behemoths are affected, so it isn't anything to do with Military class/policing. They do both have the docking permission comms entering into it, that could be something (automatic from isCarrier?). They also both have custom tunnel_texture in the script actions, there's market definitions..
This is true, but I thought it might be amusing if a mammoth ship would comment on the ridiculous nature of the mismatch.Cholmondely wrote: ↑Thu Jul 21, 2022 8:29 pmHuuumph... any self respecting dockable would not bother replying to a taunt, no matter how customised. They'd just turn towards the insulter and proceed to transmogrify them into a 2 dimensional pancake...
Afraid BC 1.3.1 also logReports "Invalid settings: Cannot use comm system message types" when I display the verbatim Send greeting to target.
Cholmondely wrote: ↑Thu Jul 21, 2022 8:29 pmany self respecting dockable would not bother replying to a taunt, no matter how customised
I think I was going along Cholmondely's line of thinking when I originally put the code together. By default, no station (ie something with a dock) will have the "Taunt" option. Therefore, if you want to achieve that, you'd need to disable the built in message type, and add custom message, rather than use the "bcc_custom_defaults" option.
Well, once I get it working reliably, anyway.
Yes it's no problem to simulate it, as you've shown me.phkb wrote: ↑Thu Jul 21, 2022 10:04 pmI think I was going along Cholmondely's line of thinking when I originally put the code together. By default, no station (ie something with a dock) will have the "Taunt" option. Therefore, if you want to achieve that, you'd need to disable the built in message type, and add custom message, rather than use the "bcc_custom_defaults" option.
Afraid it still blanks, and errorLogs:
Code: Select all
[script.javaScript.exception.uncaughtException]: ***** JavaScript exception (BroadcastCommsMFD 1.3.2): uncaught exception: Invalid settings: Cannot use comm system message types.Code: Select all
[script.javaScript.exception.uncaughtException]: ***** JavaScript exception (BroadcastCommsMFD_Equipment 1.3.2): uncaught exception: Invalid settings: message already exists.Code: Select all
"script_info" = {
"bcc_custom_messages" = {
level1a = {
delay = 5;
"delete_on_transmit" = yes;
display = "Greet target";
"post_reply_show_messages" = (
level2
);
reply = "[scrub-greeting-reply]";
state = visible;
transmit = "Greetings, honoured Scrub.";
};
level1b = {
delay = 5;
"delete_on_transmit" = yes;
display = "Taunt target";
reply = "[scrub-taunt-reply]";
state = visible;
transmit = "[scrub-taunt-transmit]";
};
level2 = {
delay = 4;
"delete_on_transmit" = yes;
display = "Inquire trade opportunity";
"post_reply_show_messages" = (
level3
);
reply = "[scrub-decide-reply]";
state = hidden;
transmit = "Great Scrub command. Please advise, is this a good time to do business?";
};
level3 = {
delay = 6;
"delete_on_transmit" = yes;
display = "Elaborate for a more clear answer";
reply = "[scrub-trade-reply]";
state = hidden;
transmit = "[scrub-trade-transmit]";
};
};
"bcc_disable_defaults" = (
1,
2,
3,
5,
6,
7,
8,
9
);
You have the "Send taunt to target" replacement set with key "level1b". However, in the "bcc_disable_defaults" array, you don't have a "4". So you'd end up conflicting with the core message.
Ah. So it can tell, even though it's named differently, "Taunt target"..
