In my last post, I wrote about how much longer the full spell suite was taking than I had expected. I've decided to change what needs to be in Sylvia GM's Public Alpha.
The plan is to launch with SRD Lite, then continue the full spell suite after release.
What I mean by SRD Lite
SRD Lite builds on the SRD 5.2.1 core we already have. For launch, I'm targeting a 96-spell roster chosen to support the current launch classes and subclasses, their normal spell choices and level-up progression, and higher-level spellcasting. We're reusing our existing SRD implementations where they fit, with any adaptations made for Sylvia's rules engine. Finger of Death isn't in the launch roster.
That gives the launch a more manageable scope. There is still plenty to implement and test, but I can work towards a defined set of spells instead of holding the entire release for the full suite.
The important part is making those adaptations clear. If a spell has a narrower effect in SRD Lite, that needs to be part of its rules. The player and the GM should be working from the same description of what it can do.
A spell appearing in the catalogue is only the starting point. Its targeting, saving throws, duration and ongoing effects still need to work together in the engine. I want to be able to check those behaviours in an actual campaign, including what happens when the spell interacts with something else.
The full spell work carries on
The work already done on the full suite stays in the project. The 16 spells cut from launch, along with all other non-launch work, are being kept for later batches. The implementations, tests and work on the harder interactions will still be useful as I expand support after launch.
Some of that can help SRD Lite directly. The rest remains part of the work towards the fuller ruleset. The immediate priority is getting the launch set into a state I can properly test and release.
Where that leaves Public Alpha
I still don't have a new release date to give. A smaller spell scope should help, but there is implementation, campaign testing and final release checking left to do.
The goal is the same: I want people to be able to sit down and run a campaign with Sylvia. Getting that first release into people's hands, then continuing to build out the full spell suite, makes more sense to me than keeping everything behind the larger job.