I don't know of any instance-scope

[leaden geyser]

im rolling my own "premium" module licence here out of nessecity. i

is there another approach? seems like foundry have closed that by de-listing. and there no api? is one planned?

(please stop explaining that js is on the client) :p

i know someone could just monkeypatch my checklicense to return tru

[soft pawn]

My point is that you'll realistically need to handle authentication at the point of download (as Foundry does) if you want to actually control things. There isn't any sort of tooling for in-world authentication and Foundry doesn't care about per-install stuff internally either (so it doesn't try to expose anything to show that).

If you need an instance-scope unique identifier, creating one yourself via a file with a UUID is going to be your most reliable option that I know of.

[leaden geyser]

thanks for the suggestion. as you say, this isnt really the best place for auth. but a matter of nessecity.

independent distributors must use public distribution i think? open repo.

[cursive pawn]

@leaden geyser I have built a way to provide a closed auth, does not use foundry listing. You can DM me if you want. The auth is done on point of download as mxzf mentioned.

[leaden geyser]

Thanks! I may come back to you. My goal with the client side drm is just to make it non trivial. I think I’m getting there.

[gritty zodiac]

Only per install thing Foundry has is the Foundry license key and you definitely won't get access to that.

[leaden geyser]

Nobody asking for the license key obviously but creating a uuid with a private key based on a license would not be difficult.

Doesn’t seem like that outlandish a request to enable developers to secure their modules, if they are closing the premium service option

I’ll link the license to worldIDs and allow users to manage installs I guess. I would have preferred by installation (machine) eg ClientID.

[gritty zodiac]

If no-one makes that request, nothing's going to happen. Tho I doubt they will even with that as they already have premium module handling.

[leaden geyser]

Yea I was in the process of signing an agreement before the AI policy changes

So exploring new avenues. I would rather not do auth at download time. But I think I’ve a moderate compromise. Problem is I need to decide how many worlds the user can use instead of just saying as many as you want in your foundry installs