Posted by usvtheman on 11/3/2022 12:23:00 AM (view original):
Pulldowns are a gray area. You could easily feasibly think that recruits who weren't getting attention from D1 schools would settle for a D2 school making a hard push.
This was not. Nobody would feasibly think it should be a net advantage to tell a kid you would redshirt him and then go back on it, nor that it would make any sense whatsoever for recruiting to work in that manner when every other coach is having to expend AP points to unlock schollies. You would only do this if you believed it was an exploit. You are reverse engineering a far-fetched justification that I'm positive none of these people actually believed. Sorry. I don't see it at all.
Not everyone thinks that though. Lots of folks think that kids who consider themselves to be D1 players should always just choose juco instead of settling for lower division effort. Since the game allows it (in this version and the previous version) veterans all know about it and it seems natural to us - but when it was first discovered, that wasn't true at all. Because the game design isn't clear that it's possible, or how, users originally stumbling on it presumably had to guess about it, and then determine for themselves whether or not it was an intended feature.
The only thing making the redshirt thing weird *at all* is having to inform of a redshirt first. But again, that wouldn't be the only intentional feature that was awkward and forced in this game. And of course the individual user doesn't know anything about what other users are having to do. They only necessarily know that it's a benefit for them, over what they were doing before. Nobody is obligated to care about what other users do, about what "standard practice" is.
Call it reverse engineering if you want, but the point is that it should never be on the user to determine developers intent. NEVER. That is incredibly poor game design and customer service practice. There are lots of "out of the box" thinkers out there, non-conformists who will never fit into a "nobody would feasibly think" kind of narrative. We don't need mobs with pitchforks coming after them every time they figure out something the rest of the community is sleeping on - not until they use it in a collusive manner. Developers can and should explicitly clarify when something is being done going against intent (and issue warnings when appropriate), but again the first priority should be to provide the product that has a clear and transparent gameplay, relatively free of exploitable bugs.