In the Halloween event, I found a pretty hot scene involving werewolf transformation. As a huge werewolf fan I was disappointed to find out you lost the form after you exit the dream. So my question is, can you actually become a werewolf outside of the dream? Or, heck, just an anthro wolf at all. The transformation items only seem to give me the ears, tail and dick. Is it possible to transform completely into a wolf/wolf-morph, like Cale?
Werewolf form
- Thread starter Jackson Foxglove
- Start date
There's no "proper" werewolf form, the one in the event is just a specific Wolf-morph build. You can apply it by manually by pressing F12, opening the web console while in-game and typing this :
Code:
Scenes.Halloween.HW = new Halloween();
Scenes.Halloween.WerewolfTF();The knot you get recieves an invalid value when you do that, though, which means the game won't let you save (not that this is a problem per se, since you were never supposed to be able to save like this). You can fix that by resetting the knot like this :
Code:
TF.ItemEffects.SetKnot(player, {value: true});Frankly, while others have said the opposite, there aren't really any good ways to get an actual wolf-morph. Lobos, Canis and Vulpinix all tend to give you a canine-morph character, but while I'd never noticed, it's true how none of them ever actually give you fur (which would appear as SetBody).
This seems to have solved my issue completely, thank you! Oddly setting the knot value to true made me unable to save, I had to set it false to fix it. Aside from that, perfect! Thank you again.
Probably when one of our great FoE writers (or Alder) write it then we even greater Alder code it. Since it was made for Halloween then maybe it would be made into out of halloween content too. Porbably with some interesting perks of been werewolf.
Never suspected it might come from the setter itself, I thought it was an oversight from that specific scene which, since it's both a timed event and because you're not supposed to save while it's active, didn't really need fixing. I'd have reported it sooner if I'd known.
Just assume that anything that crashes is a bug (unless you are doing direct scene calling out of order - and even then, it probably doesn't hurt to put in safeguards).Never suspected it might come from the setter itself, I thought it was an oversight from that specific scene which, since it's both a timed event and because you're not supposed to save while it's active, didn't really need fixing. I'd have reported it sooner if I'd known.