Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Just to check, if I were to encode a font as Base64 in a CSS stylesheet, would that be a reasonable step to prevent/discourage end users from accessing and using it? I could also add a comment to that stylesheet requesting that they don’t do that, but my feeling is that most users would never see it in the first place and so the font isn’t exactly being served up on a platter to begin with.

(+1)

We're happy with a straight up font declaration to be honest, with just a CSS comment saying the font needs to be licensed by Chequered Ink or something. We added this clarifying language so that hopefully you don't have to go to any inconvenient measures to obscure the font!

Thanks! I actually haven’t yet used these in anything that would make it that straightforward to get hold of them through a web browser, but I’ll add that comment if I ever do. (Base64 would be my go-to way of including the font anyway: I like to be able to keep Twine games to just one file.)