Add game option for textual order input.

[zond]

This would do a few things:

• Turn off the order options structure being sent to the client.
• Turn off error response codes for invalid orders.
• Refrain from sending orders for unresolved phases to clients.

This would force games to not validate orders, and give players leeway for breaking orders.

@tttppp, @JorenC what do you guys think?

[JorenC]

Oooh. I like it as an advanced user option.. But it's all about how we explain this, and I'm not sure exactly how the textual input would be...

…

On Wed, Apr 15, 2020 at 8:08 PM zond ***@***.***> wrote: This would do a few things: - Turn off the order options structure being sent to the client. - Turn off error response codes for invalid orders. - Refrain from sending orders for unresolved phases to clients. This would force games to not validate orders, and give players leeway for breaking orders. @tttppp <https://github.com/tttppp>, @JorenC <https://github.com/JorenC> what do you guys think? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#136>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABXURGOASDRK3ERPZB55P4TRMXZYRANCNFSM4MIZHVBQ> .

[zond]

Like

kie m ber

or

kie move ber

Case insensitive, I assume

[JorenC]

Hahahaha. That's not what I mean. I mean that we need to have some sort of "add order" interface; I would still want to have one rule per order (clearly separated) and some sort of "add order" thing...

…

On Wed, Apr 15, 2020 at 9:17 PM zond ***@***.***> wrote: Like kie m ber or kie move ber Case insensitive, I assume — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#136 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABXURGLVS5UQ4NEQKEMERXDRMYB4NANCNFSM4MIZHVBQ> .

[JorenC]

"delete order"

…

On Wed, Apr 15, 2020 at 10:10 PM Joren Bredman ***@***.***> wrote: Hahahaha. That's not what I mean. I mean that we need to have some sort of "add order" interface; I would still want to have one rule per order (clearly separated) and some sort of "add order" thing... On Wed, Apr 15, 2020 at 9:17 PM zond ***@***.***> wrote: > Like > > kie m ber > > or > > kie move ber > > Case insensitive, I assume > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#136 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABXURGLVS5UQ4NEQKEMERXDRMYB4NANCNFSM4MIZHVBQ> > . >

[zond]

Yeah - OR we could do it "like face to face" and give a text field, where we just split the input by line?

I mean - the point here is to give people enough rope to hang themselves, right?

[zond]

But, we still don't want to let people write messages and use the order view as a chat.

If we store the order input as text, and resolve them as "try to parse orders line by line", then we might want to filter out everything that isn't an order type, a unit type, or a province from the text before storing/displaying it?

[JorenC]

Yes, I think that makes sense. I would just make sure you have them enter it line by line, so any errors in order #1 don't have any impact on order #2.

…

On Wed, Apr 15, 2020 at 11:02 PM zond ***@***.***> wrote: But, we still don't want to let people write messages and use the order view as a chat. If we store the order input as text, and resolve them as "try to parse orders line by line", then we might want to filter out everything that isn't an order type, a unit type, or a province from the text before storing/displaying it? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#136 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABXURGJJK5SN6LV2ZM6V3YDRMYOGDANCNFSM4MIZHVBQ> .

[zond]

Oh, we can solve that even if they enter everything in a text field. But in the end it's a UX question, so I'll let you decide.