When issuing commands like :build Tom the output appears on the console, even in port mode.

Since it’s separated with unix style newlines this is particularly painful on windows, but it’d be wonderful if there were a way to say ‘send all the output to the port’

I’ve built myself a nice tool for interacting with the bot as part of my front end, but, for example, still have to paw through the hard to read windows console to read compiler output.

Currently no. Such output might blow the buffer limits for transferring data from server to client.  if you have access to the same machine the server is on, you could get the user log file and read that for the compilation information.  I can probably make the summary part of the build data send across the server, so you’d get the warnings and errors.

that’d be a nice option for me.  I’m sure I’m not the only person who’se interacting with CS via some front end.

Hadn’t considered the implications of the volley architecture for this sort of OOB communications.

Normally I’d expect someone who was “building” to do one of several things…
1. build on your local machine, transfer the TOPIC folder to the server, and issue a restart to the server
2. go to the server machine, run CS locally, do a build, then restart the server

well, when developing a character it’s mostly

1. run my front end, which makes it easy to interact with the bot
2. run CS as a server, so my front end has something to talk with
3. fiddle with the bot til I figure out what’s causing it to say the wrong thing/find a wrong thing
4. Edit the appropriate file inside RAWDATA
5. rebuild the bot and reset the user, which I have a handy pushbutton to do

only problem is, I’m on windows, I get unix style newlines in the server console when it builds, so the output’s not rally readable.

next release will
a) not echo build messages to server console (but will echo the restart sequence of CS)
b) will send the summary data only over to the client

Thats great - I notice that this version does echo :build 0