Autopilot/Development - Revision history

Dihedral: /* Security */

2008-09-10T14:51:05Z

‎Security

2008-09-03T21:37:58Z

‎Code Notes

2008-09-02T13:41:14Z

‎IRC bot

2008-08-22T15:40:47Z

‎Security

2008-08-22T14:42:26Z

‎Code Notes

2008-08-22T14:22:31Z

2008-08-22T14:20:46Z

2008-08-22T14:18:41Z

‎IRC bot

2008-08-22T14:15:57Z

‎Information and automation

2008-08-22T12:55:43Z

‎Modular / Customizable (without the need of editing autopilot source directly)

← Older revision		Revision as of 14:51, 10 September 2008
Line 41:		Line 41:

	using [http://www.tcl.tk/man/tcl8.5/TclCmd/interp.htm interp] for custom commands / callbacks might be helpful		using [http://www.tcl.tk/man/tcl8.5/TclCmd/interp.htm interp] for custom commands / callbacks might be helpful
		+
		+	distributed ban system: bans may only be uploaded to the central server with user credentials (requires registration), download publicly available

	== Code Notes ==		== Code Notes ==

← Older revision		Revision as of 21:37, 3 September 2008
Line 46:		Line 46:

	use tcl 8.5		use tcl 8.5
		+
		+	use [http://www.tcl.tk/man/tcl8.5/TclCmd/dict.htm dictionaries] for player and company lists

	== IRC bot ==		== IRC bot ==

@@ Line 27: / Line 27: @@
 It's also envisaged that console commands can be sent to the game server directly from IRC.
 in ragrad to the rcon possibility, it would be useful to 'catch' the console output from the command and return it to the user on irc.
 === Modular / Customizable (without the need of editing ''autopilot'' source directly) ===

@@ Line 37: / Line 37: @@
 === Security ===
 ''autopilot'' should implement all of these features without leaving the game, the database, the IRC channel or any third parties vulnerable to the malicious activities of a few.
 == Code Notes ==

@@ Line 40: / Line 40: @@
 == Code Notes ==
 autopilot should entirely run in it's own namespace, everything that 'adds' to autopilot (such as any additional libraries) should have their namespace within the main autopilot namespace.
 == IRC bot  ==

@@ Line 16: / Line 16: @@
 * OpenTTD itself ''can'' send an MOTD when a client joins, however this is sent into global chat. provide a way to greet / send the MOTD to the new client in private
 * (optional) log openttd's stderr in case it crashes and the admin should be eager to know why / report a bug
 === Bridge to IRC / IRC bot ===
@@ Line 40: / Line 37: @@
 === Security ===
 ''autopilot'' should implement all of these features without leaving the game, the database, the IRC channel or any third parties vulnerable to the malicious activities of a few.
 == IRC bot  ==

← Older revision		Revision as of 14:18, 22 August 2008
Line 26:		Line 26:

	It's also envisaged that console commands can be sent to the game server directly from IRC.		It's also envisaged that console commands can be sent to the game server directly from IRC.
		+	in ragrad to the rcon possibility, it would be useful to 'catch' the console output from the command and return it to the user on irc.

	=== Modular / Customizable (without the need of editing ''autopilot'' source directly) ===		=== Modular / Customizable (without the need of editing ''autopilot'' source directly) ===

← Older revision		Revision as of 12:55, 22 August 2008
Line 30:		Line 30:

	The configuration of ''autopilot'' should, from the user's perspective, be a matter of providing settings in an "Windows INI" style configuration file (similar to openttd.cfg) and perhaps the modification of auxiliary scripts kept separate from the canonical source files. These scripts might contain Tcl commands, but it's worth considering writing a parser for something a little simpler.		The configuration of ''autopilot'' should, from the user's perspective, be a matter of providing settings in an "Windows INI" style configuration file (similar to openttd.cfg) and perhaps the modification of auxiliary scripts kept separate from the canonical source files. These scripts might contain Tcl commands, but it's worth considering writing a parser for something a little simpler.
		+
		+	include a method to (safely) implement custom !commands and define callbacks (sourced tcl files - using catch around source will prevent the tcl files from crashing ap)

	=== Security ===		=== Security ===