- Mar 1, 2018
- 2,158
- 2,441
Download the "Move npc" mod or something like that. Stand in the corridor in the mansion. Go to the phone book, select the npc, hover over the status effect. Close the phone book window. Use the transformation potion on the npc.Except there's nothing even in lore that REQUIRES a specific NPC to be a furry. You could replace any of the full-furry NPCs with kemnomimi and it wouldn't break a darn thing and would still make perfect sense.
It's just furries trying to force furry and making a mockery of choice.
Most of those 'useless races' are player made and Innoxia just adds them to the game with their permission.i come every so often to check on this dumpster fire of a game and it seems like its always the same. but what really slaps me on the knee is the never ending additions of useless races and subraces that dont add anything different gameplay wise. everyone dissing on the developer dont realize shes quite smart milking paypigs for what they are worth
ive said it before its a shame cause this game could have offered some cool sandbox gameplay and with user mods its replay value would be great
i know. read the post again. i said that those races are the only thing that gets added, it isnt much different if the players or the dev put them in, it doesnt do anything for the game. in fact letting players bloat the game with them is what keeps many of the paying customers around it seemsMost of those 'useless races' are player made and Innoxia just adds them to the game with their permission.
While I agree that the game would benefit from trimming some fat, Lilith's Throne owns most of its popularity to its in-depth customization. Reducing what is already there would put you on thin ice with the community and I don't think Inno wants to rock the boat in that regard.i know. read the post again. i said that those races are the only thing that gets added, it isnt much different if the players or the dev put them in, it doesnt do anything for the game. in fact letting players bloat the game with them is what keeps many of the paying customers around it seems
I don't mind the subspecies bloat as much. I object to the species bloat. I actually liked how cat-morphs used to work, where specific subspecies were defined by fur/patterns/tail types.Were it up to me and I'd get rid of most sub-morphs and just rename their "parent" morph something more generic; dogs -> canine, cats -> feline, etc, and from there just let people use their imagination to dictate what that particular NPCs is and how they look. That's, like, half the point of a text-game after all. But some people can't live without the "confirmation" that comes with the game recognizing your appearance to the smallest detail.
It's a grey area, though I feel like exceptions can be made for sub-morphs provided these do something different from their main counterparts (something more than just different stats). Pegasi gain wings which in turn allows them to fly (something equidae can't do). Unicorns are a bit more finicky, since we're already capable of magic that means their only defining trait is the horn (makes more sense for NPCs, as magic is rare). Both are entirely doable without it though - give a horse a horn or some wings and people should instantly recognize them as a unicorn/pegasus, even without official labels.I don't mind the subspecies bloat as much. I object to the species bloat. I actually liked how cat-morphs used to work, where specific subspecies were defined by fur/patterns/tail types.
I mean, Inno did it with Horse, Pegasus, Unicorn and Alicorn-morphs. Give a character horse bits and they're a Horse-morph. Give that Horse-morph wings and they're a Pegusus-morph. Give them a single horn and they're a Unicorn-morph. Give them both and they're an Alicorn-morph. Yet we currently have a discrete "Gryphon-morph" race in the game when - IMHO - Gryphon-morphs should be some kind of combination of Harpy and feline.
Saberspark vibes; "Got a new thing coming out Friday!" (read: "Anywhere from next Wednesday to a month from now")Personally I consider the development a running gag. It's always a delay. Always something coming up. I see an update on the site and I immediately think, "Oh, how long is going to be pushed back this time?" I don't have to read the title, 99.9% of the time, the posts are always about a delay.
Well theres a thing there now lol. 4.3.1 is outSaberspark vibes; "Got a new thing coming out Friday!" (read: "Anywhere from next Wednesday to a month from now")
Well thats impressi...Well theres a thing there now lol. 4.3.1 is out
Changelog:Hello once again,
As you'll see from the patch notes, this update includes the content to replace Penelope's placeholders, but it mainly adds a lot of contributor content. There are several pull requests which I've merged into this version, which are primarily focused on fixing bugs. There's also some new content from the contributors AceXP and Nnxx, the addition of which is what led to me pushing this version's release date back to today.
From AceXP, there's a new scene in Lilaya's lab, where you can sneak inside once per day to watch a small sex scene between Lilaya and Rose. AceXP has also added some new content for Angel, which becomes available after purchasing a prostitution license from her and then returning to her office afterwards.
From Nnxx, a bakery has been added in the north-west of Dominion. The horse-girl who runs this bakery has some sex content, and also sells doughnuts (which provide an HP recovery effect).
Now that I've got this release out, the next update will be a preview again, and will likely be out in a week or so from now. I'll make a post in a couple of days to give you my detailed plan for the next few versions, but in brief I'm planning on merging some more pull requests and adding some more content from AceXP for the preview version, as well as potentially adding some main quest content.
Thank you all so much once again for your support, and I'll see you again in a couple of days when I make my detailed plan post! See you soon!
P.S. This version is 0.4.3.1 instead of 0.4.3 as I used 0.4.3 as a temporary version when pushing to github, so I needed to iterate it one more step to differentiate this public release from that work-in-progress version.
v0.4.3.1 Patch Notes
AceXP's content contributions:
Nnxx's content contribution:
- Added a scene for watching Lilaya and Rose have sex in Lilaya's lab.
- Added repeatable sex content for Angel, which is unlocked after visiting her after purchasing a prostitution license.
Contributors:
- Added a bakery in the north-west of Dominion, called 'The Creamy Bakey'.
- Added a new horse-girl character, Callie, who runs this shop, and added some sex content for her.
- Added three new doughnut food items which can be purchased from Callie.
Engine/Modding:
- Fixed issue where newly generated offspring would be of a random subspecies if they were meant to be a half-demon. (by AceXP)
- Fixed issue where sometimes starting lust would be zero for newly spawned encounters instead of at their resting lust level. (by AceXP)
- Fixed bug where if a character was immobilised then no orgasm options would be available for them to choose from, which led to a blank action grid being displayed to the immobilised player when a character reached orgasm. (PR#1638 by miome)
- Added support for instantiating all NPC classes via the addNPC(String npcGenerationId, String parserTarget) method by using predefined names (like FieldsBandit) or qualified names (like dominion.DominionAlleywayAttacker). Also updated the default (no parameter) NPC constructors to make use of gender preferences. (PR#1615 by AceXP)
- Fixed issue where offspring subspecies names weren't being generated correctly, fixed issue where offspring between demons and non-demons were not being generated as the correct subspecies, and added previously unused dialogue for all calendar months in the player's room. (PR#1634 by AceXP)
- Fixed issue where a player wearing the correct patrol uniform would auto-fail the uniform check during Enforcer alleyway encounters. (PR#1635 by DSG)
- Maxis010's bugfix PR#1630:
- Default penis and vagina values should now always respect the default values drawn from the character's race upon generation.
- Event log entries are now capped at 50 to address a potential memory leak issue.
- Stopped gear resealing onto the character upon loading if it had already been unsealed.
- Multiple dialog & tooltip fixes (with contribution from Phlarx).
- Moved QUEST rarity clothing checks to banishNPC method as previously calling it in the unequipClothingIntoVoid method was causing a duplication bug.
- Changed all removeNPC method calls to banishNPC method calls so that all NPC removal checks are applied.
- If the player's offspring are being incubated in an NPC which is removed, then the offspring are no longer deleted.
Clothing:
- Filled in all placeholder dialogue in Penelope's spa, 'Woolly Heaven'.
Bugs:
- The succubus/incubus attackers in Dominion's alleyways now draw on your gender preferences to generate their gender, instead of always being either male or female.
- Parsing fixes.
- Corrected imp lore description incorrectly stating that imps could not self-transform.
- Fixed issue where externally-defined sex managers would throw errors if a preference returned an empty String.
Once again, Ace is responsible for the majority of actual content being added. That's almost as much content as we got during the last 6 months lolVersion: 0.4.3.1
Developer's post:
Changelog:
I, for one, welcome Inno's contributions to the dev team's project.Once again, Ace is responsible for the majority of actual content being added. That's almost as much content as we got during the last 6 months lol
I haven't looked, but I assume that the "event log" is the text dump on the right that says stuff like "game saved to blahblahblah." If so, that wouldn't have any impact on gameplay, and capping it is long overdue.Hmm...
...Wait "Event log entries are now capped at 50 to address a potential memory leak issue."
Correct me if I'm wrong, but would that not literally break any larger events?
Does this even fix the issue... or just stop the process in general?
Version: 0.4.3.1
Developer's post:
Changelog: