Home
Creators
Search Recent Random
Posts
Search DMs Popular Hash Lookup Tags Random
Importer
Import FAQ
Register Favorites Keys Review DMs Logout
Community
Telegram ThePornDude
Home Creators Posts Import Register Favorites Logout

Game Quests in Patreon Builds (Patreon)

Published:
2022-09-30 10:33:22
Imported:
2026-06

Poll

Game Quests in Patreon Builds

  • Release quests directly into the world as soon as they are created 67
  • Release quests directly but have them off by default, enabled by a game setting 451
  • Dont release quests until they reach a certain level of polish 1152
  • 2022-09-30
  • 1670 votes
{'title': 'Game Quests in Patreon Builds', 'choices': [{'text': 'Release quests directly into the world as soon as they are created', 'votes': 67}, {'text': 'Release quests directly but have them off by default, enabled by a game setting', 'votes': 451}, {'text': 'Dont release quests until they reach a certain level of polish', 'votes': 1152}], 'closes_at': None, 'created_at': datetime.datetime(2022, 9, 30, 10, 7, 50, tzinfo=datetime.timezone.utc), 'description': None, 'allow_multiple': False, 'total_votes': 1670}

Content

Following up on this post by our designer Brudi we have a question and a poll for you:

Should we publish our implemented WIP quests with the upcoming builds in the game world or wait until they reach a certain degree of polishing?

A more detailed explanation for the choices:

1. We would put all quests created directly in the world and release them as is. This will have them be very unpolished, missing cutscenes, sex minigames, combat encounters, potentially buggy, etc. and with non-final placement in the world for quick testing. Also this would mean some serious spoilers.

2. Same as above but instead of just having them there we would gate them behind a game setting that would be off by default so only users that choose to expose themselves to the quest in the aforementioned state will be able to play them.

3. We dont release the quests at all until they reach a certain level of polish that we define internally. This would mean that it would take considerably longer for quests to appear in the patreon builds but they would be in a state deemed "safe to publish".

Choose wisely,

-Wild Life Team

Comments

Crispypags

i honestly don't want quests spoiled till game is released

ObsideanHawke

Take your time and get them right. It’ll be worth it. 😊

Edon Serifi

I Do believe that Option 2 is the Best for All. Since, even if you don't want to experience any spoilers before the Release, you can just leave the Option off. Having quests in the testing Version also helps the devs with Bug finding and such. So Overall a benefit for All. No matter if you want to play them or Not.

Plover1198

Hello, On this subject, I wanted to ask you, will the quests "block" the game, by successive stages? Like for example, first unlock a kerpali by a mission, then unlock the different sex scenes via secondary missions? Or will we still have access to it as we currently do? Thanks.

Adeptus Steve

The sandbox content will remain completely unlocked and fully available as it is currently. In the game however there are certain things that you unlock later on. Most important example is you start the game as Max and unlock Maya gameplay after reaching a certain point in the main story.

Kraiklin

I'd say option 3 unless you think having people trying the quests out in their early form would be helpful for testing. In that case option 2

BlankedCheck

I dont get why people who want to play the quests would have to follow people who dont want to play them. It seems counter intuitive to put those options for a poll. Why would people who dont want to play unpolished missions care about those who wouldnt mind. Literally everyone is happy with option 2. If you want you can play it and if you dont want to than its blocked and you dont have to do anything to carry on with your current experience. All this is, is people gatekeeping people who want to play. Whether or not its the majority, my playing experience doesnt affect anyone elses, so why should they get a say in what i enjoy about the game?

Chris Tex

As long as the quests don‘t bind ressources that would otherwise advance the development of the game world, I‘m fine with either option.

Blackwater

Picked option two, but I would combine 2 and 3 really. Release the quests when they have a certain amount of polish, but allow for an option to turn them off. Personally I don't want too many spoilers on the quests and story untill the game is released properly so the game would at least be fresh to me rather then having played the quests x amount of times already.

Toby Kat

If adding WIP quests to these builds would be considered enough for you folks to internally justify distributing them through Steam, then let them questies flow~ :3 Heheh, I'd hope that quest info in the UI would be optional in the end, but at worst the testers could simply ignore them. I'd say make them optional, but you do whatever is most helpful to you, even if that's holding off entirely for the time being.

EagleEyes762X51

I would like to see more quest, honestly I’m stuck in the middle between 2nd and 3rd options, went with 3 because it would be best to wait until they’re all polished up, that said, new animations, new sex mini games are enough to keep me occupied. Perhaps the two quests that were mentioned in the previous post can be released when they’re done and good and they be released in that locked mode, so then if anyone is worried about spoilers they can opt to play it or not.

Horny

Definitely option 2. Avoids spoilers for those that dont want it while allowing people to test it early and provide feedback.

Plover1198

OK, thank you. Regards.

Anonymous

Are you planning on adding painting tools for custom coloured/pattern skin and fur?

Ghostface N7

Nah, just get'em done right, as polished as possible.

Kraiklin

I don't see it as gatekeeping. My logic for voting option 3 was I've followed too many projects that try to release all the content all the time and get bogged down trying to deal with bug reports, feedback, and requests for prototype versions - once it's in people's hands there's often pressure to change a workflow. Unless there's actively a benefit to the development from having this stuff tested I'd rather they are free to focus on getting it to the state they want it, and then let us in to test and feedback. Just my 2 cents though, I do see where you're coming from.

Andrew Davis

Option 2 is the best, because anyone who doesn't want to wait to experience the quests have the choice to. I personally wouldn't want to wait, even if the content is incomplete. meanwhile those who want to wait for the content to be fully polished have that choice. if anything it just increases playability of the game even in these early stages.

Kobei Son

3 finish everything first, don't rush it, we're not in a hurry. We all don't want the same situation like Cyberpunk 2077 haha

badunn

Hey Steve, u should try this poll again in another 3 months for the people who want to legitimately test the game?!(i say develop jussst a bit more) I was leaning hard toward option 2, but option 3 called. I think itll truly be test-worthy once there's more bits and pieces added to the quests, and less placeholder stuff, etc.

Anonymous

I’m fine with option three but with that said, all I care about is what is convenient for y’all with progress updates or releases in regards to your workload and advancement of the project. Whatever method is most beneficial and convenient for you guys, that’s all I care about. 😉💪🏻💯

Luke

Number 2 is the fairest selection for all. For everyone picking number 3 then just don't enable the quests. Others that want to can enable them. Its by choice not design where one group gets what they want and the others don't. I choose 2.

Smorgasbork

If Adeptus releases the quests prior to polishing it will give him more to work with because Patrons will let him know about any issues with the quests or make important suggestions that can greatly improve them. That’s the whole idea of “early access”.

BlankedCheck

What your saying makes sense but to your point on bug reports, feedback, and requests; This is the exact way alpha/beta testing works. Why would you not want to have users testing and reporting bugs. This is normally how the process goes is it not? If the plan is for the devs to release a polished project, than testing from users and feedback is essential. If you just want them to keep it a secret and have a small team test for bugs; so there are no spoilers or delay on release, they will miss a large amount of them and then the "polished product" will have bugs. And at that point everyone who voted 3 will say "but hey we chose to wait for a perfect product and you gave me this" or something to that affect. And to gatekeeping yes, if you dont want to play the missions unfinished/having spoilers and you are making a decision to have other players do the same it is in fact gatekeeping. And if there is a mass amount of bugs being reported happens push back the release, you will be happy once the polished game comes out because they will be addressed and you wont have to experience them. Not calling you wrong just wanted to express a little more. I just dont see how everyone doesnt win from option 2. Its actually the best of both worlds with no compromise, where as option 1 and 3 alienate one group or the other.

Station Noise

there's 50% chance, 31% of patrons will switch to a different tier after this poll

Hgamer

Gotta say.. very impressed the developers continue to ask for feedback from members. Well done!

Narttu

I’m torn between options 2 and 3. If it will help with development to include quests in early builds, for us to help with testing, then I would want it to be done in whichever way is best for the dev team. Either way, I think having the quests gated in settings before full release is a great way to accommodate all of your early players; and your fantastic communication with us will keep everyone informed as to what they’re opting in to or out of in those settings.

Mostacho

Based on the animations and what is known so far, I think you are already following a good direction. Minimally changing or improving a finished quest seems to me to be the more effective way to success. You will never be able to convince everyone, so you should implement your ideas and adapt them if absolutly necessary.

Dvpainter

I think option 2 is the most beneficial one, you have the choice to opt-in live for a bit of early QA testing on the quests, and I think if it was chosen by the team that it would maybe help out the developers with people pointing out solutions that may not seem obvious just from a wider viewpoint than the dev team may have exposure to. I don't think option 1 is viable however imo

Station Noise

to be blunt and from my perspective, I would switch to the early access tier, just so I can get my hands on the prototype quests. Keep up the good work, this is next level shit you are doing

DevastatingDave

Number 2. Number 3 seems to be others telling those who want it you can't have it. If it's disabled by default, it's the same outcome for those who don't want anything and they can be happy. Those of us who want it will also be happy by turning it on.

WarMallet

I have not read anything and don't know anything. I say choice number 3 for me. I have no problem waiting for the very best/polished versions. Not sure how you will get any feedback from us patrons without any early unpolished releases though.