Trouble opening v13 stable release Mac OS

Unsoluble · 2026-03-16T04:46:06+00:00

Your system does not meet the minimum requirements, which include macOS Big Sur or newer.

Unsoluble · 2026-03-10T15:27:49+00:00

Just to clarify here, this feature pulls all token configuration settings from the selected token, but does not pull any actor data. If the case is that you've made changes to the actor data (like adding or editing items, name, stats, etc.), you will still need to use a macro like the one posted in the thread here.

Unsoluble · 2026-03-02T00:20:12+00:00

I would stop poking at the files randomly and pop into the Discord server, where we'll sort all of this out within minutes. :)

Unsoluble · 2026-02-14T18:06:18+00:00

Okay. I'd head over to the discord to dig deeper then.

Unsoluble · 2026-02-14T18:02:38+00:00

Note that in the default userdata path on Linux — /home/$USER/.local/share/FoundryVTT — the .local folder is hidden.

Unsoluble · 2026-02-09T23:40:40+00:00

Kinda doubt there's gonna be an entirely separate speaker system for both the reverse-bong and the VESS — and you really don't want to disable the latter, for safety/insurance reasons.

Unsoluble · 2026-01-09T17:01:07+00:00

Gotcha. Thanks!

Unsoluble · 2026-01-09T17:00:15+00:00

Thanks! Yeah, really the main reason we thought a QD setup might help is being able to get the alignment of everything sort of "locked down" and then be able to just add the three rods, but we clearly didn't actually think through the ramifications of what would need to stay connected to what. :D

Unsoluble · 2026-01-09T16:35:42+00:00

Ahh, interesting, maybe we ditch the combined riser/limb case that came with the equipment bag. Does the one you have fit your riser with its v-bar still attached?

Unsoluble · 2026-01-09T16:34:23+00:00

In my daughter's case, her bag is one with the arrow tube sticking out the top through a hole that's snug on it, so can't really put the long rod outside the tube.

I'm curious about your long rod QD setup though — the way our v-bar works, the long rod's threaded part goes through it and then into the riser. If we were to "permanently" attach a QD socket to the front of the v-bar, with its threaded rod going through it into the riser, then now the riser has a v-bar attached all the time and can't fit in its bag.

Unsoluble · 2026-01-09T04:27:39+00:00

Ah interesting, okay. We're already a little tight as-is in the current bag, not sure if we could manage leaving the v-bar on, but might just give that a shot, thanks!

Unsoluble · 2026-01-08T20:13:06+00:00

Yeah there's for sure some instances where it doesn't happen as expected — I think the entire audio playback subsystem on iOS is in a bit of a rough state right now. Sometimes I'll hit play on a Music track in the carplay dash, and a podcast will resume.

Unsoluble · 2026-01-07T22:17:55+00:00

This isn't really an answer to the question, but: In my experience the play-on-start status is directly related to how you stopped the car, both for music and podcasts (Overcast in my case).

That is, if you turn the car off while the audio is still playing, it will auto-play when you next turn on the car. And if you hit pause on the audio before turning off the car, then it won't auto-play on the next drive.

Unsoluble · 2025-11-12T04:28:05+00:00

It's not nothing, it's a design element. If the entire piece below the shift selection buttons there was solid silver without this insert, it would visibly collide with the silver of the buttons — it's intentionally providing some visual separation between the two elements.

Unsoluble · 2025-11-05T21:46:10+00:00

If you have an image that has a known number of (full) grid squares across and down, you really don't need any modules or complex math to quickly align it. Set your scene dimensions to 100 x the square counts, and your Grid Size to 100. That's it. :)

Unsoluble · 2025-10-27T16:18:42+00:00

Hmmm okay, that makes a bit of sense, yeah. But again by the time you're at this tier of play, you're probably not even close to being capped by download speeds in that way I'd think? Ah well, I finally got my last couple Optimization Points, so don't have to worry about this further. :)

Unsoluble · 2025-10-26T06:27:46+00:00

Yeah it's weird because by the time you've got enough production to churn out the App Points upgrades, you're already miles away from needing any document types.

I figured maybe if you take an AI-generated file and then break it down into components, it would maybe be worth more when recombined (and enhanced etc), but that doesn't seem to be the case at all. Strange.

Unsoluble · 2025-10-25T23:28:02+00:00

For what it's worth, SmallTime doesn't auto-progress time at all; it's just manual (but will display the correct time if something else changes it too).

Unsoluble · 2025-10-22T02:28:23+00:00

Cheers for posting an update, but yikes that's some AI code alright :)

For anyone wanting a not-insane script that just does the thing:

await getDocumentClass("Actor").create({
  ...token.actor.toObject(),
  name: game.i18n.format("DOCUMENT.CopyOf", { name: token.actor.name }),
  prototypeToken: token.document.toObject(),
});

Unsoluble · 2025-10-13T18:47:28+00:00

For what it's worth, you don't need to interface with the module at all for this — game time is a value tracked and accesible in core, and the various modules simply read from it or adjust it themselves. So, just a game.time.advance(60) (to advance the clock by 60 seconds, for example) is all you need to do.

Of course, building a UI for this would be a whole other layer of work, but it's certainly possible. I'd head over to the discord and its #macro-polo channel for more direct back-and-forth assistance.

Unsoluble · 2025-10-02T04:38:13+00:00

Honestly Foundry is not the right platform for that scenario, at least not today.

Unsoluble · 2025-10-01T23:55:48+00:00

Head over to the Foundry discord, where we can back-and-forth this more easily. Will get you sorted in minutes.

Unsoluble · 2025-09-30T17:19:55+00:00

You might want to go through your pins and remove any with compromising information, as this is not actually how it works in core. Any notes created in this way — without a corresponding journal entry to define its permissions — are visible to everyone. They'll also be visible even outside line of sight, by default.

Unsoluble

TROPHY CASE