Status:
A-OK
- Time: 11:09:08 AM 13-Aug-2008
Navigation
Active Players
- SubWolf
Active forum topics
Recent comments
- Players, we need you!
6 days 3 hours ago - JOIN
3 weeks 6 days ago - JOIN
4 weeks 1 day ago - JOIN
4 weeks 2 days ago - This passed before
4 weeks 2 days ago - Makes sense.
4 weeks 3 days ago - We only had 2 active players
4 weeks 4 days ago - Well, besides the fact that
4 weeks 4 days ago - Agreed. Some of us were
4 weeks 4 days ago - I'm so surprised at this
4 weeks 4 days ago
Contracts
- 06/29/2008 - 11:20
- 05/18/2008 - 01:41
- 05/26/2008 - 21:50
- 05/23/2008 - 19:07
- 05/14/2008 - 16:27
- 05/16/2008 - 00:11
- 05/14/2008 - 13:59
User login
Who's online
There are currently 0 users and 0 guests online.
Who's new
- BitterOldPunk
- SubWolf
- gerryblog
- vernondalhart
- Meatbomb
Syndicate
Chess Thread Archive
jay Sun, 05/11/2008 - 10:57
This is a historic graveyard for the Chess Thread
ROLL
MOVE 1 18 13
MOVE 2 9 17
ROLL
MOVE 15 9 19
MOVE 16 14 3
jay, just for clarity, a few questions:
1) I'm assuming that moves "run" in the order they're posted? i.e., when two pieces try to move into the same square, the second piece will take the first.
2) Since the rules don't prohibit changing one's moves, I presume that's allowed....
ROLL
MOVE 3 12 11
MOVE 4 14 19
ROLL
MOVE 14 19 11
How the fuck do you tell what color you are?
Meatbomb: use the numbers. You're the pieces labeled 11 and 12.
ROLL
MOVE 9 6 20
MOVE 10 3 10
The board is updated.
*ahem*
I think my pawn number 14 moved a little farther than I'd intended. Maybe I meant (11, 19), not (19, 11)
ROLL
MOVE 20 15 17
I corrected v's 11,19
If anybody else was submitting not horizontal-vertical let me know and I'll correct.
Re gerryblog's' questions, 1) Yes, the new piece would capture the old piece. 2) You can't re-move in reg'lur chess so I'm counting the only first move. Actually I'm counting everything right now but please only post one per turn.
Let's hope gerry logs in before offby1 and takes that pawn before it's a really really quick game for em.
In B Nomic's chess new pieces get created next to your king. We should patch our rules like that or we're going to have a lot of these ninja attacks .. maybe create new pieces within 2 squares of your king?
ROLL
MOVE 15 8 20
MOVE 16 14 4
MOVE 18 14 19
And yes, my poor king was basically spawned alone and unaided in the midst of enemy forces. He will persevere, but at what cost?
Because play is in order I'll just catch the board up as I can, if there are no objections. I hope to automate this to be realtime soon but I had problems getting NetLogo running on Linux.
(turtle 20) killed (turtle 18)
(turtle 15) killed (turtle 21)
So gerryblog's last posted move didn't get to happen.
My first move of today:
ROLL
Reporting for duty, jay: pawn on (patch 5 7) (turtle 22)
Okay, so I've moved already today, is that right? The next time I can move is 12:01 AM?
That sounds reasonable.
Depends on if you can move a piece on the day you ROLL it, which probably isn't fair given my sporadic rate of keeping the board updated.
Which means I can't move that pawn I just got.
I didn't mention that pieces are dispersed by normal chess occurrence frequency, e.g. there's an 8x chance you'll get a pawn instead of a queen.
All this is mutable, and I'm willing to do a certain amount of work to modify the chess game, if anybody wants to start proposing uncrossable squares or something weirder. The code already tracks Team and Health for no good reason.
Uh-oh, numbering got screwed up. Trying to unravel this with Dave, who currently owns a piece that gerryblog is shown to have moved.
ROLL
MOVE 3 13 12
MOVE 4 15 19
MOVE 19 18 2
jay: I think it was my piece at the time (my knight that got killed). Maybe people should just be careful to re-reference the map before they submit?
Re-rolling a couple pieces, and I think we're OK:
Reporting for duty, vernondalhart: pawn on (patch 16 3) (turtle 22)
Reporting for duty, gerryblog: pawn on (patch 13 11) (turtle 23)
Reporting for duty, jay: pawn on (patch 4 13) (turtle 24)
Reporting for duty, Dave: knight on (patch 11 4) (turtle 25)
I'm not moving today because it can't help.
I changed Dave's last comment to reference the piece 19 he used to have but was called piece 18 for a bit.
jay: I'm not sure what happened. To fix the problem with the numbering we had to reroll the pieces? That's too bad for me, because I had a bishop before -- but it's also too bad for Dave, as my new piece spawned right next to his King...
I'll give you all the Sporkos I have if you let him move away.
Or if you post intent to compile a more accurate gamestate from Revisions before another player posts a move I'll import it.
Okay, I think I can do that. Hold on a second.
Things get renumbered between 16:11 and 16:18.
Taking into account what should have been the revisions, here's what should be the board, I think:
(turtle 20) killed (turtle 18)
(turtle 15) killed (turtle 21)
--------
set commander "jay" crt 1 [ awaken "king" set color 15 move-to (patch 18 13) ] ;; (turtle 1)
set commander "jay" crt 1 [ awaken "pawn" set color 15 move-to (patch 9 17) ] ;; (turtle 2)
set commander "Dave" crt 1 [ awaken "king" set color 25 move-to (patch 13 12) ] ;; (turtle 3)
set commander "Dave" crt 1 [ awaken "pawn" set color 25 move-to (patch 15 19) ] ;; (turtle 4)
set commander "ctmf" crt 1 [ awaken "king" set color 35 move-to (patch 9 13) ] ;; (turtle 5)
set commander "ctmf" crt 1 [ awaken "knight" set color 35 move-to (patch 6 15) ] ;; (turtle 6)
set commander "jeblis" crt 1 [ awaken "king" set color 45 move-to (patch 9 11) ] ;; (turtle 7)
set commander "jeblis" crt 1 [ awaken "bishop" set color 45 move-to (patch 2 7) ] ;; (turtle 8)
set commander "offby1" crt 1 [ awaken "king" set color 55 move-to (patch 6 20) ] ;; (turtle 9)
set commander "offby1" crt 1 [ awaken "pawn" set color 55 move-to (patch 3 10) ] ;; (turtle 10)
set commander "Meatbomb" crt 1 [ awaken "king" set color 65 move-to (patch 4 15) ] ;; (turtle 11)
set commander "Meatbomb" crt 1 [ awaken "pawn" set color 65 move-to (patch 3 6) ] ;; (turtle 12)
set commander "vernondalhart" crt 1 [ awaken "king" set color 75 move-to (patch 15 10) ] ;; (turtle 13)
set commander "vernondalhart" crt 1 [ awaken "pawn" set color 75 move-to (patch 11 19) ] ;; (turtle 14)
set commander "gerryblog" crt 1 [ awaken "king" set color 85 move-to (patch 8 20) ] ;; (turtle 15)
set commander "gerryblog" crt 1 [ awaken "pawn" set color 85 move-to (patch 14 4) ] ;; (turtle 16)
set commander "jay" crt 1 [ awaken "pawn" set color 15 move-to (patch 12 3) ] ;; (turtle 17)
set commander "gerryblog" crt 1 [ awaken "knight" set color 85 move-to (patch 0 0) ] ;; (turtle 18)
set commander "Dave" crt 1 [ awaken "pawn" set color 25 move-to (patch 18 2) ] ;; (turtle 19)
set commander "vernondalhart" crt 1 [ awaken "pawn" set color 75 move-to (patch 15 17) ] ;; (turtle 20)
set commander "offby1" crt 1 [ awaken "pawn" set color 55 move-to (patch 0 0) ] ;; (turtle 21)
set commander "vernondalhart" crt 1 [ awaken "bishop" set color 75 move-to (patch 2 18) ] ;; (turtle 22)
set commander "gerryblog" crt 1 [ awaken "bishop" set color 85 move-to (patch 17 17) ] ;; (turtle 23)
set commander "jay" crt 1 [ awaken "pawn" set color 15 move-to (patch 5 7) ] ;; (turtle 24)
set commander "Dave" crt 1 [ awaken "knight" set color 25 move-to (patch 11 4) ] ;; (turtle 25)
Done! Thank you!
Thanks, Jay! I think this was the least worst way to deal with the renumbering issue.
There are a couple midnight duels now.
Hey, jay, while I'm breathlessly waiting for midnight, am I right that all my pieces don't have to move at once? For instance, I could move my king at 11 AM, and move my bishop at 6:15?
Judging from the way you were talking about your "first move of the day," it sounds like that's how you understand the rules, and nothing up top says that they all have to move at the same time.
(If anything the language suggests that you may move none of your pieces OR each of them -- ie, all or nothing.)
ROLL
MOVE 16 14 5
MOVE 23 15 19
Splitting moves up is fine by me. I can think of several reasons to ROLL just before or just after midnight.
Speaking of interpretations, here's one I like: losing your king doesn't mean you have to stop rolling and moving, for vengeance or bribes.
I was thinking that very thing.
It's already a hoot how non-participating players are going to get whacked. We should award Sporkos for kills.
ROLL
MOVE 22 9 11
And a king goes down!
Well, when this move takes place. I should get something for that.
ROLL
MOVE 3 14 13
MOVE 4 16 19
MOVE 19 18 3
MOVE 25 12 6
Reporting for duty, gerryblog: pawn on (patch 7 20) (turtle 26)
(turtle 23) killed Dave pawn (turtle 4)
Reporting for duty, vernondalhart: pawn on (patch 6 6) (turtle 27)
(turtle 22) killed jeblis king (turtle 7)
Reporting for duty, Dave: rook on (patch 17 15) (turtle 28)
Reporting for duty, jay: rook on (patch 9 1) (turtle 29)
oh yea i took my
ROLL
jay: slight error in the new map: Dave's pawn 4 should have been killed before he was able to move out of the way...
And I think you forgot to put your rook on too.
Dave's dead pawn moved from 0 0 to where he told it, I gotta catch that bug. I re-exported and my rook showed up.
Lets start with a
ROLL
jay: I'm not sure if it's a bug so much as the extreme literal nature of the commands. From now on people should be sure to write (kills X) next to the command that kills X so you know that X is dead and to ignore any subsequent moves involving X...
It leaves open the possibility of reanimation.
Here are some things I would like to see right away, if someone else wants to sponsor a proposal before it loops back to me:
Grant players a wall of pawns around their Kings before somebody rolls a Queen and executes us en masse.
Actions that could count as daily moves:
New command ASPLODE - sacrifice your piece to make the square uncrossable.
New command CLONE - 50/50 chance of duplicating a non-King to an adjoining square, or dying.
New command UPGRADE - spend 10 sporkos for a piece upgrade, up to Queen.
New command RESURRECT - spend 5 sporkos for a 50/50 chance of bringing a captured piece back onto a random empty square.
New command ENSLAVE - spend 10 sporkos for a 1/10 chance of gaining ownership of any uncaptured non-King.
New command ZOMBIE - spend 5 sporkos for a 1/10 chance of gaining captured ownership of a captured non-King.
Reporting for duty, SubWolf: rook on (patch 14 4) (turtle 30)
MOVE 1 18 14
MOVE 17 13 3
MOVE 24 6 6
(turtle 24) killed vernondalhart pawn (turtle 27)
I figured SubWolf could use a King so I JOIN'd him.
offby1 withdrew but there are no provisions for deleting pieces, so they're sitting ducks too.
ROLL
MOVE 26 6 20
MOVE 15 7 20
MOVE 16 15 6
MOVE 23 9 13
The first move kills #9, the second kills #5. It's a bloodbath.
Reporting for duty, gerryblog: bishop on (patch 17 3) (turtle 32)
(turtle 26) killed offby1 king (turtle 9)
(turtle 23) killed ctmf king (turtle 5)
ROLL
MOVE 20 16 16
ROLL
MOVE 19 17 3 (killing 32)
MOVE 25 13 8
MOVE 3 15 12
MOVE 28 17 10
Reporting for duty, vernondalhart: bishop on (patch 15 4) (turtle 33)
Reporting for duty, Dave: pawn on (patch 12 11) (turtle 34)
(turtle 19) killed gerryblog bishop (turtle 32)
MOVE 29 9 11
(turtle 29) killed vernondalhart bishop (turtle 22)
I can't stand the suspense.
ROLL
Reporting for duty, jay: pawn on (patch 11 12) (turtle 35)
gah
jay, let's make a deal: at midnight I'll move my bishop off the diagonal it's currently on, and you'll go in and kill SubWolf's king.
SubWolf is in need of a break. I may actively defend him.
Sounds like I'll see you at 12:00 AM.
Pfft, you were like eight whole minutes late last time.
MOVE 28 17 10
MOVE 34 13 10
MOVE 19 18 2
MOVE 3 16 12
MOVE 25 15 9
eat my bubbles
MOVE 23 7 11
(kills 31)
(turtle 23) killed SubWolf king (turtle 31)
MOVE 29 7 11
(turtle 29) killed gerryblog bishop (turtle 23)
MOVE 26 6 19
MOVE 15 6 20
MOVE 16 15 5
ROLL
MOVE 13 15 9 (killing 25)
MOVE 33 9 10
Reporting for duty, vernondalhart: pawn on (patch 19 18) (turtle 36)
(turtle 13) killed Dave knight (turtle 25)
jay, same offer, you take 30, I won't take you...
Gah, realized i didn't actually move my Rook 28, i just issued a MOVE with the coordinates it was already on, and my mistake cost me a Knight.
Given that I didn't actually move the Rook, I'm reissuing a proper MOVE order to him at this time with the expectation that such a MOVE is legal.
MOVE 28 17 9
Sorta like touching your piece without moving it, legal within reason.
ROLL
Reporting for duty, jay: pawn on (patch 13 12) (turtle 37)
ROLL
ROLL
Reporting for duty, gerryblog: knight on (patch 5 16) (turtle 38)
Reporting for duty, Dave: knight on (patch 11 14) (turtle 39)
MOVE 28 15 9
MOVE 16 14 4
MOVE 38 6 14
forgot to mention that 16 kills 30, earning me a delicious Sporko.
ROLL
MOVE 33 11 12 (kill 35)
MOVE 13 16 8
MOVE 36 18 17
That was carnage. Welcome 40 vernondalhart's pawn. Hope you like the new layout.
MOVE 17 14 4
MOVE 24 5 6
MOVE 29 6 11
MOVE 2 8 18
MOVE 37 12 11
ROLL
(turtle 17) killed gerryblog pawn (turtle 16)
Reporting for duty, jay: pawn on (patch 5 5) (turtle 41)
MOVE 15 5 20
MOVE 26 5 19
Hey, my Rook move to 15 9 would have killed vernondalhart's king.
Yeah, he's right. The king got killed, then respawned when you processed v's moves.
Crap, is my king gone?
I have to admit, this updating thing is confusing.
Fixed, and board's now caught up.
ROLL
Reporting for duty, jay: queen on (patch 15 18) (turtle 42)
bite it
Ack I already rolled last night, my queen goes poof.
ROLL
BITE jay's lost queen
Reporting for duty, Dave: pawn on (patch 3 8) (turtle 43)
I've made several steps toward automating this completely, so the board would update a couple minutes after a move is posted.
ROLL
MOVE 11 2 15
MOVE 12 2 7 (kill 8)
jay, it's your call, but given that 11 can't actually get to 2, 15 from where it's at it's probably best to read that as 3, 15, which I assume is what Meatbomb meant.
my apologies, yes, I meant 3 15
(turtle 12) killed jeblis bishop (turtle 8)
Reporting for duty, Meatbomb: knight on (patch 1 7) (turtle 45)
MOVE 39 13 13
MOVE 3 16 11
MOVE 19 17 3
MOVE 34 14 10
Updated
ROLL
ROLL
Reporting for duty, gerryblog: bishop on (patch 16 5) (turtle 46)
Reporting for duty, Dave: pawn on (patch 7 20) (turtle 47)
[invalid move, deleted]
[invalid move, deleted]
MOVE 43 2 7
(killing Meatbomb's pawn 12)
whoops.
MOVE 38 4 13
MOVE 46 8 13
Dave, I'm impressed, you're always there right on the button.
[incorrect, deleted]
oop overautomated
(turtle 43) killed Meatbomb pawn (turtle 12)
ROLL
Reporting for duty, jay: pawn on (patch 2 18) (turtle 48)
MOVE 37 11 12
MOVE 29 2 11
MOVE 2 7 18
MOVE 24 5 7
MOVE 41 6 6
MOVE 17 13 5
MOVE 1 17 14
(turtle 37) killed vernondalhart bishop (turtle 33)
(turtle 29) killed jeblis bishop (turtle 8)
MOVE 15 4 20
MOVE 26 4 19
Noted.
ROLL
MOVE 45 2 5
MOVE 11 2 15
Reporting for duty, Meatbomb: rook on (patch 4 12) (turtle 49)
Meatbomb, let's talk ransom.
MOVE 3 16 10
MOVE 28 13 9
MOVE 19 16 4
MOVE 47 6 20
MOVE 39 15 12
ROLL
Reporting for duty, Dave: pawn on (patch 20 10) (turtle 50)
ROLL
Reporting for duty, gerryblog: knight on (patch 8 11) (turtle 51)
MOVE 43 3 6
MOVE 38 5 15
MOVE 46 6 15
(kills 6)
MOVE 51 7 13
ROLL
MOVE 11 3 14
MOVE 49 4 13 (kill knight)
MOVE 45 4 4
My knight laughs at your clumsy attempts to kill him.
(turtle 46) killed ctmf knight (turtle 6)
Reporting for duty, Meatbomb: rook on (patch 2 7) (turtle 53)
gerryblog's knight moved away before Meatbomb's rook was scheduled to capture.
I think I'm one bug and one minor feature away from automating this completely so you don't have to wait on me to update the board.
This is a test of the new input filter, but also a move.
MOVE my rook 29 that was gonna take meatbomb's king to instead take out his brand new rook at 2 7 before he has a chance to move it.
(turtle 29) killed Meatbomb rook (turtle 53)
MOVE pawn 24 to 6 8 and his buddy
MOVE 41 7 7
MOVE 17 12 6
MOVE 37 12 14
MOVE king 1 to 16 13 - i'm not after that knight, dave, i just need safe passage
ROLL to test complete automation - my new piece should show up in an activity log under the piece list.
I consolidated the Spork Chess rules, noting in the main ruleset that what's on this thread is canonical, and included some of the clarifications and conventions we've been following. Appropriate objections welcome.
I would also like to propose tweaks to the game, barring objection:
Allow new pieces to move upon creation, and add a daily bonus automatic ROLL at 3pm Eastern for all players with a piece on the board.
ROLL