thesolitary25
Newbie
- Nov 23, 2024
- 22
- 26
- 32
Oh my God, the game is over and not a single scene with Carol, what a monstrosity 
YES! THAT! I'm glad someone finally fucking said it.Oh my God, the game is over and not a single scene with Carol, what a monstrosity
smasher_the_smith
Newbie
- Feb 4, 2020
- 73
- 176
- 150
Status of Lust Time in Lust Theory - Season 1 and Lust Theory - Season 2: ELIMINATED
Do you hate Lust Time as much as me? Remove it with the Universal Inceton Lust Time Eliminator Mod. Now with support for the entire Lust Theory series and a new universal mod system.
Do you hate Lust Time as much as me? Remove it with the Universal Inceton Lust Time Eliminator Mod. Now with support for the entire Lust Theory series and a new universal mod system.
Okay, v0.8.3 and 0.9.0 review, I'm caught up now!
You don't have permission to view the spoiler content.
Log in or register now.
How do I unlock the full gallery? Every time I reinstall, I have to start all over again – it's hell!
I hear what you are saying, but Carol has already been introduced, and the 'AI Overlord' aspect of her has already been established.
So anything she does to further her plotting is still internally consistent with what has been shown so far.
If Carol didnt exist, or more to the point, if it was only during *that* ending that she was introduced would it be a full on 'dafuq?'
Yeah but it's not, that's the whole point. Her plotting has one purpose: To bring MC and Alice together.
In this version, we're supposed to grasp that she changed her mind once she saw how MC was acting, I guess? Except her original purpose is never explained in this ending. And yet, she still pursues actions that serve her original purpose and go directly against her new purpose, up until almost literally five minutes before she achieves said original purpose at which point she freaks out and has to conjure up obstacles of biblical proportions to fuck with her own plan.
She's not "furthering her plotting", she's suddenly doing the opposite, she's actively trying to tear apart all of the plotting she did. And more importantly, you wouldn't know it without the other ending to explain the missing piece of the plot.
She still didn't, for instance, give MC a way to fix his relationships with the other LIs (which would've gotten him out of Alice's hair if this is what she now wanted), she still sent him on the VERY DATE she then freaked out about and sabotaged.
Carol being an AI Overlord isn't the problem. It's her doing a 180 on her motivations (not the stated ones, the hidden ones that are meant to be revealed and are during ending 1) quite literally out of left field that is.
Last edited:
OWSam000
Well-Known Member
- Mar 1, 2022
- 1,750
- 2,011
- 387
I like the first ending better than the second shit ending. So why there will be a choice to choose either Alice or others? A season 4 coming or does that choice really matter or it will just like the end of season 2 that nothing will happen but the a set ending?
Surfup64
Newbie
- Jul 18, 2024
- 31
- 70
- 96
Well because there will be multiple endings or prologues for each girls or combos
I suppose that's all fair.
I guess I'm so numb from all the previous ass pulls, plus i always suspected Carol had her own agenda beneath the surface, that i just rolled with it. Lol
Again, her having her own agenda was always the likely scenario. Her going back on her agenda 5 minutes before the end of the game was the asspull.
But fair enough yeah lol.
Hey, has anyone said that ending 1 rocks and ending 2 sucks?
(yeah, everybody has, I know - I just felt like reiterating the concept, in case Lancelot is reading)
(yeah, everybody has, I know - I just felt like reiterating the concept, in case Lancelot is reading)
James-of-alabama
Member
- Aug 18, 2019
- 270
- 666
- 281
Resort of temptation is full of monsters and decrépit beings so lancelot is happy with that game
Oh hey, previous Inceton writer. Cool cool.He isn't. Like he said, he has to spend the next 2 months fixing Embercat's fuckups. Which based on his previous writing contributions will include scenes of characters being raped by gross, decrepit homeless men or the family dog.
Fuckups in Lancelot's eyes only lol. Practically everywhere else, whether that's here on f95 or on Inceton's own Discord server, I've only seen high praise for Embercat's writing.
So, yeah. We've been dunking on Ending 2 hard, and will continue to do so.
Guess we'll see how the next update turns out.
How do I unlock the full gallery? Every time I reinstall, I have to start all over again – it's hell!
I know this was written with sarcasm, but if we take it at face value that this Lancelot guy really did think Embercat fucked up all of the writing since taking over in S3, it does beg the question by what metric did he use to come to that conclusion?He isn't. Like he said, he has to spend the next 2 months fixing Embercat's fuckups. Which based on his previous writing contributions will include scenes of characters being raped by gross, decrepit homeless men or the family dog.
Was it the, from what I've seen on F95 at least, overwhelmingly positive feedback by the audience, hailing it as salvaging the train wreck left by S2, and doing some nice character growth with each installment?
Was it the frequency of the updates, which were close to almost a week per at times, compared to most other devs, team or not, that would typically take at least 1-3 months for the size of these updates?
Was it the lack of complete asspulls that made the plot an incoherent mess?
When comparing the two endings of the latest update as a compare/contrast exercise, was his work too satisfying?
Was it the complete lack of shitty fucking Lust Time?
Seriously, what was the metric that determined Embercat sucked and needed to be fired?
Last edited:
- May 22, 2017
- 3,466
- 9,154
- 748
Likely a combination of all of it. Ember tried to fix something that was designed to suck
rebellare
Newbie
- Mar 30, 2017
- 33
- 20
- 46
Hello everyone,
Lancelot asked me to post a statement here, regarding Inceton Games and our stance on this whole subject/s.
Official Statement on the Termination of Paper Boat
Inceton Games CEO Lancelot
Inceton Games confirms that the professional collaboration with the freelance writer known as Paper Boat (Embercat) has been formally terminated. This decision was made after an extended production period and was based strictly on documented workflow incompatibility, delivery reliability issues, and production pipeline disruption. It was not a personal decision, nor was it based on isolated creative disagreements.
TLDR; Good ideas, bad execution
From the very beginning of the cooperation, Paper Boat was provided with:
1. Repeated Deviation From Agreed Production Direction
Throughout the production of our games, Paper Boat consistently challenged or attempted to rework already-approved core narrative and technical constraints, despite those constraints being directly tied to engine limitations, platform compliance, and internal pipeline safety.
Examples include:
2. Excessive and Disruptive Communication Volume
While initiative is valued, communication volume reached an operationally disruptive level. The writer regularly sent:
This created a situation where production management time became dominated by communication overhead instead of actual execution.
3. Delivery of Unfinished and Non-Finalized Material
Although significant writing volume was produced, a consistent pattern emerged of delivering material that was not production-ready, including:
4. High Frequency of Post-Submission Corrections
A large portion of submitted material required post-delivery correction due to:
5. Premature Financial and Long-Term Control Discussions
Despite Episode 3 not yet being finalized and undergoing multiple active revisions, repeated discussions were initiated regarding:
These discussions occurred before the successful delivery of a fully completed, locked production episode, which is not aligned with Inceton Games’ standard contractual workflow.
6. Direct Production Pipeline Impact
As a direct result of the above issues:
Final Determination
Inceton Games operates under a high-output, multi-disciplinary production model where:
While Paper Boat demonstrated enthusiasm and creative investment, the collaboration ultimately failed to meet the operational standards required for reliability, scalability, and production stability.
For these reasons, the collaboration was terminated in the interest of:
Legal & Professional Clarifications
Closing Statement
Inceton Games will not engage in public arguments, speculation, or social media disputes regarding internal production matters. The company remains focused on its team, its players, and its release roadmap.
Lancelot asked me to post a statement here, regarding Inceton Games and our stance on this whole subject/s.
Official Statement on the Termination of Paper Boat
Inceton Games CEO Lancelot
Inceton Games confirms that the professional collaboration with the freelance writer known as Paper Boat (Embercat) has been formally terminated. This decision was made after an extended production period and was based strictly on documented workflow incompatibility, delivery reliability issues, and production pipeline disruption. It was not a personal decision, nor was it based on isolated creative disagreements.
TLDR; Good ideas, bad execution
From the very beginning of the cooperation, Paper Boat was provided with:
- Full production onboarding
- Clear narrative and content restrictions
- Render-count limits
- Technical constraints of static visual novel development
- Internal approval process
- Multi-department production workflow explanation (writing → 3D → animation → coding → QA)
1. Repeated Deviation From Agreed Production Direction
Throughout the production of our games, Paper Boat consistently challenged or attempted to rework already-approved core narrative and technical constraints, despite those constraints being directly tied to engine limitations, platform compliance, and internal pipeline safety.
Examples include:
- Attempting to restructure key scenes after they were already staged for render production.
- Repeatedly questioning core technical restrictions such as signal availability on the island in Lust Bound, which had already been inherited from legacy scripts, causing unnecessary continuity friction.
- Attempting to introduce narrative mechanics that conflicted with internal platform safety rules and monetization compliance.
2. Excessive and Disruptive Communication Volume
While initiative is valued, communication volume reached an operationally disruptive level. The writer regularly sent:
- Multi-page breakdowns for minor scene confirmations
- Late-night and weekend multi-message analysis dumps
- Repeated follow-ups on non-blocking issues within hours of earlier messages
This created a situation where production management time became dominated by communication overhead instead of actual execution.
3. Delivery of Unfinished and Non-Finalized Material
Although significant writing volume was produced, a consistent pattern emerged of delivering material that was not production-ready, including:
- Draft-state scenes entered into Celtx without final technical validation full of grammatical errors and story inconsistencies.
- Placeholder logic embedded into scenes that conflicted with Ren’Py implementation rules
- Scenes submitted without full path validation for branching logic
4. High Frequency of Post-Submission Corrections
A large portion of submitted material required post-delivery correction due to:
- Continuity conflicts with earlier episodes
- Pacing problems caused by exceeding render limits
- Technical conflicts with animation sequencing
- Conflict with pre-established character behavior constraints
5. Premature Financial and Long-Term Control Discussions
Despite Episode 3 not yet being finalized and undergoing multiple active revisions, repeated discussions were initiated regarding:
- Early payment
- Payment in advance
- Payment for a story that was not complete or riddled with mistakes.
These discussions occurred before the successful delivery of a fully completed, locked production episode, which is not aligned with Inceton Games’ standard contractual workflow.
6. Direct Production Pipeline Impact
As a direct result of the above issues:
- The 3D and animation teams repeatedly paused production while waiting for corrected scripts.
- The coding team was forced to delay implementation due to unresolved branching and continuity conflicts.
- Render scheduling became inconsistent due to late structural changes.
- Internal release projections had to be actively protected through emergency resource reassignment.
Final Determination
Inceton Games operates under a high-output, multi-disciplinary production model where:
- Writers
- 3D artists
- Animators
- Code team
- QA
- Release management
While Paper Boat demonstrated enthusiasm and creative investment, the collaboration ultimately failed to meet the operational standards required for reliability, scalability, and production stability.
For these reasons, the collaboration was terminated in the interest of:
- Project continuity
- Team efficiency
- Deadline protection
- Financial stability
- Operational risk management
Legal & Professional Clarifications
- This termination was not disciplinary.
- It was not personal.
- It was not retaliation-based.
- It was based on documented workflow failure and delivery unreliability.
- All delivered work is being handled in accordance with internal review and contractual obligations.
- No further private development materials will be discussed publicly.
Closing Statement
Inceton Games will not engage in public arguments, speculation, or social media disputes regarding internal production matters. The company remains focused on its team, its players, and its release roadmap.