| Local chat distance | Base Y-Level | Bonus per block above base |
|---|---|---|
| 1,000 | 100 | 1 |
Chat: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
(n/a alias cells) |
(link civ) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Mechanics series}} |
{{Mechanics series}} |
||
Civ servers commonly modify how chat messages are sent and received. In contrast to most Minecraft servers, chat messages on most Civ servers are not global, but can only be read by players within a certain number of blocks. This distance varies by server, but is typically around a thousand blocks. Messages can also be sent to a specific [[NameLayer]] group, where they are only readable by members in that group. |
[[Civ]] servers commonly modify how chat messages are sent and received. In contrast to most Minecraft servers, chat messages on most Civ servers are not global, but can only be read by players within a certain number of blocks. This distance varies by server, but is typically around a thousand blocks. Messages can also be sent to a specific [[NameLayer]] group, where they are only readable by members in that group. |
||
This was originally intended to create a sense of local community among nearby nations and to restrict the flow of information. However, [[Devoted]] introduced the concept of a [[global group]], where chat messages are not restricted by distance. This global group has been included in every [[mainline]] server since Devoted. |
This was originally intended to create a sense of local community among nearby nations and to restrict the flow of information. However, [[Devoted]] introduced the concept of a [[global group]], where chat messages are not restricted by distance. This global group has been included in every [[mainline]] server since Devoted. |
||
| Line 10: | Line 10: | ||
== Mechanics == |
== Mechanics == |
||
[[File:Civchat Example.png|thumb|500px|The first line is output caused by typing <code>/g Circleblob</code>. The second and third line display a message that was types as-is. The fourth line, in yellow, is the output of typing <code>/g</code>. The fifth line was typed as-is.]]When sending a |
[[File:Civchat Example.png|thumb|500px|The first line is output caused by typing <code>/g Circleblob</code>. The second and third line display a message that was types as-is. The fourth line, in yellow, is the output of typing <code>/g</code>. The fifth line was typed as-is.]]When not sending messages to a particular NameLayer group (referred to as using ''local chat''), only users within a certain radius of you will be able to see the message. This radius can be increased depending on your y-level, giving a bonus for each block above the base y-level. |
||
<tabber> |
|||
|-|CivMC= |
|||
You can also switch your chat group from local chat to a Namelayer group with the <code>/g <group></code> command. Messages sent to a Namelayer group will be visible to anybody in that group with the read messages permission, regardless of how far away they are. |
|||
{| class="wikitable" |
|||
|+ |
|||
Direct messages will also bypass the distance restriction. |
|||
!Local chat distance |
|||
!Base Y-Level |
|||
!Bonus per block above base |
|||
|- |
|||
|1,000 |
|||
|100 |
|||
|1 |
|||
|} |
|||
|-|CivClassic 2.0= |
|||
{| class="wikitable" |
|||
|+ |
|||
!Local chat distance |
|||
!Base Y-Level |
|||
!Bonus per block above base |
|||
|- |
|||
|1,000 |
|||
|100 |
|||
|1 |
|||
|} |
|||
|-|Devoted 3.0= |
|||
{| class="wikitable" |
|||
|+ |
|||
!Local chat distance |
|||
!Base Y-Level |
|||
!Bonus per block above base |
|||
|- |
|||
|1,000 |
|||
|100 |
|||
|1 |
|||
|} |
|||
|-|CivCraft 3.0= |
|||
{| class="wikitable" |
|||
|+ |
|||
!Local chat distance |
|||
!Base Y-Level |
|||
!Bonus per block above base |
|||
|- |
|||
|1,000 |
|||
|100 |
|||
|1 |
|||
|} |
|||
|-|CivCraft 2.0= |
|||
{| class="wikitable" |
|||
|+ |
|||
!Local chat distance |
|||
!Base Y-Level |
|||
!Bonus per block above base |
|||
|- |
|||
|1,000 |
|||
|100 |
|||
|1 |
|||
|} |
|||
|-|CivCraft 1.0= |
|||
{| class="wikitable" |
|||
|+ |
|||
!Local chat distance |
|||
!Base Y-Level |
|||
!Bonus per block above base |
|||
|- |
|||
|1,000 |
|||
|100 |
|||
|1 |
|||
|} |
|||
</tabber> |
|||
== |
=== Groups === |
||
To switch to chatting in a NameLayer group, use the <code>/g <group></code> command. Messages sent to a group are not affected by the distance restriction, and can be read by anybody on that group. |
|||
=== Private Messages === |
|||
Some civ servers have a Namelayer group for the sole purpose of providing a global chat. This group is usually called <code>!</code> or <code>g</code>. It is used to effectively bypass the local chat restrictions and send messages which are visible to anybody, regardless of distance. |
|||
You can switch to a private message group with another player by using the <code>/tell <player></code> command. Messages sent to private message groups are also unaffected by the distance restriction. |
|||
=== Death Messages === |
|||
In earlier civ servers such as [[Devoted]], this global chat group was entirely player-owned and managed, requiring players to join the group manually before being able to talk in it. Some later civ servers like [[CivClassic]] cemented the global chat group as a gameplay mechanic, automatically adding new players as members to the group and having the group be admin owned. However, not all civ servers do this. |
|||
One consequence of the distance-restricted nature of chat messages is that death messages are not necessarily broadcast to the entire server. This means that some players may not become aware of important events, like a player being [[Exile Pearl|pearled]], until it is later chosen to be publicized. |
|||
== Command Reference == |
== Command Reference == |
||
| Line 31: | Line 98: | ||
| <code>/g [group] [message]</code> |
| <code>/g [group] [message]</code> |
||
| If just <code>group</code> is specified, sets your current chat group to <code>group</code>. |
| If just <code>group</code> is specified, sets your current chat group to <code>group</code>. |
||
If both <code>group</code> and <code>message</code> are specified, sends <code>message</code> to <code>group</code> without changing your current group. |
If both <code>group</code> and <code>message</code> are specified, sends <code>message</code> to <code>group</code> without changing your current chat group. |
||
If neither <code>group</code> nor <code>message</code> is specified, acts like <code>/exit</code>. |
If neither <code>group</code> nor <code>message</code> is specified, acts like <code>/exit</code>. |
||
| Line 37: | Line 104: | ||
|- |
|- |
||
|<code>/exit</code> |
|<code>/exit</code> |
||
|Sets your current group to |
|Sets your current chat group to local chat (messages are only visible locally). |
||
|<code>/e</code> |
|<code>/e</code> |
||
|- |
|- |
||
| <code>/tell <player> [message]</code> |
| <code>/tell <player> [message]</code> |
||
| Sends <code>message</code> to <code>player</code>. If <code>message</code> is not specified, switches your current group to be a private chat with <code>player</code> instead. |
| Sends a private <code>message</code> to <code>player</code>. If <code>message</code> is not specified, switches your current chat group to be a private chat with <code>player</code> instead. |
||
| <code>/message</code> <code>/msg</code> <code>/m</code> <code>/pm</code> |
| <code>/message</code> <code>/msg</code> <code>/m</code> <code>/pm</code> |
||
|- |
|- |
||
| Line 49: | Line 116: | ||
|- |
|- |
||
| <code>/ignore <player></code> |
| <code>/ignore <player></code> |
||
| Toggles ignoring <code>player</code>. You will not see any messages, in any group |
| Toggles ignoring <code>player</code>. You will not see any messages, in any group, from an ignored player. |
||
| <code>/i</code> |
| <code>/i</code> |
||
|- |
|- |
||
Latest revision as of 23:56, 13 December 2023
| Part of a series on |
| Mechanics and Plugins |
|---|
 |
| Core Mechanics |
| Common Mechanics |
| Minor Mechanics |
Civ servers commonly modify how chat messages are sent and received. In contrast to most Minecraft servers, chat messages on most Civ servers are not global, but can only be read by players within a certain number of blocks. This distance varies by server, but is typically around a thousand blocks. Messages can also be sent to a specific NameLayer group, where they are only readable by members in that group.
This was originally intended to create a sense of local community among nearby nations and to restrict the flow of information. However, Devoted introduced the concept of a global group, where chat messages are not restricted by distance. This global group has been included in every mainline server since Devoted.
Messages sent to NameLayer groups do not have any restriction on distance, and can be read by anybody in that group.
The mechanic of chat messages being readable only by nearby players is a staple of the Civ genre. First introduced in CivCraft, this mechanic has been included in every mainline server since, as well as virtually every non-mainline server.
Mechanics
/g Circleblob. The second and third line display a message that was types as-is. The fourth line, in yellow, is the output of typing /g. The fifth line was typed as-is.When not sending messages to a particular NameLayer group (referred to as using local chat), only users within a certain radius of you will be able to see the message. This radius can be increased depending on your y-level, giving a bonus for each block above the base y-level.
| Local chat distance | Base Y-Level | Bonus per block above base |
|---|---|---|
| 1,000 | 100 | 1 |
| Local chat distance | Base Y-Level | Bonus per block above base |
|---|---|---|
| 1,000 | 100 | 1 |
| Local chat distance | Base Y-Level | Bonus per block above base |
|---|---|---|
| 1,000 | 100 | 1 |
| Local chat distance | Base Y-Level | Bonus per block above base |
|---|---|---|
| 1,000 | 100 | 1 |
| Local chat distance | Base Y-Level | Bonus per block above base |
|---|---|---|
| 1,000 | 100 | 1 |
Groups
To switch to chatting in a NameLayer group, use the /g <group> command. Messages sent to a group are not affected by the distance restriction, and can be read by anybody on that group.
Private Messages
You can switch to a private message group with another player by using the /tell <player> command. Messages sent to private message groups are also unaffected by the distance restriction.
Death Messages
One consequence of the distance-restricted nature of chat messages is that death messages are not necessarily broadcast to the entire server. This means that some players may not become aware of important events, like a player being pearled, until it is later chosen to be publicized.
Command Reference
| Command | Description | Alias |
|---|---|---|
/g [group] [message]
|
If just group is specified, sets your current chat group to group.
If both If neither |
/groupchat /gchat /gc
|
/exit
|
Sets your current chat group to local chat (messages are only visible locally). | /e
|
/tell <player> [message]
|
Sends a private message to player. If message is not specified, switches your current chat group to be a private chat with player instead.
|
/message /msg /m /pm
|
/reply [message]
|
Acts the same as /tell, but automatically sets <player> to be the last player to send you a private message.
|
/r
|
/ignore <player>
|
Toggles ignoring player. You will not see any messages, in any group, from an ignored player.
|
/i
|
/ignoregroup <group>
|
Toggles ignoring group. You will not see any messages sent to an ignored group.
|
/ig /igroup /ignoreg
|
/ignorelist
|
List ignored groups and players. | — |
/afk
|
Toggles afk (away from keyboard) state. While afk, any private messages sent to you will be automatically replied to with a preset afk message. | — |