BukkitWiki

Welcome to the BukkitWiki!

This Wiki is home to Bukkit's documentation and regulations surrounding the Bukkit Project and it's services. Want to help out? We would love to have you! Signup to get started!

READ MORE

BukkitWiki
Don't have an account?
Register
Register
BukkitWiki
BukkitWiki
175
pages
in: Pages using deprecated source tags

Changes: Plugin YAML/nl

< Plugin YAML
Back to page
Sign in to edit
No edit summary
Xbony2 (talk | contribs)
m (Undo revision 13429 by 112.98.19.201 (talk))
 
Line 1: Line 1:
  +
Wanneer Bukkit een plugin laadt, moet Bukkit wat informatie over deze plugin weten. Deze informatie wordt gelezen van een YAML bestand, genaamd 'plugin.yml'. In dit bestand staan verschillende eigenschappen, waarvan elke op een nieuwe regel begint.
−
Warmly congratulate XCRailway team's creation in minecraft have exceed 40,000 chunks!<br/><h1>What is XCRailway Team?</h1>XCRailway is the focus of the Minecraft creation.XCRailway is the origin of the railway associations.XCRailway, a non-commercial non-profit Minecraft and Vocaloid railway creation team, founded on January 31, 2015, under the efforts of the founder xiaocao2015, has received extensive praise from the railway fans. XCRailway have created many fantastic works in many place. XCRailway have already had 1.5 million fans in China.<br/><h1>XCRailway Energy</h1>Whether under the void, or the unbuildable area that above the world height limit; Whether in the disordered Far Land, or land that is difficult to exploit, XCRailway are never stop exploring and building. XCRailway, disseminated railway to every corner of the Minecraft and Vocaloid world. We believe that railways can create miracles. We believe that we have the ability to promote the spirit of XCRailway. Through the creation of various works on the railway, the fans and members of XCRailway can get the energy of the divine railway.<br/><h1>Creations</h1>XCRailway, except for our minecraft world, created more than 40 pieces of music related to XCRailway; created more than 30 railway lines and locomotives in Railwork; XCRailway have received a wide range of praise all the time. XCRailway, in all walks of life, each dimension, each platform has a lot of excellent works.<br/><h1>Explorations</h1>In the exploration of the unknown dimension, XCRailway team summed up a set of track characteristics of creative planning and methods. Since its inception to March 2017, a large number of fans and members of XCRailway support us. XCRailway members, like Xionglong , Yudian Xuehua, etc. have contributed greatly to the creation of XCRailway. So far, XCRailway has more than 1 million subscribers in weibo.XCRailway team will continue to flourish with the support of everyone.<br/><h1>In the end</h1>XCRailway, will overturn all the obstacles along the way forward, efforts to advance, continue to create, to promote the XCRailway team - specific spirit of the railway, keep healthy and vigorous developing, create more excellent works, create miracle in the railway world,in the every dimensions!<br/><h1>Contact/Join Us</h1>Zhihu : www.zhihu.com/people/XCRailway/activities<br/>Weibo : weibo.com/xiaocao2015<br/>Bilibili : space.bilibili.com/66261012<br/>Telephone: ( 86) 135 0452 3672 (use Chinese only)
  
  +
  +
{| cellspacing="0" cellpadding="4" border="1" class="wikitable"
  +
|+ Eigenschappen
  +
|-
  +
! Eigenschap
  +
! Benodigd
  +
! Beschrijving
  +
! Voorbeeld
  +
! Handig om te weten
  +
|- style="font-weight: bold;"
  +
| name
  +
| ja
  +
| De naam van de plugin.
  +
| <code>name: MyPlugin</code>
  +
|
  +
*Kan bestaan uit alle alfanumerieke karakters en underscores (a-z,A-Z,0-9, _)
  +
*Wordt gebruikt om de datafolder van de plugin te vinden. De datafolder van een plugin staat standaard in ./plugins/
  +
*Het is slim om het .jar bestand van de plugin hetzelfde te noemen als de naam, bijvoorbeeld 'MyPlugin.jar'
  +
  +
|- style="font-weight: bold;"
  +
| version
  +
| ja
  +
| De versie van de plugin
  +
| <code>version: 1.4.1</code>
  +
|
  +
*De versie is een willekeurige tekst, maar het wordt meestal op de volgende manier gebruikt: MajorRelease.MinorRelease.Build (eg: 1.4.1).
  +
*Het versie nummer wordt normaal veranderd als er een bugfix is of als er nieuwe functies zijn toegevoegd.
  +
*Wordt weergegeven als het commando <code>/version <plugin></code> wordt uitgevoerd.
  +
  +
|-
  +
| description
  +
| nee
  +
| Een gebruiksvriendelijke beschrijving van wat de plugin kan.
  +
| <code>description: Met deze plugin kun je jezelf in de fik zetten.</code>
  +
|
  +
*De beschrijving kan uit meerdere regels bestaan.
  +
*Wordt weergegeven als het commando <code>/version <plugin></code> wordt uitgevoerd.
  +
  +
|-
  +
| load
  +
| nee
  +
| Explicitly state when the plugin should be loaded. if not supplied will default to postworld
  +
| <code> load: STARTUP </code>
  +
| Heeft twee mogelijke waarden:
  +
* STARTUP
  +
* POSTWORLD
  +
|-
  +
| author
  +
|nee
  +
| Uniquely identifies who developed this plugin.
  +
| <code>author: CaptainInflamo</code>
  +
|
  +
*Gives credit to the developer.
  +
*Used in some server error messages to provide helpful feedback on who to contact when an error occurs.
  +
*A bukkit.org forum handle or email address is recommended.
  +
*Is displayed when a user types /version PluginName
  +
  +
|-
  +
| authors
  +
|nee
  +
| Allows you to list multiple authors, if it is a collaborative project. See author.
  +
| <code>authors: [Cogito, verrier, EvilSeph]</code>
  +
|
  +
*You can define both author and authors, however they will be merged into one list internally.
  +
  +
|-
  +
| website
  +
|nee
  +
| De website van de maker van de plugin.
  +
| <code>website: http://forums.bukkit.org/threads/MyPlugin.31337/</code>
  +
|
  +
*If you have no dedicated website, a link to the Bukkit forum post where this plugin is listed is highly recommended.
  +
*Displayed when a user types <code>/version PluginName</code>
  +
  +
|- style="font-weight: bold;"
  +
| main
  +
|ja
  +
| Wijst op de klasse die JavaPlugin uitbreidt.
  +
| <code>main: org.bukkit.plugin.MyPlugin</code>
  +
|
  +
*Note that this must contain the full namespace including the class file itself.
  +
*If your namespace is <code>org.bukkit.plugin</code>, and your class file is called <code>MyPlugin</code> then this must be <code>org.bukkit.plugin.MyPlugin</code>
  +
  +
|-
  +
| database
  +
|nee
  +
| Stel dit in op true als de plugin een database gebruikt.
  +
| <code>database: false</code>
  +
|
  +
*Using a database is non-trivial. See [[Plugin_Databases]]
  +
  +
|-
  +
| depend
  +
|nee
  +
| Een lijst met plugins die jouw plugin nodig heeft.
  +
| <code>depend: [OnePlugin, AnotherPlugin]</code>
  +
|
  +
*The value must be in YAML list format (See http://en.wikipedia.org/wiki/YAML#Lists )
  +
*Use the "name" attribute of the required plugin in order to specify the dependency.
  +
*If any plugin listed here is not found your plugin will fail to load.
  +
*If multiple plugins list each other as a depend, so that there are no plugins without an unloadable dependency, all will fail to load.
  +
*(See: Wiki: Plugin_Dependencies)
  +
|-
  +
| prefix
  +
|nee
  +
| De naam die wordt gebruikt bij het loggen naar de console in plaats van de naam van de plugin.
  +
| <code>prefix: ex-why-zee</code>
  +
|
  +
|-
  +
| softdepend
  +
|nee
  +
| Een lijst met plugins die nodig zijn om jouw plugin volledig te laten functioneren.
  +
| <code>softdepend: [OnePlugin, AnotherPlugin]</code>
  +
|
  +
*The value must be in YAML list format (See http://en.wikipedia.org/wiki/YAML#Lists )
  +
*Use the "name" atrribute of the desired plugin in order to specify the dependancy.
  +
*Your plugin will load after any plugins listed here.
  +
*Circular soft dependencies are loaded arbitrarily.
  +
*(See: Wiki: Plugin_Dependencies)
  +
  +
|-
  +
| loadbefore
  +
|nee
  +
| Een lijst met plugins die moeten worden geladen voor jouw plugin.
  +
| <code>loadbefore: [OnePlugin, AnotherPlugin]</code>
  +
|
  +
*The value must be in YAML list format (See http://en.wikipedia.org/wiki/YAML#Lists )
  +
*Treated as if the listed plugin soft depends on the specifying plugin.
  +
*Use the "name" atrribute of the desired plugin in order to specify the target.
  +
*Your plugin will load before any plugins listed here.
  +
*Circular soft dependencies are loaded arbitrarily.
  +
*(See: Wiki: Plugin_Dependencies)
  +
  +
|-
  +
| commands
  +
|nee
  +
| The name of a command the plugin wishes to register, as well as an optional list of command attributes.
  +
|
  +
<code>
  +
commands:
  +
flagrate:
  +
[optional command attributes]
  +
</code>
  +
  +
|
  +
*The command name should not contain the leading '/' required to issue a command.
  +
*You can choose any command name you wish, however 'common' commands such as <code>/kick</code> are often already registered. Use the 'alias' command attribute to supply alternate names. @TODO: verify we're happy with this
  +
  +
|-
  +
| permissions
  +
|nee
  +
| Permissions that the plugin whishes to register. Each node represents a permission to register. Each permission can have additional attributes.
  +
| <pre>permissions:
  +
inferno.*:
  +
[optional permission attributes]
  +
inferno.flagate:
  +
[optional permission attributes]
  +
inferno.burningdeaths:
  +
[optional permission attributes]</pre>
  +
|
  +
*Permission registration is optional, can also be done from code
  +
*Permission registration allows you to set descriptions, defaults, and child parent relationships
  +
*Permission names should be kept in the style of &lt;pluginname&gt;.[category].[category].&lt;permission&gt;
  +
  +
|}
  +
  +
  +
A command block starts with the command's name, and then has a list of attributes.
  +
  +
{| cellspacing="0" cellpadding="4" border="1" class="wikitable"
  +
|-
  +
! Command Attribute
  +
! Benodigd
  +
! Beschrijving
  +
! Voorbeeld
  +
! Handig om te weten
  +
|-
  +
| description
  +
| nee
  +
| Een korte beschrijving van wat het commando doet.
  +
| <code>description: Set yourself on fire</code>
  +
|
  +
*Can be used in conjunction with /help
  +
  +
|-
  +
| aliases
  +
| nee
  +
| Alternate command names a user may use instead
  +
|
  +
<code>aliases: combust_me</code> OR
  +
<code>aliases: [combust_me, combustMe, cm]</code>
  +
  +
|
  +
*You can specify any of none, 1 or many aliases.
  +
*If you specify more than one alias, they must be in YAML list format (See http://en.wikipedia.org/wiki/YAML#Lists )
  +
  +
|-
  +
| permission
  +
| nee
  +
| De meest basale permissie die nodig is om dit commando uit te voeren.
  +
|
  +
<code>permission: inferno.flagrate</code>
  +
  +
|
  +
*This permissions node can be used to determine if a user should be able to see this command
  +
*Some plugins will use this node to construct a personalized /help
  +
|-
  +
| permission-message
  +
|nee
  +
| Het geen-permissie bericht.
  +
| <code>permission-message: You do not have /&lt;permission&gt;</code>
  +
|
  +
*Displayed to a player that attempts to use a command but does not have the associated permission
  +
*&lt;permission&gt; is a macro that is replaced with the permission node that is required to use the command.
  +
*You may use empty quotes to indicate nothing should be displayed.
  +
  +
|-
  +
| usage
  +
|nee
  +
| Een korte beschrijving van hoe je het commando moet gebruiken.
  +
| <code>usage: Syntax error! Perhaps you meant /&lt;command&gt; PlayerName?</code>
  +
|
  +
*Displayed to whoever issued the command when the plugin's command handler (onCommand typically) does not return true.
  +
*&lt;command&gt; is a macro that is replaced with the command issued wherever it occurs.
  +
*To use the string "Usage:" (i.e. <code>usage: Usage: /god [player]</code>, surround the text after the usage: label with double-quotes:<br> <code>usage: "Usage: /god [player]"</code>
  +
  +
|}
  +
  +
  +
A permission block starts with the permission's name and is followed by nodes of attributes
  +
  +
{| cellspacing="0" cellpadding="4" border="1" class="wikitable"
  +
|-
  +
! Permission Attribute
  +
!Voorbeeld
  +
!Beschrijving
  +
!Voorbeeld
  +
!Handig om te weten
  +
|-
  +
| description
  +
|nee
  +
| Een korte beschrijving van wat deze permissie toestaat.
  +
| <pre>description: Allows you to set yourself on fire</pre>
  +
|
  +
*Allows programmatic access, and helps server administrators
  +
  +
|-
  +
| default
  +
|nee
  +
| Stelt de standaardwaarde van deze permissie in.
  +
| <pre>default: true</pre>
  +
|
  +
*If node does not exist the permission defaults to op
  +
*allowed defaults are: true, false, op, not op
  +
*op default will be true if player is op
  +
*no op default is the opposite behavior (of op)
  +
  +
|-
  +
| children
  +
|nee
  +
| Geeft de mogelijkheid in subpermissies in te stellen. De subpermissies zijn de permissienamen.
  +
| <pre>children:
  +
inferno.flagrate: true
  +
inferno.burningdeaths: true</pre>
  +
|
  +
*Each child node must be either set to true or false
  +
**a child node of true inherits the parent permission
  +
**a child node of false inherits the inverse parent permission
  +
* Can also contain other permission nodes [https://github.com/bukkit/bukkit/commit/326f2aca9b98d1d096842d3410000ed9d84611f5 {1}]
  +
  +
|}
  +
  +
Voorbeeld:<source lang="yaml" style="border: 1px #aaa solid;">
  +
name: Inferno
  +
version: 1.4.1
  +
description: This plugin is so 31337. You can set yourself on fire.
  +
# We could place every author in the authors list, but chose not to for illustrative purposes
  +
# Also, having an author distinguishes that person as the project lead, and ensures their
  +
# name is displayed first
  +
author: CaptainInflamo
  +
authors: [Cogito, verrier, EvilSeph]
  +
website: http://forums.bukkit.org/threads/MyPlugin.31337/
  +
  +
main: com.captaininflamo.bukkit.inferno.Inferno
  +
database: false
  +
depend: [NewFire, FlameWire]
  +
  +
commands:
  +
flagrate:
  +
description: Set yourself on fire.
  +
aliases: [combust_me, combustMe]
  +
permission: inferno.flagrate
  +
usage: Syntax error! Simply type /&lt;command&gt; to ignite yourself.
  +
burningdeaths:
  +
description: List how many times you have died by fire.
  +
aliases: [burning_deaths, burningDeaths]
  +
permission: inferno.burningdeaths
  +
usage: |
  +
/&lt;command&gt; [player]
  +
Example: /&lt;command&gt; - see how many times you have burned to death
  +
Example: /&lt;command&gt; CaptainIce - see how many times CaptainIce has burned to death
  +
  +
permissions:
  +
inferno.*:
  +
description: Gives access to all Inferno commands
  +
children:
  +
inferno.flagrate: true
  +
inferno.burningdeaths: true
  +
inferno.burningdeaths.others: true
  +
inferno.flagrate:
  +
description: Allows you to ignite yourself
  +
default: true
  +
inferno.burningdeaths:
  +
description: Allows you to see how many times you have burned to death
  +
default: true
  +
inferno.burningdeaths.others:
  +
description: Allows you to see how many times others have burned to death
  +
default: op
  +
children:
  +
inferno.burningdeaths: true
  +
</source>
  +
  +
{{Languages|Plugin YAML}}

Latest revision as of 14:31, 25 June 2017

Wanneer Bukkit een plugin laadt, moet Bukkit wat informatie over deze plugin weten. Deze informatie wordt gelezen van een YAML bestand, genaamd 'plugin.yml'. In dit bestand staan verschillende eigenschappen, waarvan elke op een nieuwe regel begint.

Eigenschappen
Eigenschap Benodigd Beschrijving Voorbeeld Handig om te weten
name ja De naam van de plugin. name: MyPlugin
  • Kan bestaan uit alle alfanumerieke karakters en underscores (a-z,A-Z,0-9, _)
  • Wordt gebruikt om de datafolder van de plugin te vinden. De datafolder van een plugin staat standaard in ./plugins/
  • Het is slim om het .jar bestand van de plugin hetzelfde te noemen als de naam, bijvoorbeeld 'MyPlugin.jar'
version ja De versie van de plugin version: 1.4.1
  • De versie is een willekeurige tekst, maar het wordt meestal op de volgende manier gebruikt: MajorRelease.MinorRelease.Build (eg: 1.4.1).
  • Het versie nummer wordt normaal veranderd als er een bugfix is of als er nieuwe functies zijn toegevoegd.
  • Wordt weergegeven als het commando /version <plugin> wordt uitgevoerd.
description nee Een gebruiksvriendelijke beschrijving van wat de plugin kan. description: Met deze plugin kun je jezelf in de fik zetten.
  • De beschrijving kan uit meerdere regels bestaan.
  • Wordt weergegeven als het commando /version <plugin> wordt uitgevoerd.
load nee Explicitly state when the plugin should be loaded. if not supplied will default to postworld load: STARTUP Heeft twee mogelijke waarden:
  • STARTUP
  • POSTWORLD
author nee Uniquely identifies who developed this plugin. author: CaptainInflamo
  • Gives credit to the developer.
  • Used in some server error messages to provide helpful feedback on who to contact when an error occurs.
  • A bukkit.org forum handle or email address is recommended.
  • Is displayed when a user types /version PluginName
authors nee Allows you to list multiple authors, if it is a collaborative project. See author. authors: [Cogito, verrier, EvilSeph]
  • You can define both author and authors, however they will be merged into one list internally.
website nee De website van de maker van de plugin. website: http://forums.bukkit.org/threads/MyPlugin.31337/
  • If you have no dedicated website, a link to the Bukkit forum post where this plugin is listed is highly recommended.
  • Displayed when a user types /version PluginName
main ja Wijst op de klasse die JavaPlugin uitbreidt. main: org.bukkit.plugin.MyPlugin
  • Note that this must contain the full namespace including the class file itself.
  • If your namespace is org.bukkit.plugin, and your class file is called MyPlugin then this must be org.bukkit.plugin.MyPlugin
database nee Stel dit in op true als de plugin een database gebruikt. database: false
depend nee Een lijst met plugins die jouw plugin nodig heeft. depend: [OnePlugin, AnotherPlugin]
  • The value must be in YAML list format (See http://en.wikipedia.org/wiki/YAML#Lists )
  • Use the "name" attribute of the required plugin in order to specify the dependency.
  • If any plugin listed here is not found your plugin will fail to load.
  • If multiple plugins list each other as a depend, so that there are no plugins without an unloadable dependency, all will fail to load.
  • (See: Wiki: Plugin_Dependencies)
prefix nee De naam die wordt gebruikt bij het loggen naar de console in plaats van de naam van de plugin. prefix: ex-why-zee
softdepend nee Een lijst met plugins die nodig zijn om jouw plugin volledig te laten functioneren. softdepend: [OnePlugin, AnotherPlugin]
  • The value must be in YAML list format (See http://en.wikipedia.org/wiki/YAML#Lists )
  • Use the "name" atrribute of the desired plugin in order to specify the dependancy.
  • Your plugin will load after any plugins listed here.
  • Circular soft dependencies are loaded arbitrarily.
  • (See: Wiki: Plugin_Dependencies)
loadbefore nee Een lijst met plugins die moeten worden geladen voor jouw plugin. loadbefore: [OnePlugin, AnotherPlugin]
  • The value must be in YAML list format (See http://en.wikipedia.org/wiki/YAML#Lists )
  • Treated as if the listed plugin soft depends on the specifying plugin.
  • Use the "name" atrribute of the desired plugin in order to specify the target.
  • Your plugin will load before any plugins listed here.
  • Circular soft dependencies are loaded arbitrarily.
  • (See: Wiki: Plugin_Dependencies)
commands nee The name of a command the plugin wishes to register, as well as an optional list of command attributes. 

commands:
 flagrate:
   [optional command attributes]

  • The command name should not contain the leading '/' required to issue a command.
  • You can choose any command name you wish, however 'common' commands such as /kick are often already registered. Use the 'alias' command attribute to supply alternate names. @TODO: verify we're happy with this
permissions nee Permissions that the plugin whishes to register. Each node represents a permission to register. Each permission can have additional attributes. 
permissions:
  inferno.*:
    [optional permission attributes]
  inferno.flagate:
    [optional permission attributes]
  inferno.burningdeaths:
    [optional permission attributes]
  • Permission registration is optional, can also be done from code
  • Permission registration allows you to set descriptions, defaults, and child parent relationships
  • Permission names should be kept in the style of <pluginname>.[category].[category].<permission>


A command block starts with the command's name, and then has a list of attributes.

Command Attribute Benodigd Beschrijving Voorbeeld Handig om te weten
description nee Een korte beschrijving van wat het commando doet. description: Set yourself on fire
  • Can be used in conjunction with /help
aliases nee Alternate command names a user may use instead 
aliases: combust_me OR 
aliases: [combust_me, combustMe, cm]
permission nee De meest basale permissie die nodig is om dit commando uit te voeren. 
permission: inferno.flagrate
  • This permissions node can be used to determine if a user should be able to see this command
  • Some plugins will use this node to construct a personalized /help
permission-message nee Het geen-permissie bericht. permission-message: You do not have /<permission>
  • Displayed to a player that attempts to use a command but does not have the associated permission
  • <permission> is a macro that is replaced with the permission node that is required to use the command.
  • You may use empty quotes to indicate nothing should be displayed.
usage nee Een korte beschrijving van hoe je het commando moet gebruiken. usage: Syntax error! Perhaps you meant /<command> PlayerName?
  • Displayed to whoever issued the command when the plugin's command handler (onCommand typically) does not return true.
  • <command> is a macro that is replaced with the command issued wherever it occurs.
  • To use the string "Usage:" (i.e. usage: Usage: /god [player], surround the text after the usage: label with double-quotes:
    usage: "Usage: /god [player]"


A permission block starts with the permission's name and is followed by nodes of attributes

Permission Attribute Voorbeeld Beschrijving Voorbeeld Handig om te weten
description nee Een korte beschrijving van wat deze permissie toestaat. 
description: Allows you to set yourself on fire
  • Allows programmatic access, and helps server administrators
default nee Stelt de standaardwaarde van deze permissie in. 
default: true
  • If node does not exist the permission defaults to op
  • allowed defaults are: true, false, op, not op
  • op default will be true if player is op
  • no op default is the opposite behavior (of op)
children nee Geeft de mogelijkheid in subpermissies in te stellen. De subpermissies zijn de permissienamen. 
children:
  inferno.flagrate: true
  inferno.burningdeaths: true
  • Each child node must be either set to true or false
    • a child node of true inherits the parent permission
    • a child node of false inherits the inverse parent permission
  • Can also contain other permission nodes {1}

Voorbeeld:

 name: Inferno
 version: 1.4.1
 description: This plugin is so 31337. You can set yourself on fire.
 # We could place every author in the authors list, but chose not to for illustrative purposes
 # Also, having an author distinguishes that person as the project lead, and ensures their 
 # name is displayed first
 author: CaptainInflamo
 authors: [Cogito, verrier, EvilSeph] 
 website: http://forums.bukkit.org/threads/MyPlugin.31337/
 
 main: com.captaininflamo.bukkit.inferno.Inferno
 database: false
 depend: [NewFire, FlameWire]
 
 commands:
   flagrate:
     description: Set yourself on fire.
     aliases: [combust_me, combustMe]
     permission: inferno.flagrate
     usage: Syntax error! Simply type /&lt;command&gt; to ignite yourself.
   burningdeaths:
     description: List how many times you have died by fire.
     aliases: [burning_deaths, burningDeaths]
     permission: inferno.burningdeaths
     usage: |
       /&lt;command&gt; [player]
       Example: /&lt;command&gt; - see how many times you have burned to death
       Example: /&lt;command&gt; CaptainIce - see how many times CaptainIce has burned to death
 
 permissions:
   inferno.*:
     description: Gives access to all Inferno commands
     children:
       inferno.flagrate: true
       inferno.burningdeaths: true
       inferno.burningdeaths.others: true
   inferno.flagrate:
     description: Allows you to ignite yourself
     default: true
   inferno.burningdeaths:
     description: Allows you to see how many times you have burned to death
     default: true
   inferno.burningdeaths.others:
     description: Allows you to see how many times others have burned to death
     default: op
     children:
       inferno.burningdeaths: true
Language   English • беларуская • Deutsch • español • suomi • français • italiano • 한국어 • Nederlands • norsk • polski • português • русский • lietuvių • čeština
Community content is available under CC BY-NC-SA unless otherwise noted.