Home

Welcome to the AlbianWarpClient wiki!

This page contains Information on how to install/update/troubleshoot AlbianWarp.

Remember that this is extremely new and extremely buggy! Download and run this stuff at your own risk. Backup important files and things. We're all learning how to make this work together and there are bound to be some casualties along the way.

Currently, the Albian Warp Client is a 64-bit Windows application. If you are running Creatures Exodus/Docking Station on a 32-bit version of Windows (or anything other than Windows), you will not be able to run the client. This issue will be addressed in the future.

To Get Started

1. Join the #albianwarp channel on the CAOS Coding Cave discord.. You are probably going to run into a bunch of problems/bugs along the way and we will be able to help you out there. You'll also want to receive updates as newer versions are being released all the time.
2. Download the latest client from the Releases page. As of writing, this is the one named "AlbianWarpPythonClient_alpha_v0.0.2-alpha.baboon.zip"
   • You may need to alter the file "albianwarp.cfg" to point to your My Creatures directory if you find you are unable to send and receive creatures. To do this, open the file in notepad, remove the '#' in front of the 'my_creatures_directory' line, and change the path to point to your proper folder.
3. Download the required bootstrap modifications from here. Follow the instructions on this page to install.
4. Make an account here. You don't need to provide a valid email address.
5. After installing the bootstrap modifications, you will need to create a new world for the updates to take effect. Each time the scripts are updated, you will need to make a new world, so try not to get too attached if you can help it 😛
6. Once you have launched into your new world, start the client. For best results, start it via the command line or powershell (you can do this by shift+right clicking on the folder the the client exe is in and selecting the option that says "open command window/powershell here", then hitting Tab until the client exe filename is displayed, then hitting Enter). If you don't start it via the command line, the client will simply exit and close if it encounters an error and you won't be able to tell what happened or how to fix it.
   • If you get an error when starting the client, Windows might be blocking the file as it considers it suspicious. Follow the instructions here to unblock both the exe and CAOS.dll.
   • Your virus scan might treat the Albian Warp Client as suspicious or harmful. This seems to be an unfortunate side effect of many applications compiled with pyInstaller, as this issue details. There is not a fix for this currently, but it is one of many issues being investigated and hopefully corrected before a public release.
7. Log in to the Client with your username and password. If all goes well, you should be in!
8. To gather useful information, make sure you keep autokill off and post any errors you encounter to the #albianwarp channel along with exactly what was going on when the error occurred. Keep an eye on the Client window for errors as well.
9. Have fun feeling like it's 2001 all over again! Well, a bunch of bugs and crashes not withstanding.
10. Keep an eye on the Project Board and see what we're working on next! Feel free to suggest future features and modifications!

Known Issues

• Chat is not yet implemented (see Issue)
• Creatures warping "twice" crash the portal scripts (see Issue)
• Creatures sit in the My Creatures folder for a while before warping in sometimes (see Issue)
• Deletion of sent creature files does not always work. You might need to regularly clear out your My Creatures folder if seeing those errors stack up bothers you.
• Creatures sometimes try to warp in more than once (probably the same problem as the above)