PelagoHaven

A devlog? So I am still in the middle of coding the Option Creator but it is making good progress. I have already finished the complex script to searilize the option data and cache it in sqlite and am now at creating the ui for it. The Ui is also making some progress, I already have rendering of the most basic option types implemented and am now trying to make the rest of the UI functional (you cant edit the options currently). Currently we have implemented:

• Toggle (and DefaultOnToggle)
• Text Input (FreeText)
• Select (Choice)
• Range
• Range with Options (NamedRange)

So 6/20 different option types…

Bye!

What happened? You ask? I finished the new Library tab! So what actually differentiates this one from the old one?

• Instead of a two column design, we now use cards for each world and can therefore show vastly more worlds in less space, also the cards are the right size to later support grid art!
• The backend works completely different: the old one read manifest files to get its data, this one asks the runtime directly!
• Caching in a DB, so loads are really fast!

This also provides the basis for the following new Option Creator, which I will work on next!
Bye!

Its been a long time, but i made a decission that I think is correct, but is sort of a scarry one, I decided to start over from scratch again. Reason for this move is that the old architecture built around PyInstaller wasnt really a way i could continue foward, as it had too much Problems and while I probably could have switched that out, I decided to just start over. So what happend in the new Version? I added well almost the complete bootstrap flow, so the App now downloads a python runtime and the archipelago source code and installs all dependencies automatically! I will now continue working on reimplementing the basic layout and the option editor
Bye!

Here we are again, it’s been a bit of time, so what has happened?

The option editor was updated to actually work (wuhhhhhh), we now handle rendering the options and allow editing of these options, supported option types are:

• Toggle
• Range
• Named Range
• Choice (Select).
• Text Choice (Combobox)
• List
• Text

The editor also now allows selecting the apworld you want to edit and adding new ones (this was hardcoded before).

Up next is a bit of styling work on the option editor, the room setup screen, and maybe getting started with generation of the YAML files.
I too need to again take a look at the option extraction, as I ran into multiple errors with extracting options, ranging from missing deps to other errors.

Bye!

So, it’s time for another devlog. So, what has happened?

As I talked about in the last devlog, I got the program added to the .apworld file format in the Windows Explorer, so that one can install apworlds just by double pressing.

I also made a lot of progress on handling the options creator, originally I wanted to use PyO3 for integrating with the official Archipelago runtime, which I realised isn’t that great of an idea as shipping a Python interpreter with it is kind of a pain. So I ended up using PyInstaller to create an executable of the runtime + my wrapper and bundling that executable with the application.

This executable now allows me to read the options from an apworld, which I am using to recreate the options creator in a more intuitive way by bundling the seed generation and room creation all in one flow, so a user can in one flow create all configurations, configure their room, generate their seed and upload it to a webhost of their choosing.

From that flow, I already have some basics of the slot configuration set up, as well as, of course, the option reader.

Next up I will try to complete the slot configuration and try myself at the seed generation, as well as the room configuration UI.

Bye!

So, well… This took a bit longer than expected, but here we are again.

Over the last days, I managed to make some big progress on the launcher, to the point that it now has a World Manager. (For context, a world is basically a game, or, to be more specific, the piece of software that tells Archipelago how a game works and how it should generate the items.)

Writing this World Manager was way more difficult than originally thought, since I personally am neither an expert on Archipelago nor an expert on Tauri. It also didn’t help that the manifest file “archipelago.json” isn’t really a standard, as every world has different values and keys available, even the builtin worlds don’t have a consistent schema here.

So, what actually is new?

• Some basic settings for selecting the path of your Archipelago Folder
• The Library tab to view installed Worlds
• An APWorld Installation flow
• The ability to remove Worlds

Next I will have to look what I do, in terms of the world management I would really like to add the program to the Windows file picker, so opening the APWorld files would open this launcher instead of the official one. I also now need to more focus on the core part of the project, the Generation side, there I currently don’t have a plan how to do that yet, as I need to read a lot of Python for that, I will probably end up using PyO3, but I will have to look.

Bye!

Hi there, I have been working on making a basic Layout and getting those pesky traffic light buttons to look good, this is what i ended up on. Yeah also setup my Tauri dev enviroment but thats the boring stuff