forked from mirror/Archipelago
Jonathan Tinney
7971961166
Some checks failed
Analyze modified files / flake8 (push) Failing after 2m28s
Build / build-win (push) Has been cancelled
Build / build-ubuntu2204 (push) Has been cancelled
ctest / Test C++ ubuntu-latest (push) Has been cancelled
ctest / Test C++ windows-latest (push) Has been cancelled
Analyze modified files / mypy (push) Has been cancelled
Build and Publish Docker Images / Push Docker image to Docker Hub (push) Successful in 5m4s
Native Code Static Analysis / scan-build (push) Failing after 5m2s
type check / pyright (push) Successful in 1m7s
unittests / Test Python 3.11.2 ubuntu-latest (push) Failing after 16m23s
unittests / Test Python 3.12 ubuntu-latest (push) Failing after 28m19s
unittests / Test Python 3.13 ubuntu-latest (push) Failing after 14m49s
unittests / Test hosting with 3.13 on ubuntu-latest (push) Successful in 5m0s
unittests / Test Python 3.13 macos-latest (push) Has been cancelled
unittests / Test Python 3.11 windows-latest (push) Has been cancelled
unittests / Test Python 3.13 windows-latest (push) Has been cancelled
12 lines
821 B
Python
12 lines
821 B
Python
# The first thing you should make for your world is an archipelago.json manifest file.
|
|
# You can reference APQuest's, but you should change the "game" field (obviously),
|
|
# and you should also change the "minimum_ap_version" - probably to the current value of Utils.__version__.
|
|
|
|
# Apart from the regular apworld code that allows generating multiworld seeds with your game,
|
|
# your apworld might have other "components" that should be launchable from the Archipelago Launcher.
|
|
# You can ignore this for now. If you are specifically interested in components, you can read components.py.
|
|
|
|
# The main thing we do in our __init__.py is importing our world class from our world.py to initialize it.
|
|
# Obviously, this world class needs to exist first. For this, read world.py.
|
|
from .world import Schedule1World as Schedule1World
|