But I literally write like that. I don’t want for something that has a lot of technicalities to be just a wall of monotone text. That’s what academic papers are for ![]()
I use those styling patterns as well as those ‘zingers’, as, well, stylistic devices, because that’s literally what they are.
It was supposed to be a paraphrazed Star Wars joke. Oh well.
Sorry if I’m coming off harsh.
No no, I’m very glad that you and @averyhiebert brought this up, because it haven’t even occurred to me that this style of writing would cause such a reaction. I guess I need to tweak some things a little to get the AI vibe out of this tutorial, so thanks for the feedback.
Part of the reason for my distaste is that the forum has recently seen a big increase in posts from people who are only here to self-promote their custom AI-written games or systems but don’t participate in the larger community or interact with other people’s creations at all, and it rankles me.
Yeah, I’ve seen the post. It’s a damn shame. But, back to the topic at hand:
And I do like the idea of Sass and npm integration with Twine. I wonder what led you to change your mind and use npm when your original post specified that you don’t want to use npm. Was there a particular reason you resorted to npm after all?
I thought that plastering npm on top of a Twine project would create some hassle in the Twee building process - but no, the process is basically the same as with e.g. a React app. I have no qualms with npm itself as I use it on multiple other projects (I personally prefer yarn to be honest), so I just went with that.
By the way,
Frankly, I’d vastly prefer reading a LaTeX pdf if it didn’t use emojis, italics and jokey zinger lines.
Extending the post editor to include a way to embed a PDF viewer for uploaded files would be sick ![]()