Botflags - Revision history

Silentwings: /* Battle hosts on the lobby server */

2019-03-31T17:31:38Z

Battle hosts on the lobby server

← Older revision		Revision as of 18:31, 31 March 2019
Line 3:		Line 3:
	== Battle hosts on the lobby server ==		== Battle hosts on the lobby server ==

	All battle hosts that do not have a botflag are limited to a maximum number of players, plus unlimited spectators. This includes both human hosters and autohosts.		All battle hosts that do not have a botflag are limited to a maximum number of 8 players, plus unlimited spectators. This includes both human hosters and autohosts.

	Host admins that would like to get a botflag for an Autohost need to create a new thread in the [https://springrts.com/phpbb/viewforum.php?f=16 Ingame Community Forum] with "Botflag request" as topic title and the lobby username which should get the botflag. ''Note: A botflagged user account should not be used to play games on, except when hosting; otherwise it will not function correctly.		Host admins that would like to get a botflag for an Autohost need to create a new thread in the [https://springrts.com/phpbb/viewforum.php?f=16 Ingame Community Forum] with "Botflag request" as topic title and the lobby username which should get the botflag. ''Note: A botflagged user account should not be used to play games on, except when hosting; otherwise it will not function correctly.

Silentwings: /* Battle hosts with a botflag */

2019-02-01T10:45:05Z

Battle hosts with a botflag

← Older revision		Revision as of 11:45, 1 February 2019
Line 15:		Line 15:

	Autohosts with a botflag are expected to appoint host owners and/or admins who are generally capable of maintaining the above expectations, with the help of the tools (pms/kicks/bans/mutes/plugins/etc) provided by the lobby server and SPADS. They should react and respond to all server commands in accordance with the lobby protocol. As part of the response to a ''!list users'' command sent via private message, the autohost must list the usernames of all host admins, and at least one contactable host owner. This list should be kept up to date.		Autohosts with a botflag are expected to appoint host owners and/or admins who are generally capable of maintaining the above expectations, with the help of the tools (pms/kicks/bans/mutes/plugins/etc) provided by the lobby server and SPADS. They should react and respond to all server commands in accordance with the lobby protocol. As part of the response to a ''!list users'' command sent via private message, the autohost must list the usernames of all host admins, and at least one contactable host owner. This list should be kept up to date.

			Hosts with a botflag are normally expected to use the latest stable engine version, or a later developmental version, and to host content that is made available for automated download.

	Hosts with a botflag may add additional features and enforce restrictions on their use (such as rank limits, plugins, special game modes) providing that they meet the above expectations. In extreme cases, if lobby moderators judge that the above expectations are consistently not met, lobby moderators may require that particular people are added and/or removed as host admins or owners, or that particular features/restrictions are removed. Hosts that do not comply will lose their botflag.		Hosts with a botflag may add additional features and enforce restrictions on their use (such as rank limits, plugins, special game modes) providing that they meet the above expectations. In extreme cases, if lobby moderators judge that the above expectations are consistently not met, lobby moderators may require that particular people are added and/or removed as host admins or owners, or that particular features/restrictions are removed. Hosts that do not comply will lose their botflag.

	~~Hosts with a botflag are normally expected to use the latest stable engine version, or a later developmental version, and to host content that is made available for automated download.~~

	=== Battle hosts without a botflag ===		=== Battle hosts without a botflag ===

Silentwings: /* Battle hosts with a botflag */

2019-02-01T10:44:26Z

Battle hosts with a botflag

← Older revision		Revision as of 11:44, 1 February 2019
Line 12:		Line 12:
	=== Battle hosts with a botflag ===		=== Battle hosts with a botflag ===

	Hosts with a botflag are expected to encourage and maintain an environment in which users are able to play games, free from serious disruption and excessively hateful or obscene behavior~~. The are generally expected to use the latest stable engine version, or a later developmental version, and to host content that is automatically downloadable~~.		Hosts with a botflag are expected to encourage and maintain an environment in which users are able to play games, free from serious disruption and excessively hateful or obscene behavior.

	Autohosts with a botflag are expected to appoint host owners and/or admins who are generally capable of maintaining the above expectations, with the help of the tools (pms/kicks/bans/mutes/plugins/etc) provided by the lobby server and SPADS. They should react and respond to all server commands in accordance with the lobby protocol. As part of the response to a ''!list users'' command sent via private message, the autohost must list the usernames of all host admins, and at least one contactable host owner. This list should be kept up to date.		Autohosts with a botflag are expected to appoint host owners and/or admins who are generally capable of maintaining the above expectations, with the help of the tools (pms/kicks/bans/mutes/plugins/etc) provided by the lobby server and SPADS. They should react and respond to all server commands in accordance with the lobby protocol. As part of the response to a ''!list users'' command sent via private message, the autohost must list the usernames of all host admins, and at least one contactable host owner. This list should be kept up to date.

	Hosts with a botflag may add additional features and enforce restrictions on their use (such as rank limits, plugins, special game modes) providing that they meet the above expectations. In extreme cases, if lobby moderators judge that the above expectations are consistently not met, lobby moderators may require that particular people are added and/or removed as host admins or owners, or that particular features/restrictions are removed. Hosts that do not comply will lose their botflag.		Hosts with a botflag may add additional features and enforce restrictions on their use (such as rank limits, plugins, special game modes) providing that they meet the above expectations. In extreme cases, if lobby moderators judge that the above expectations are consistently not met, lobby moderators may require that particular people are added and/or removed as host admins or owners, or that particular features/restrictions are removed. Hosts that do not comply will lose their botflag.

			Hosts with a botflag are normally expected to use the latest stable engine version, or a later developmental version, and to host content that is made available for automated download.

	=== Battle hosts without a botflag ===		=== Battle hosts without a botflag ===

Silentwings: /* Battle hosts with a botflag */

2019-02-01T10:42:59Z

Battle hosts with a botflag

← Older revision		Revision as of 11:42, 1 February 2019
Line 12:		Line 12:
	=== Battle hosts with a botflag ===		=== Battle hosts with a botflag ===

	Hosts with a botflag are expected to encourage and maintain an environment in which users are able to play games, free from serious disruption and excessively hateful or obscene behavior. The are generally expected to use the latest stable engine version, or a later developmental version.		Hosts with a botflag are expected to encourage and maintain an environment in which users are able to play games, free from serious disruption and excessively hateful or obscene behavior. The are generally expected to use the latest stable engine version, or a later developmental version, and to host content that is automatically downloadable.

	Autohosts with a botflag are expected to appoint host owners and/or admins who are generally capable of maintaining the above expectations, with the help of the tools (pms/kicks/bans/mutes/plugins/etc) provided by the lobby server and SPADS. They should react and respond to all server commands in accordance with the lobby protocol. As part of the response to a ''!list users'' command sent via private message, the autohost must list the usernames of all host admins, and at least one contactable host owner. This list should be kept up to date.		Autohosts with a botflag are expected to appoint host owners and/or admins who are generally capable of maintaining the above expectations, with the help of the tools (pms/kicks/bans/mutes/plugins/etc) provided by the lobby server and SPADS. They should react and respond to all server commands in accordance with the lobby protocol. As part of the response to a ''!list users'' command sent via private message, the autohost must list the usernames of all host admins, and at least one contactable host owner. This list should be kept up to date.

Silentwings: /* Battle hosts on the lobby server */

2019-02-01T10:42:22Z

Battle hosts on the lobby server

← Older revision		Revision as of 11:42, 1 February 2019
Line 3:		Line 3:
	== Battle hosts on the lobby server ==		== Battle hosts on the lobby server ==

	All battle hosts that do not have a botflag are limited to a maximum of, plus spectators. This includes both human hosters and autohosts.		All battle hosts that do not have a botflag are limited to a maximum number of players, plus unlimited spectators. This includes both human hosters and autohosts.

	Host admins that would like to get a botflag for an Autohost need to create a new thread in the [https://springrts.com/phpbb/viewforum.php?f=16 Ingame Community Forum] with "Botflag request" as topic title and the lobby username which should get the botflag. ''Note: A botflagged user account should not be used to play games on, except when hosting; otherwise it will not function correctly.		Host admins that would like to get a botflag for an Autohost need to create a new thread in the [https://springrts.com/phpbb/viewforum.php?f=16 Ingame Community Forum] with "Botflag request" as topic title and the lobby username which should get the botflag. ''Note: A botflagged user account should not be used to play games on, except when hosting; otherwise it will not function correctly.

Silentwings: /* Battle hosts on the lobby server */

2019-02-01T10:41:53Z

Battle hosts on the lobby server

← Older revision		Revision as of 11:41, 1 February 2019
Line 3:		Line 3:
	== Battle hosts on the lobby server ==		== Battle hosts on the lobby server ==

	All battle hosts that do not have a botflag are limited to a maximum of ~~10 players~~, plus spectators. This includes both human hosters and autohosts.		All battle hosts that do not have a botflag are limited to a maximum of, plus spectators. This includes both human hosters and autohosts.

	Host admins that would like to get a botflag for an Autohost need to create a new thread in the [https://springrts.com/phpbb/viewforum.php?f=16 Ingame Community Forum] with "Botflag request" as topic title and the lobby username which should get the botflag. ''Note: A botflagged user account should not be used to play games on, except when hosting; otherwise it will not function correctly.		Host admins that would like to get a botflag for an Autohost need to create a new thread in the [https://springrts.com/phpbb/viewforum.php?f=16 Ingame Community Forum] with "Botflag request" as topic title and the lobby username which should get the botflag. ''Note: A botflagged user account should not be used to play games on, except when hosting; otherwise it will not function correctly.
Line 12:		Line 12:
	=== Battle hosts with a botflag ===		=== Battle hosts with a botflag ===

	Hosts with a botflag are expected to encourage and maintain an environment in which users are able to play games, free from serious disruption and excessively hateful or obscene behavior.		Hosts with a botflag are expected to encourage and maintain an environment in which users are able to play games, free from serious disruption and excessively hateful or obscene behavior. The are generally expected to use the latest stable engine version, or a later developmental version.

	Autohosts with a botflag are expected to appoint host owners and/or admins who are generally capable of maintaining the above expectations, with the help of the tools (pms/kicks/bans/mutes/plugins/etc) provided by the lobby server and SPADS. They should react and respond to all server commands in accordance with the lobby protocol. As part of the response to a ''!list users'' command sent via private message, the autohost must list the usernames of all host admins, and at least one contactable host owner. This list should be kept up to date.		Autohosts with a botflag are expected to appoint host owners and/or admins who are generally capable of maintaining the above expectations, with the help of the tools (pms/kicks/bans/mutes/plugins/etc) provided by the lobby server and SPADS. They should react and respond to all server commands in accordance with the lobby protocol. As part of the response to a ''!list users'' command sent via private message, the autohost must list the usernames of all host admins, and at least one contactable host owner. This list should be kept up to date.

Silentwings: /* Battle hosts with a botflag */

2018-12-30T12:11:58Z

Battle hosts with a botflag

← Older revision		Revision as of 13:11, 30 December 2018
Line 14:		Line 14:
	Hosts with a botflag are expected to encourage and maintain an environment in which users are able to play games, free from serious disruption and excessively hateful or obscene behavior.		Hosts with a botflag are expected to encourage and maintain an environment in which users are able to play games, free from serious disruption and excessively hateful or obscene behavior.

	Autohosts with a botflag are expected to appoint host owners and/or admins who are generally capable of maintaining the above expectations, with the help of the tools (pms/kicks/bans/mutes/plugins/etc) provided by the lobby server and SPADS. As part of the response to ~~a ''!admins'' and/or~~ a ''!list users'' command, the autohost must list the usernames of all host admins, and at least one contactable host owner. This should be kept up to date.		Autohosts with a botflag are expected to appoint host owners and/or admins who are generally capable of maintaining the above expectations, with the help of the tools (pms/kicks/bans/mutes/plugins/etc) provided by the lobby server and SPADS. They should react and respond to all server commands in accordance with the lobby protocol. As part of the response to a ''!list users'' command sent via private message, the autohost must list the usernames of all host admins, and at least one contactable host owner. This list should be kept up to date.

	Hosts with a botflag may add additional features and enforce restrictions on their use (such as rank limits, plugins, special game modes) providing that they meet the above expectations. In extreme cases, if lobby moderators judge that the above expectations are consistently not met, lobby moderators may require that particular people are added and/or removed as host admins or owners, or that particular features/restrictions are removed. Hosts that do not comply will lose their botflag.		Hosts with a botflag may add additional features and enforce restrictions on their use (such as rank limits, plugins, special game modes) providing that they meet the above expectations. In extreme cases, if lobby moderators judge that the above expectations are consistently not met, lobby moderators may require that particular people are added and/or removed as host admins or owners, or that particular features/restrictions are removed. Hosts that do not comply will lose their botflag.

Abma: /* Battle hosts on the lobby server */

2018-11-17T00:18:12Z

Battle hosts on the lobby server

← Older revision		Revision as of 01:18, 17 November 2018
Line 5:		Line 5:
	All battle hosts that do not have a botflag are limited to a maximum of 10 players, plus spectators. This includes both human hosters and autohosts.		All battle hosts that do not have a botflag are limited to a maximum of 10 players, plus spectators. This includes both human hosters and autohosts.

	~~Hosts~~ that would like to ~~be given~~ a botflag ~~should contact Springs moderators, either~~ in the [https://springrts.com/phpbb/viewforum.php?f=16 Ingame Community] ~~forum, or via a [https://springrts.com/phpbb/ucp.php?i=pm&mode=compose&g=1643 private message]~~. ''Note: A botflagged user account should not be used to play games on, except when hosting; otherwise it will not function correctly.		Host admins that would like to get a botflag for an Autohost need to create a new thread in the [https://springrts.com/phpbb/viewforum.php?f=16 Ingame Community Forum] with "Botflag request" as topic title and the lobby username which should get the botflag. ''Note: A botflagged user account should not be used to play games on, except when hosting; otherwise it will not function correctly.
	''		''

Silentwings: /* Battle hosts without a botflag */

2018-06-06T06:40:59Z

Battle hosts without a botflag

← Older revision		Revision as of 07:40, 6 June 2018
Line 20:		Line 20:
	=== Battle hosts without a botflag ===		=== Battle hosts without a botflag ===

	~~Autohosts~~ without a botflag are not subject to the same expectations as botflagged hosts, and are free to act as a private service provided by one or more users. Such hosts may arbitrarily appoint/remove their admins and owners, add additional features and enforce restrictions on their use, providing they remain within the terms of service of the lobby server.		Hosts without a botflag are not subject to the same expectations as botflagged hosts, and are free to act as a private service provided by one or more users. Such hosts may arbitrarily appoint/remove their admins and owners, add additional features and enforce restrictions on their use, providing they remain within the terms of service of the lobby server.

	=== Reporting ===		=== Reporting ===

Silentwings: /* Battle hosts with a botflag */

2018-04-24T20:30:39Z

Battle hosts with a botflag

← Older revision		Revision as of 21:30, 24 April 2018
Line 14:		Line 14:
	Hosts with a botflag are expected to encourage and maintain an environment in which users are able to play games, free from serious disruption and excessively hateful or obscene behavior.		Hosts with a botflag are expected to encourage and maintain an environment in which users are able to play games, free from serious disruption and excessively hateful or obscene behavior.

	Autohosts with a botflag are expected to appoint host owners and admins who are generally capable of maintaining the above expectations, with the help of the tools (pms/kicks/bans/mutes/etc) provided by the lobby server and SPADS. As part of the response to a ''!admins'' and/or a ''!list users'' command, the autohost must list the usernames of all host admins, and at least one contactable host owner. This should be kept up to date.		Autohosts with a botflag are expected to appoint host owners and/or admins who are generally capable of maintaining the above expectations, with the help of the tools (pms/kicks/bans/mutes/plugins/etc) provided by the lobby server and SPADS. As part of the response to a ''!admins'' and/or a ''!list users'' command, the autohost must list the usernames of all host admins, and at least one contactable host owner. This should be kept up to date.

	Hosts with a botflag may add additional features and enforce restrictions on their use (such as rank limits, plugins, special game modes) providing that they meet the above expectations. In extreme cases, if lobby moderators judge that the above expectations are consistently not met, lobby moderators may require that particular people are added and/or removed as host admins or owners, or that particular features/restrictions are removed. Hosts that do not comply will lose their botflag.		Hosts with a botflag may add additional features and enforce restrictions on their use (such as rank limits, plugins, special game modes) providing that they meet the above expectations. In extreme cases, if lobby moderators judge that the above expectations are consistently not met, lobby moderators may require that particular people are added and/or removed as host admins or owners, or that particular features/restrictions are removed. Hosts that do not comply will lose their botflag.