@Ganymede said:
@Coin said:
Then you need to point out when you file for the asp that this is how your vampire operates. Because your opinon is just that--and not everyone else's. So we're back to context.
I am hesitant to pass judgment on player's reasoning when it comes to aspirations. I see your point, but it borders on violating the "wrongfun" doctrine. I realize that GMC/CoD encourages greater ST participation in the crafting of a PC, but I am cautious, in a MU* context, of setting up a system where staff has to constantly question why a player is requesting something.
Nothing I said is meant to be interpreted as my saying you should judge. But requiring context is important. So instead of saying "well, i guess they could have a reason for this", staff should ask, "thiscould work, what's your reasoning?" and try to leave bias behind.
@Derp said:
@Coin said:
this is because the book and the writers of the book assume that it's understood that each Aspiration, even short-term ones, are supposed to further the character's progression.
I get what you're saying, and where you're coming from, but I disagree with your premise.
An aspiration is a tool to help advance a character through a story, yes, but it's really nothing more than trying to set out a couple of points that you would like to see happen in this character's particular narrative at that time. They are things to keep in mind, and directions you want to take them in. Nothing more than that. They don't have to represent some deep and philosophical soul-searching journey. They're just... what they are. They are things that either the player or the character want to see happen in a story, minor accomplishments for short-term stuff and major accomplishments for long-term stuff. It doesn't have to go any deeper than that, and trying to judge what aspirations are worthy may end up being more of a pain in the ass than it's worth. All that should really be required is:
Is this an action that requires the character to go out on the grid and interact with the world in some way that's important to their enjoyment of the game?
Some context might be necessary, on certain ones, sure. 'Buy Sammy a beer' might not be great, but 'Buy Sammy a beer so that we can start establishing a friendly relationship' is better. Either is simple, gives the character and the player a direct goal to work toward (rather than having them wander aimlessly wondering what to do) and is easily check-able.
If your status quo for establishing a relationship is buying someone a beer, and you routinely use "buy X a beer to establish a relationship", then it's a bad Aspiration, IMO. I don't care, particularly, if it's viable or not, if you are going to abuse it. So once? Sure. Once every long while? If you can tell me why you think it's relevant again. Once a week? Nope.
This is obviously my own criteria, and what I interpret from the books.