Skip to content

Commit

Permalink
Renamed MCServer to Cuberite.
Browse files Browse the repository at this point in the history
  • Loading branch information
madmaxoft committed Jan 1, 2016
1 parent ac6ad21 commit d73f95a
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion CurrentLng.lua
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
-- CurrentLng.lua
-- This file provides all the translatable strings
-- The expectation is that the translators will create copies of this file, translate the texts and then the users will overwrite this file with a specific language version
-- Note that the individual languages must not have ".lua" extension, otherwise MCServer will load them and the plugin won't work!
-- Note that the individual languages must not have ".lua" extension, otherwise Cuberite will load them and the plugin won't work!



Expand Down
4 changes: 2 additions & 2 deletions Info.lua
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ g_PluginInfo =
of the overlapping areas, they are allowed to build / dig.
The protected areas are stored in an SQLite database in a file "ProtectionAreas.sqlite" that is created
next to the MCServer executable. The plugin has its configuration options stored in a
next to the Cuberite executable. The plugin has its configuration options stored in a
"ProtectionAreas.ini" file.
]],

Expand All @@ -33,7 +33,7 @@ g_PluginInfo =
Title = "Configuration",
Contents =
[[
The configuration is stored in the ProtectionAreas.ini file next to the MCServer executable in a
The configuration is stored in the ProtectionAreas.ini file next to the Cuberite executable in a
regular manner.
The wand item can be specified in the configuration. By default, a stick with meta 1 is used, but
Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,10 @@ This plugin lets VIP users define areas of the world where only specified users

An area is defined by the VIP by using a Wand item (by default, a stick with a meta 1) by left-clicking and right-clicking in two opposite corners of the area, then issuing a /protection add command. Multiple users can be allowed in a single area. There is no hardcoded limit on the number of areas or the number of players allowed in a single area. Areas can overlap; in such a case, if a user is allowed in any one of the overlapping areas, they are allowed to build / dig.

The protected areas are stored in an SQLite database in a file "ProtectionAreas.sqlite" that is created next to the MCServer executable. The plugin has its configuration options stored in a "ProtectionAreas.ini" file.
The protected areas are stored in an SQLite database in a file "ProtectionAreas.sqlite" that is created next to the Cuberite executable. The plugin has its configuration options stored in a "ProtectionAreas.ini" file.

# Configuration
The configuration is stored in the ProtectionAreas.ini file next to the MCServer executable in a regular manner.
The configuration is stored in the ProtectionAreas.ini file next to the Cuberite executable in a regular manner.

The wand item can be specified in the configuration. By default, a stick with meta 1 is used, but any valid item can be used. Stored in the [ProtectionAreas].WandItem value.

Expand Down

0 comments on commit d73f95a

Please sign in to comment.