Translating 1130 words of SpongeDocs English to Indonesian Part 5

Source

About SpongeDocs

What Is Sponge?
The purpose of the Sponge project is to create a plugin development framework for Minecraft. Sponge is being created by a global community, and its open-source nature means anyone can participate.

Sponge was created after seeing the failures of other projects in the Minecraft plugin development community. We are trying to avoid making the same mistakes as other projects; thus:

Sponge is an extremely open project.
Sponge is licensed under the MIT license - an extremely permissive open source license.
Performance is of high priority.
Most plugins developed with the Sponge API should work across several different versions of Minecraft without needing to be updated. This means that, for the most part, server owners do not need to worry about plugin incompatibilities.
We have two other projects in addition to the Sponge API:

SpongeForge, a coremod for Minecraft Forge, which is an existing Minecraft modding framework famous for spurring the Minecraft modding scene. Forge lacks a cross-version API, and this is where Sponge steps in. Sponge allows server owners to deploy Sponge plugins with ease, making server management easier.
SpongeVanilla, a stand-alone implementation of the Sponge API, running on top of the vanilla Minecraft server. (SpongeVanilla was formerly known as Granite, until the development teams merged).
Players on servers running SpongeForge or SpongeVanilla do not need to install any client-side mods. They are able to join servers running Sponge using the vanilla Minecraft client provided by Mojang.

The Sponge API is not tied to any platform. This means that server owners can run Sponge plugins on any official implementation of the Sponge API. Sponge plugins should function identically on either implementation, due to the common functionality of mixins.

Source

Source Language

English

Number of Words

I translate a total of 1130 words.

Translated Language

I contribute to Indonesian Language and translated the file 'customwgen.pot' and 'modifiers.pot'. The project is huge, it still needs 92190 words to translate.

Before Translating

• customwgen.pot from 67%
  
• modifiers.pot from 39%
  
  
  

After Translation

• customwgen.pot to 100%
  
  customwgen.pot : https://crowdin.com/translate/sponge-docs/920/en-id
• modifiers.pot to 100%
  
  modifiers.pot : https://crowdin.com/translate/sponge-docs/922/en-id

Proofread Words

Currenly waiting for my translation to be proofread.

Links

You may check my activity in SpongeDocs
My Profile Activity as a translator
Project profile link
GitHub project link

Part1, Part2, Part3, Part4

Examples

The :javadoc:Cactus#setHeight(int), and many other similar methods on other populators, also takes a :javadoc:VariableAmount which can be used to specify the height as a range or other custom value.

:javadoc:Cactus#setHeight(int), dan banyak methods lain yang mirip di populators lain, juga memerlukan sebuah :javadoc:VariableAmount yang dapat digunakan untuk menentukan tinggi jangkauannya atau nilai perubahan yang lain.

Start by getting the :javadoc:BiomeGenerationSettings for the desert biome. This object is a container for all generation settings relating to that biome. Next, iterate through the list of all :javadoc:Cactus populators and set the height to 5, which means it can only generate cactii which are 5 blocks tall.

Dimulai dengan memperoleh :javadoc:BiomeGenerationSettings untuk desert biome. Obyek ini adalah sebuah penampung untuk semua pengaturan turunan terkait dengan biome tersebut. Selanjutnya, terus ulangi semua daftar :javadoc:Cactus poplulators dan ubah tingginya menjadi 5, yang berarti hal itu hanya dapat menghasilkan cactii sepanjang 5 blok.

All plugins wishing to make changes to a worlds generator must register a :javadoc:WorldGeneratorModifier. These modifiers are registered globally with a unique id, which must be added to the config of a world by a server admin. With the id specified in the world config, a WorldGeneratorModifier will be automatically called when the generator for that world is set up, allowing it to make changes to the generator.

Semua plugin diharapkan untuk membuat perubahan kedalam pembuat dunia yang harus mendaftarkan sebuah :javadoc:WorldGeneratorModifier. Perubahan ini didaftarkan secara menyeluruh dengan id yang unik, dimana akan ditambahkan kedalam config dari dunia itu oleh admin server. Dengan id yang ditetapkan kedalam config dunia, sebuah WorldGeneratorModifier akan secara otomatis dipanggil ketika pembuat dari dunia tersebut didirikan, mengizinkannya untuk membuat perubahan pada pembuat.

As you can see, WorldGeneratorModifier has three methods which we override. :javadoc:CatalogType#getId() must be overridden to return a constant and unique identifier for your WorldGeneratorModifier, this is the identifier which will be used in the world configuration to specify which worlds your modifier should be applied to. :javadoc:CatalogType#getName() must be overriden with a constant and simple human-readable name for your modifier.

Seperti yang bisa anda lihat, WorldGeneratorModifier memiliki tiga methods yang kita sampingkan. :javadoc:CatalogType#getId() harus dikesampingkan untuk mengembalikan pengidentifikasi yang konstan dan unik untuk WorldGeneratorModifier anda, inilah pengidentifikasi yang akan digunakan didalam pengaturan dunia untuk menentukan ke dunia mana perubahan anda harus diterapkan. :javadoc:CatalogType#getName() harus dikesampingkan dengan nama yang konstan dan mudah dibaca manusia untuk perubahan anda.

---

Posted on Utopian.io - Rewarding Open Source Contributors

---