Feature - Rejected Prevent or require confirmation when goals cannot be met in selected location

Just accidentally wasted ~60 turns in a hardcore run because the selected adventure location was The Beanbat Chamber while the adventure goals were set to +1 S.O.C.K., and it got me thinking that having some preventative measures for situations like this might be a nice feature. Would it be possible to have mafia prevent or require confirmation if the goals cannot be met in the selected location?

Do you have a list of all things that cannot be achieved in each location ? That's the difficulty with the request, we can (and do) suggest some common things that can be achieved in some locations, but we cannot parse everything that can't be achieved.

Did you manually change the goal to S.O.C.K. as it shouldn't have been a default for The Beanbat Chamber ?

I don't think that this feature is tenable. The maintenance burden of coding what can (and cannot) be dropped in a certain zone is massive. Items can come not only from (non-) combat adventures, but also from newly creatable concoctions, familiar drops, wandering monsters, or other wonky game mechanics that have or have not been invented yet. Every time we add a new zone, goals would be unusable until all mechanics are fully spaded and coded...

Going to mark rejected.

Easiest way to accomplish this is with a before battle script... parse through goals if any exist, parse through the monsters, and if they don't match, present a popup asking if you really want to continue. That lets Ioeth self-goal-scream without anyone else getting annoyed by the mess.

Basically saying, what you're asking for can already be accomplished with what you have. Though the SOCK specifically will complain since it comes from a non-combat and we don't track non-combat possible results in mafia yet.

I recall asking for this years ago and accepting the result that it just isn't feasible, or more to the point, the cost in dev time to implement and maintain is seriously greater than the projected benefits to community.

Something that might be easier would be to implement a simple check - is the goal listed as a drop (or creatable from listed drops) from a non-wandering monster in the current zone and take some action if it isn't, but this is the BBS solution and falls into the don't need as a mafia feature because it is easily scripted category.

fronobulax said:

is the goal listed as a drop (or creatable from listed drops) from a non-wandering monster in the current zone

Click to expand...

For the SOCK, which is what prompted this thread to begin with, the answer would be no. If you automate the airship every run and get used to ignoring the prompt that comes up, it no longer helps with the situation that prompted the feature request.