#TERASOLOGY ONLINE CODE#
Rarely blocks of code in the engine may be hit in a way requiring use of AccessController.doPrivileged(.) - usually this is nothing module authors have to worry about but once in a while it could explain something quirky.
External classes or packages in the basic whitelist at .ExternalApiWhitelist are available to all modules.Internal classes or packages marked with the annotation are available to all modules.Terasology’s engine uses a whitelisting approach to expose API for modules using two primary methods and a rarely needed third one: This is also possible later on.Īfter you have a module repository on GitHub and still from modules/MySample, execute git remote add origin, where repository_url is either your personal repository url or the official repository url.
You can ask the project staff to please create a module repository for you under the Terasology organization and give you access.You can create your own module repository on your personal GitHub account.Running gradlew idea from the root directory will create the required project files.īy default, the module will be initialized with an empty git repository.Ĭonnecting the new module to GitHub can be done in one of two ways, either of which needs you to create a new remote reference in the local git repository. Similar to fetching a module, be sure to adjust your workspace after your module lineup has changed.
This will create a module named MySample at modules/MySample. New modules can be created with a similar command:
0 kommentar(er)
