This document is to specify the implementation of consensus On Endowment of Title.
Publish a world and win an award
The world that has the most monthly playtime will win the award “World of the Month”. Its owner will gain the title “the Famed”.
The world that has the most seasonly playtime will win the award “World of the Season”. Its owner will gain the title “the Prestigious”.
The world that has the most yearly playtime will win the award “World of the Year”. Its owner will gain the title “the Great”.
Worlds will be evaluated every month/season/year. This is an automatic process and you don’t need to do anything.
Publish an AI and win an award
The AI part of World_Gate is still in a rudimentary state. As a general guideline, AI should be evaluated by its quality, not playtime. Ideally, there should be AI competitions from time to time. AI that wins the competition will get an award. That’s just future plan.
Right now there’s no way for you to gain a title by this means.
Contribute multimedia resources to the community
Anyone who can contribute multimedia resources to the community will gain the title “the Fair”.
If you have created some multimedia resources and are willing to share your work with the community under friendly license, preferably public domain or creative commons, feel free to write to world_creator@dins.site. Present some samples and we can discuss the details.
For example, a set of UIs, a set of sound effects, a set of particle effects or a set of textures that belong to a particular category.
Find a major bug in the softwares of World_Gate platform
Anyone who can identify a major bug in the softwares will gain the title “the Hunter”.
A major bug is defined as a bug that causes the expected functionality of the software to fail under normal usage.
So if you find a typo, you can still write to me. But that doesn’t count since it doesn’t break the functionality. If you delete some files in World_Creator and start it, you’ll likely see some errors. But that doesn’t count since you are not using it normally.
You need to report your finding as a test case. Here is a valid format.
Test Case Name: Marker.RotateBy method
Testing Procedure:
———-Create a marker in template and set it up in DataStructure.
———-Call RotateBy(90, 1000).
———-Call RotateBy(90, 1000) again after the first RotateBy ends.
Expected Result:
———-After the first call marker should rotate from 0 to 90 degrees.
———-After the second call marker should rotate from 90 to 180 degrees.
Actual Result:
———-First rotate OK.
———-Second rotate is still from 0 to 90 degrees.
In the test case you must tell me what is wrong, how to reproduce the bug and the expected behavior. Using the above format will force you to write all these points.
For bugs in World_Gate, please email to world_gate@dins.site.
For bugs in World_Creator, please email to world_creator@dins.site.
For bugs in World_Mind, please email to world_mind@dins.site.
If you are reporting a bug on the script side, it’s always a good idea to make a toy world that produces the bug, zip it and send to me with the email. This will help me quickly verify the bug.
Spread the word and teach others how to build a world
Anyone who can teach others how to build a world or AI will gain the title “the Lodestar”.
If you write a series on how to use World_Creator, or do a video walkthrough on the procedure, or write a few articles analyzing a framework and how to extend it, these will all do.
For the world teaching, please email your work to world_creator@dins.site.
For the AI teaching, please email your work to world_mind@dins.site.
Build a decent world framework
Anyone who can build a decent world framework will gain the title “the Pillar”, which is an honored title in the community.
A decent world framework is hard to build. If you want to go for it, I appreciate your ambition. Here’re some procedures to go after.
Before you begin, you should write to me and explain a few things.
(1) General description about the framework you want to build.
(2) The business logic, such as game rules, abstractions and modeling.
(3) The code design, such as what classes you will write, main mechanism and how to extend.
We’ll discuss if the design is sound, or if we can make improvement. I’ll also check if somebody is already working on similar ideas. We do this so that we can make sure the framework is of high quality.
After that you are ready to go. During implementation, feel free to write to me if you face difficulties.
When you think you have finished, write to me and we can arrange some tests.
When all tests have passed, you get the framework published and become a legend.
All emails related to framework should be written to world_creator@dins.site.
Support the community by funds
You can support World_Gate by a monthly membership. Available payment channels are listed below:
Please follow the instructions there.
Misc
The above description only covers the general types of contribution. If you think you can do something else for the community, please write to dins@dins.site. I’d love to hear creative ideas.
The Gatekeeper has the privilege to grant custom title. If your idea sounds good, we can discuss more about it, which may possibly gain you a cool title.