IRCiv: Difference between revisions

From SoylentNews
Jump to navigation Jump to search
Line 73: Line 73:


===Development journal entries===
===Development journal entries===
http://soylentnews.org/~crutchy/journal/381
http://soylentnews.org/~crutchy/journal/379
http://soylentnews.org/~crutchy/journal/367
http://soylentnews.org/~crutchy/journal/357


http://soylentnews.org/~crutchy/journal/355
http://soylentnews.org/~crutchy/journal/355


http://soylentnews.org/~crutchy/journal/352
http://soylentnews.org/~crutchy/journal/352

Revision as of 22:16, 14 May 2014

IRCiv is a little game (and game engine of sorts) for building stuff like in "Civilization"-branded games.

IRCiv logo

IRC

IRC:exec


Commands

IRCiv commands must start with the exec alias "civ" unless an alias lock is set (which is the case by default).

status

Outputs a status message to either PM (default) or the game channel if "public_status" flag is set.

flag

syntax: [civ] flag name

flags recognised:

- public_status

outputs player active unit status to game channel instead of private message

- grid

paints gridlines on map images

example:

flag public_status

unflag

syntax: [civ] unflag name

set

syntax: [civ] set key=value

unset

syntax: [civ] unset key

Active unit movement

up or u
down or d
left or l
right or r

after movement command, status is automatically shown

if unit successfully moves, the active unit will be cycled to the next available unit

units can't move off map or off landmasses


if "public_status" flag isn't set (which is the case by default), it's probably easier to enter movement commands in the exec PM window, though they will still be recognised in the game channel; you will just have to change to PM window to see status

Website

A simple website @ http://irciv.port119.net/ has been set up to access map images output by the IRC script.

A demo can be accessed here: http://irciv.port119.net/?pid=1

Development

Developer(s): crutchy

Development journal entries

http://soylentnews.org/~crutchy/journal/381

http://soylentnews.org/~crutchy/journal/379

http://soylentnews.org/~crutchy/journal/367

http://soylentnews.org/~crutchy/journal/357

http://soylentnews.org/~crutchy/journal/355

http://soylentnews.org/~crutchy/journal/352