BlogNomic: The First Dynasty of Desertfrog

What happens to the other segments? That’s not clear to me.

Can you clarify what you mean by the other segments?

If you mean the ones that aren’t the extra two strings, I think they are still considered to be segments because they are part of the list of Segments. In other words, a Wager according to this Proposal should be thought of as a list of up to two strings appended to a list of Segments.

On the other hand, if you mean what does this Proposal even do, it’s meant to allow us to add segments to our wager that have been or will be proposed and we know we’re gonna want for whatever reason, but the Proposal enacting them has not yet passed.

I’d prefer it if this proposal was designed in such a way that it would work even if “Segmentation Fault” fails.

However, I’ll support it even as-is; not voting for now, though, so that you can edit it if required.

I suppose this is for people that does not play at least once a day. But does not it risk to be confusing? New Amnesiac can see in my Wager “7 Perpendicular Lines” and ask to themselves “Where is the 7 Perpendicular Lines Segment”???

Edited - @ais I incorporated your suggestion

@Marco Yes, I understand that concern. Players have no strategic incentive to do that, but they very well might. However, I don’t see a way to make things more clear without creating work for the admins, for example by making Players begin each string that isn’t yet a Segment with a Hashmark and having the admins remove the corresponding Hashmarks whenever they enact a Proposal that creates a new Segment. Still, maybe there is a better solution, or maybe what I just described is something people want, so I’m curious what you and others think. I’m going to leave my Proposal the way it is for now though. Note that if Kevan’s proposal passes, the strings would have to be at the end of the list, so that would make things a little clearer compared to if it does not pass.

Well, I think the response is in your Wager and pokes’ one: let “All segments” and “All segments except” :)

Doesn’t work the way its intended. If my wager consists a list of Segments and the word “Cheese” and then “Cheese” becomes a segment, my wager doesn’t magically contain the Cheese segment. It still just contains the word “Cheese”.

I’m also a little worried what a segment called “Ais523 Achieves Victory” would do…

[Clucky] In response to 2nd concern: such a statement would be gamestate, not a rule

In response to 1st concern: Why does the line, “If such a string is the Name of a Segment, it is the corresponding Segment.” not fix this issue?

per Clucky

More trivially, a Wager of “Numbness, Rimless” could either be a list of two Segments, or a single 17-character string which is not “the Name of a Segment”.

s/k but I would have liked to see my question to Clucky answered in case I was going to repost this