Badass Dragon Scavengers of the Void - Kassandra's Complex

games
1

You grab a nearby console and start a session with Kassandra.

wFKMNOY.gif720×392

Hey everybody! Kassandra here. I’ll be your logistics specialist, ship’s purser, and void boss. All that to say that you’ll be filing your orders with me every turn. I just want you to know that you can @mention me anywhere, and I’ll find you. and boy, will I find you… If you haven’t submitted a valid set of orders for the round by T-36h, I’ll even @mention you to remind you. Not too shabby, eh?

For sanity’s sake: plan on working out the kinks in your orders here and consider submitting your orders in the thread for the current round once you’ve finalized them. Currently recognized orders:

@Kassandra <option> PAY <amount> <player> BUY <item> TRADE <item> <player> MISSION <number> USE <node> <item> <juice> END

Please note: All orders for a given turn must be submitted in a single post. Each subsequent SUBMIT order overwrites all previous orders.

##Order Syntax and You: a Primer
@Kassandra

  • where <option> is either CHECK or SUBMIT

  • Indicates the start of an order block. I will ignore everything before my @mention.

  • @Kassandra CHECK will parse your orders for correct syntax

  • @Kassandra SUBMIT will submit your orders for the turn

  • DO check your maths

  • DO NOT edit an old order post as I will ignore it - create a new post instead

  • To update submitted orders, a new SUBMIT will overwrite your existing orders

    PAY

  • where <amount> is a quantity of juice and <player> is the account name of the recipient.

  • <player> can be either <player_name> or <@player_name>. Either are accepted.

  • Example: PAY 25 messana

    BUY

  • where <item> is the name of an item currently available for purchase from the ship’s stores

  • Example: BUY Hot_pocket

    TRADE

  • Will trade <item> from your inventory to <player>

  • <player> can be either <player_name> or <@player_name>. Either are accepted.* Example: TRADE Hot_pocket messana

  • You may buy and trade an item on the same turn

  • Only ONE trade order can be issued per turn

    MISSION

  • Indicates the mission selection of the void scavenger in question

  • Example: MISSION 3

  • Only ONE mission order can be issued per turn

  • If a mission is not selected, the idle fee for the turn will be deducted from your account. This can happen if:

    • Orders are not submitted for the turn
    • A MISSION directive is not found in your orders
    • You fail to meet the requirements of the mission you’ve selected
    • You are unable to pay the mission fee of the mission you’ve selected

    USE GOLD

  • Consumes one GOLD salvage from inventory

  • MaxHP+5 and HP+MAX for non-Wardens, MaxHP+15 and HP+MAX for Wardens

"And this GREEN stuff is super weird as an organic enhancement to existing equipment, check this out:

USE GREEN <item> <juice>

  • Consumes one GREEN salvage from inventory

  • Transmogrifies from existing inventory

  • <juice> is used to purchase BLUE from the hold at a 1:1 ratio

  • 50Ʉ is the minimum juice value required for transmogrification

  • Diminishing returns eventually kick in, but in general the more juice the more powerful the transmogrification

  • Transmogrification improves existing stats on the item

  • Transmogrification can add additional stats to the item based on the specialization of the player

    USE RED

  • Consumes one RED salvage from inventory

  • Acts as a combination USE GOLD and USE GREEN <item> <juice>+50

  • Extremely rare and valuable

  • Unused RED nodes will add 65HP to your suit the instant it reaches 0HP

Notes on the USE Order: A total of one GOLD and one GREEN effect can be experienced per player per round, which means either:

USE GOLD
USE GREEN <item> <juice>

or

USE RED

Represents the maximum number of use orders per player per round

END
  • Indicates the end of your orders.
  • I will ignore the remainder of the post.

Important notes:

At the moment, I should process all existing @Kassandra notifications within a few minutes. You should have some sort of response from me within 60s or so. That having been said, Discourse has some finicky thresholds regarding post rate and post entropy. If you don’t hear from me within two minutes, we’re probably running into one of these limits. Wait five minutes and try again. If you still don’t hear back from me, let @messana know and we’ll get it fixed.

A CHECK order only checks syntax - it does not simulate those orders in any way. Which means that an order of BUY Really_expensive_thing will be marked as a valid order, but does not check to see if you have sufficient cash on hand to make the purchase*

Similarly an order of MISSION 2 will check to see if that mission exists. It will not check if you meet the requirements to go on that mission.*

*That’s a bummer, why is that? It’s a side effect of the ‘everyone goes at once’ turn format. Successful actions in your orders may depend on someone else’s actions - specifically PAY and TRADE orders. Their orders may in turn depend on someone else’s orders. You may not clear the mission requirements at the moment, but orders submitted by someone else at the last minute may change that. Please see ‘Order of Round Execution’ below for more info.

Order of Turn Execution

  1. PAY orders for all players are executed; Juice totals are updated.
  2. BUY orders for all players are executed; player inventory, player stats, and Juice totals are updated.
  3. TRADE orders for all players are executed; player inventory and player stats are updated.
  4. MISSION FEES or IDLE FEES assessed for all players
  5. DETERMINATION of mission results

Related links:
Rules and Gameplay
Round 1 - Milk Run

2 Likes
2

For the record? I’m still settin’ up shop. I’ll let you know when I’m online and available to process your orders. And anyhow, don’t you have a training session to be at?

1 Like
5

Nothing like a little nap to wake up feeling refreshed. Better put out the shingle.

    CURRENT STATUS:      ACTIVE
    ORDER PROCESSING:    ONLINE
    SUBMISSION DEADLINE: 2017-01-22 18:00:00 -0500
    INCARNATION:         0x0b1fb8ca0c0caef8ba0177a8ee438af914b987c9
1 Like
8

And by way of example, here is what an order submission looks like:

@Kassandra check
BUY Fancy_Hat
BUY Hot_Pocket
MISSION 1
END

2 Likes
9 
  > iotrap.messana: 0xc2e6852abb6ffcdeb54de667e487e6e35a2e8da0

“Okay, messana - these orders have been parsed for accuracy, but not submitted.”

✖ buy fancy_hat
   [ERR] fancy_hat does not appear to be in stock this round. :(
✖ buy hot_pocket
   [ERR] hot_pocket does not appear to be in stock this round. :(
✔ mission 1
2 Likes
12

Whoops, that’s what I get for trying to shop before the missions are posted. Let me re-check these…

@Kassandra check
BUY Mag_Boots
BUY Directional_Antenna
MISSION 1
END

and maybe correct the config file…

2 Likes
13 
  > iotrap.messana: 0xb5ab567c74d9105349e1401b347605c2ad6fff2f

“Okay, messana - these orders have been parsed for accuracy, but not submitted.”

✔ buy mag_boots
✔ buy directional_antenna
✔ mission 1
2 Likes
14

Okay! Those orders check out. Let’s submit them.

@Kassandra submit
BUY Mag_Boots
BUY Directional_Antenna
MISSION 1
END

1 Like
15 
  > iotrap.messana: 0xbd981c394063c1b5b5e5df9f7eda23f687f446a3

“Roger that, messana - these orders have been submitted! You can overwrite these orders with a new submission.”

✔ buy mag_boots
✔ buy directional_antenna
✔ mission 1

“You know something? You seem nice.”

5 Likes
16

@Kassandra check
MISSION 3
END

17 
  > iotrap.gwwar: 0x362ea026d0fb3edbef16ae728df5269f80292ff6

“Okay, gwwar - these orders have been parsed for accuracy, but not submitted.”

✔ mission 3
18

@messana looks like the bot might need some Juice constraints, lest folks fry themselves the moment they EVA.

1 Like
19

Nothing like a little nap to wake up feeling refreshed. Better put out the shingle.

    CURRENT STATUS:      ACTIVE
    ORDER PROCESSING:    ONLINE
    SUBMISSION DEADLINE: 2017-01-22 18:00:00 -0500
    INCARNATION:         0x62fe81260da198d20aa1149009f51820d5cb89c6
1 Like
20

Very minor fixes. Namely - that typo was killing me.

1 Like
21

Testing issue with mixed case account names:

@Kassandra check
PAY 0 Old
PAY 0 SeaLion
PAY 0 Donald_Petersen
PAY 0 DreamboatSkanky
END

1 Like
22 
  > iotrap.messana: 0xb23c47f84411ae6cb19ecb57cb24aeed8c36e168

“Okay, messana - these orders have been parsed for accuracy, but not submitted.”

✔ pay 0 old
✔ pay 0 sealion
✔ pay 0 donald_petersen
✔ pay 0 dreamboatskanky
1 Like
23

Fixed - orders for round 1 that Kassandra flagged as errors will be processed correctly at execution. Future PAY orders should parse correctly.

24

Hmph. Typical paystub.

12 Likes
25

I’m working on improving kassandra in the background, so please feel free to submit bug reports and feature requests. For the moment, it’s pretty clear that mentioning a player in the orders should allow both ‘@playername’ and ‘playername’ - at the moment, it only recognizes the latter.

I will manually correct this until it is fixed - player intent will overrides syntax restrictions for at least turn 1.

1 Like
26

“So get this: as a gag, I change all the airlock codes. Right? And then…um. Crap, are we live?”

    CURRENT STATUS:      ACTIVE
    ORDER PROCESSING:    ONLINE
    SUBMISSION DEADLINE: 2017-01-22 18:00:00 -0500
    INCARNATION:         0x68fe00fd080c1988ce9e07800cadf7637fa4e589
2 Likes