• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

(Drop Dead Studios) Spheres of Power: Official Support Thread

Any reason the SoP files aren't available through LWD? I mean, I'm fully capable of downloading and installing 'em, it's just considerably less convenient.
 
Any reason the SoP files aren't available through LWD? I mean, I'm fully capable of downloading and installing 'em, it's just considerably less convenient.

We did have some discussion with LWD about distributing SoP through their channels, but in the end they decided not to go that route with us. I do not know what prompted that decision, but I'm sure they had their reasons. And they were kind enough to let me use their forums for a support channel.
 
I've just posted version 1.6, which fixes various bugs that I've been finding through bug reports and work on SoPEx.

As usual, be careful of updating right before you run a game.
 
Bug encountered right after updating. My SoP setup just has the Community files as other add-ons, no. other .user files.

BTW, would it be possible for the update files we download to have version numbers, so that they don't overwrite the previous versions when a new download is available? That would help rolling back in case of a major bug. Thanks!
 

Attachments

  • Screen Shot 2016-06-26 at 11.18.26.png
    Screen Shot 2016-06-26 at 11.18.26.png
    211.7 KB · Views: 10
Bug encountered right after updating. My SoP setup just has the Community files as other add-ons, no. other .user files.

BTW, would it be possible for the update files we download to have version numbers, so that they don't overwrite the previous versions when a new download is available? That would help rolling back in case of a major bug. Thanks!

Looks like as if there is a dependency to the Expanded Options test file from the main file somewhere. Either that dependency needs to be cut or reversed by moving the appropriate content from the EO to the main file.
 
That is indeed what happened. I have posted a fixed version of 1.6, so if you download that and re-compile then it should work.
 
Is NICsopSpSt from this file? I see that it doesn't exist, didn't load the data files.

More info.. I remove Spheres from my addons and it compiles, so something is calling this function in the 1.6 file

It is in the components file, line 1246.. hmmm And removing it didn't quite help, now I have a SoPSphPtf references non existant panel option /sigh... help! We game on Saturday.. at least that laptop still has 1.5.. I won't upgrade it yet, for sure.
 
Last edited:
I just posted 1.7 to fix this issue. There were a couple of files I had accidentally added to a previous release, and mistakenly thought I could remove from 1.6 without a problem. Oh, well.

In related news, Expanded Options is feature-complete and now in testing. No hard date yet for release but it should be soon.
 
Thank you very very much, i am also looking forward to the expanded options, so far i love the spheres of power, only game so far i like more has been shadowrun but it is fading fast, Thank you
 
Thanks again. As usual, it is a pleasure communicating with you! Hey, I see the sphere staff is still in here. Did you have any luck getting that coded to work yet? If so, how would I implement it? I'll see if you posted earlier in this thread on that, but I "built" the staff I have using adjustments (+ to sphere casting level and the like).
 
Last edited:
Sphere Staves are in a half-done state, and that half got put on hold while I worked on Expanded Options. All that NICsopSpSt business is an artifact of that work. It shouldn't have gotten out into the wild, but I was careless.

I haven't looked at that code in a few weeks, but when I left off of it, staves were kinda-sorta working, in that they correctly applied their enhancement bonus to your caster level with the relevant sphere(s), and you could add talents and additional spheres to a staff. But I was hung up on getting staff-based talents to show up on the hero (so that, for example, the talents on a Life staff would add dice to the hero's Cure ability). And I haven't even started on getting it to calculate the price of the staff.

That reminds me: it's time for an utterly informal, wildly unscientific poll!

Expanded Options is close to going out the door, and DDS has given me permission to proceed how I see fit in terms of order of future content. So after Expanded is out, I can either pick a Sphere Handbook to implement, OR I can circle back and take another run at some of the harder content like Sphere Staves that require in-depth UI work.

So which would you prefer? And if it's a Handbook you want, which one?
 
Last edited:
i kinda like the handbooks, they add a lot more to depth of some of the charecters and add new ones, and also they may give you other ideas not only for new books, but on how to implement the staff's, but thats jst my thinking
 
That reminds me: it's time for an utterly informal, wildly unscientific poll!

Expanded Options is close to going out the door, and DDS has given me permission to proceed how I see fit in terms of order of future content. So after Expanded is out, I can either pick a Sphere Handbook to implement, OR I can circle back and take another run at some of the harder content like Sphere Staves that require in-depth UI work.

So which would you prefer? And if it's a Handbook you want, which one?

How close are you from finishing that staves part? If it less work than a handbook, I would prefer that. Also, going through all handbooks before you finish a core part of the magic system doesn't feel right. In the worst case, I can add new magic talents myself. (Which reminds me: Can you please add a magic talent "other" like "Profession (other)"? I want to do be able to add a magic talent on the fly to a character and later replace it properly, once I have time.)
 
While I'm eagerly awaiting the handbooks, having the base book as a solid foundation, makes more sense to me.

Sphere Staves would have my vote, prior to handbooks.

Incidentally, are each of the handbooks their own purchase... or can they be taken as a package/subscription, even if that package is gradually added to over time?
 
Incidentally, are each of the handbooks their own purchase... or can they be taken as a package/subscription, even if that package is gradually added to over time?

I plan to work under the assumption that each is a separate purchase, at least in terms of technical dependencies. Obviously each sphere handbook should depend on you having vanilla SoP, and whatever Paizo content they build off of, but none of the handbooks should depend on each other.

As for how they'll be sold, that is a question above my pay grade. Packaging handbooks together is certainly possible, and I've advised DDS of that. But I can't say for sure right now how it's going to work.
 
I plan to work under the assumption that each is a separate purchase, at least in terms of technical dependencies. Obviously each sphere handbook should depend on you having vanilla SoP, and whatever Paizo content they build off of, but none of the handbooks should depend on each other.

As for how they'll be sold, that is a question above my pay grade. Packaging handbooks together is certainly possible, and I've advised DDS of that. But I can't say for sure right now how it's going to work.

That is a bit of a of problem as some handbooks do use stuff from other handbooks. Especially if they reference PoW stuff that might not have a HL representation yet.
 
Well, PoW doesn't worry me, because PoW is in the Pathfinder Pack, which is free and well-supported by the community so I can safely make it a dependency. And I know PoW well enough to add anything that SoP needs to it.

If there are inter-handbook dependencies then that might require some finessing, but I have some ideas about how to approach that.

In the meantime, behold!
kV4yGNm.png
 
Last edited:
Back
Top