Yeah, you'll need them at some point. If you want Prim arrested just don't present your findings to SamarraShould I still investigate the 3 clues in the library, even though I want to unlock the Primrose dungeon route?
Do you know if the dungeon is available in this update?Yeah, you'll need them at some point. If you want Prim arrested just don't present your findings to Samarra
If you're on .10 then yeah, it is. You can meet and speak with Prim down there if she gets taken in. Have to get there by talking to Samarra, and it opens up another remove inhibition option on Samarra.Do you know if the dungeon is available in this update?
Thanks for the replyAt some point, sure. I have barely enough time to push out monthly releases as it is, so don't expect it anything right now. That's something that it's more likely that I'll add after the game is complete.
Probably not. We're getting close to some more ability building, but I'm focusing on smaller, more fun things this time around.anything new (stat/abilities wise) coming in 0.11
Should all of that be in a spoiler tag?Here's a weird thought or fucked up twist...
None of those options. 10 is a larger value than 6. You're making the mistake of assuming that just because there's a dot in there, it's a decimal number. It's not. If it helps, read the entire version number: 0.10.0. Now it doesn't look like a decimal number any more. These are merely 3 different values separated by dots.@Belle Just realised something. Old releases went as far as 0.6 before going down to 0.10. Was I blind and missed a zero or did you realise you were further away from finishing the game than you first thought?
Well that's put me in my place lol. I was think the numbering system now would put it like around pre-alpha stage when with the content you've put in, it's gone way beyond that and other games with similar numbering formats.None of those options. 10 is a larger value than 6. You're making the mistake of assuming that just because there's a dot in there, it's a decimal number. It's not. If it helps, read the entire version number: 0.10.0. Now it doesn't look like a decimal number any more. These are merely 3 different values separated by dots.
I can easily see why you're confused about it though. I went back and forth with it in my head for several months before I decided to just plow ahead regardless. It's not a mistake, but in hindsight, I should have used a different way of showing version numbers that wouldn't confuse non-programmers in particular.
Edit: Just to be perfectly clear, once and for all: The version numbers for LLtP have never indicated, and will never indicate, distance to the final release. They only indicate how far we are from the first release. Separate your mind from decimals and percentages.
I don't subscribe to the way AAA publishers have turned terms like "alpha" and "beta" into marketing slogans this past decade, making something sound more exclusive than if they simply called it a "demo." I use the classic definition of these terms: A game has reached Alpha when it's feature complete (from then on out it's all about perfecting those features and fixing bugs). It has reached Beta when it's ready for external testing. Those definitions don't fit with the iterative development schedule I use for LLtP, since each "iteration" (ie. update) is fully developed and tested in its own right. We're going to go directly from "pre-alpha" to "final" the day I pull the trigger and call one of my releases 1.0.0.I was think the numbering system now would put it like around pre-alpha stage when with the content you've put in, it's gone way beyond that and other games with similar numbering formats.
Indeed. You'll have a pretty good idea of when we're getting close to that though, because the end-game itself is probably going to occupy a few updates alone.Good to know it doesn't need to be version 1.00. you'll simply tell us when you've finished.
I know you mean it tongue-in-cheek, but what's really happened is that gamers in particular are so interested in how game development works that a kind of bastardized version of programmer lingo has become part of regular lingo, and it causes all kinds of confusion since the two don't always match up perfectly (with regular lingo heavily influenced by marketing). Using the kind of versioning I did for LLtP was business as usual for me, but I didn't take into consideration (enough, anyway) the idea that some of my own expectations and language won't match up with the expectations and language of the players.Programmers are so weird.
I did not mean for me actually as I'm studying to be a programmer, but you still got to admit that we are a weird bunch. Like it's natural now, but starting to count from 0 with my first arrays was... weird.I know you mean it tongue-in-cheek, but what's really happened is that gamers in particular are so interested in how game development works that a kind of bastardized version of programmer lingo has become part of regular lingo, and it causes all kinds of confusion since the two don't always match up perfectly (with regular lingo heavily influenced by marketing). Using the kind of versioning I did for LLtP was business as usual for me, but I didn't take into consideration (enough, anyway) the idea that some of my own expectations and language won't match up with the expectations and language of the players.
The version numbers for LLtP work like this:
The first value represents the major version of the game. It will always be either 0 or 1. 0 means the game isn't finished. 1 means it is. That doesn't mean development will stop at that point, but anyone playing it when the first value is 1 will experience a complete game.
The second value started at 1 and increases by 1 for each new minor (ie. monthly) release I put out. I broke that with the second version of this game, when I was still figuring things out, but I've followed this system since then.
The third value represents hotfixes. It resets to 0 with each monthly release, and increases by 1 whenever I put out a minor update that does nothing but fix bugs.
Some developers think of the 0.1 to 1.0 scale as a kind of percentage value. If the version is 0.3, their game is 30% done. The result is that most of them start increasing version numbers by smaller and smaller values for every update they put out, making the whole thing rather confusing. With LLtP, the version numbers should always be predictable and logical. In other words, if you see something like LLtP version 0.10.1 (a version that doesn't exist, thankfully), it means that it's the 10th monthly release of the game (disregarding the 0.15 anomaly that was the second release) and that it includes a hotfix for a bug that cropped up in that version.
What? How could you possibly think that? It's been a part of porn and people's sexual lives for ages.It's an anime porn trope isn't it?
It's not a joke.I guess the joke is it's a petite character doing the boob job.
It's positionally awkward rubbing of dry skin on penis, might as well use the back of her knee or armpit. Why not use hands or mouth if your plan is just making the guy have an orgasm.What? How could you possibly think that? It's been a part of porn and people's sexual lives for ages.
This game uses the porn approach to sex. In other words, there's no need for stuff like lube. If it helps, imagine that Primrose's breasts are lubed in that scene. The same goes for things like anal scenes.It's positionally awkward rubbing of dry skin on penis, might as well use the back of her knee or armpit. Why not use hands or mouth if your plan is just making the guy have an orgasm.