Talk:Remote agent: Difference between revisions

m
→‎Event parameters?: replaced (duplicated) table with "see task page"
(→‎game: new section)
m (→‎Event parameters?: replaced (duplicated) table with "see task page")
 
(5 intermediate revisions by 3 users not shown)
Line 13:
: Maze circumstances are fine; the intent in description was to prevent a ball from existing in a place where it couldn't be reached. --[[User:Short Circuit|Michael Mol]] 22:31, 16 December 2010 (UTC)
:: Great. Then I propose to pass another argument for the number of walls. For consistency, I would prefer to also pass the ''number'' of balls (instead of a percentage). What do you think?
: The specification for "Map Generation" requires that "no non-wall sector may be surrounded on four cardinal sides with wall sectors." This isn't strong enough to ensure that all (non-wall) cells are reachable. Was that the intention? --[[User:Tim-brown|Tim-brown]] ([[User talk:Tim-brown|talk]]) 12:30, 1 December 2014 (UTC)
 
Now I have a working server implementation (see the task). Concerning the color events, I propose to use upper- and lowercase characters: R G Y B for the fields (sectors), and r g y b for the ball. In an analog way, if we say that uppercase characters stand for sector attributes, and lowercase for ball attributes, and use some punctuation characters for special operations, the <del>following makes sense to me:</del> (see task page)
 
{|border=1
|-
|name||type||character||decimal||hex
|-
|forward||command||^||94||0x5E
|-
|turn right||command||>||62||0x3E
|-
|turn left||command||<||60||0x3C
|-
|get||command|||@||64||0x40
|-
|drop||command||!||33||0x21
|-
|game over||event||+||43||0x2B
|-
|stop||event||.||46||0x2E
|-
|color red||event||R||82||0x52
|-
|color green||event||G||71||0x47
|-
|color yellow||event||Y||89||0x59
|-
|color blue||event||B||66||0x42
|-
|ball red||event||r||114||0x72
|-
|ball green||event||g||103||0x67
|-
|ball yellow||event||y||121||0x79
|-
|ball blue||event||b||98||0x62
|-
|bump||event||<nowiki>|</nowiki>||124||0x7C
|-
|sector full||event||S||83||0x53
|-
|agent full||event||A||65||0x41
|-
|no ball in sector||event||s||115||0x73
|-
|no ball in agent||event||a||97||0x61
|}
: Epic timing. I'd just rewritten the commands myself. I like your command set better, though.--[[User:Short Circuit|Michael Mol]] 22:27, 16 December 2010 (UTC)
 
Line 69 ⟶ 26:
 
maybe this should be called "simulation" instead of "game". --[[User:Oenone|Oenone]] 08:54, 19 April 2011 (UTC)
: If you give it a goal, such as 'fewest steps possible', then it becomes a game, does it not? I'm not saying it's a conventional or particularly fancy game, though. --[[User:Short Circuit|Michael Mol]] 12:16, 19 April 2011 (UTC)
 
== Stream? ==
 
The Task talks about a "stream". Does this mean a TCP stream? Or is it just a stream without defining what medium to use? --[[User:Oenone|Oenone]] 09:17, 19 April 2011 (UTC)
: Any bidirectional stream is probably fine; some outside-program glue can be used as an adapter. For example, if there's a TCP-based server, but a STDIN/STDOUT-based client, one can use tcpwrappers to get the client and server talking to each other. --[[User:Short Circuit|Michael Mol]] 12:14, 19 April 2011 (UTC)
 
== First Turn ==
 
Once the handshake is exchanged, do I understand correctly that the RA has no idea about the cell it stands on until it successfully moves into another cell... bump won't describe your current cell. Could we have a stay "_" command, which although not awesomely useful for getting things done would at least show the contents of the first cell without changing the initial exchanges in the stream protocol. --[[User:Tim-brown|Tim-brown]] ([[User talk:Tim-brown|talk]]) 07:51, 10 December 2014 (UTC)
7,794

edits