??? & CC (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
immoetality) wrote2012-08-27 11:08 pm
immoetality) wrote2012-08-27 11:08 pm
a note.
This isn’t an open letter to the team. If anyone on Ruby wants to talk to me, then they’re welcome to comment here or e-mail me. Likewise, this isn’t me speaking for the team, but I want to discuss the dynamics of the team as I see it and from the perspective of my character while addressing some personal concerns I’ve been having as of late . . .
Ruby is a team that relies on itself. In nearly every incarnation, the team has been more likely to retreat into itself, even after it explodes at each other. They divide, they separate, they come together. Likewise, Ruby seems to have always had a dangerous element to it. Somehow, in the middle of its co-dependency, it always has a person that will react with violence, with madness, or whatever you prefer to call it. It’s a great testament to the team that they always treat these members not as marginal, but as someone who is just as loved as the rest, valuing their opinion, while also balancing it against what the team wants.
Playing C.C. within the team, she always prefers to mediate and dissipate tension. When she arrived within the team, she saw how often it could react explosively, threatening to come apart at the seams at each turn. So, she threw her stake in to make it stay together. In that same breath, she understands the many different personalities that make up a team, and that is always a precarious balance, ready to be upset. In this case, Naha is an explosive, highly possessive character that would like to make an example of hurting those on Ruby. This isn’t a new development by far; Naha has always been the aggressive one of the two “team-mothers”, and C.C. counters her with pacifism and diplomacy. Counters, but does not stop, however. C.C. has no qualm making a public statement, a safety warning if you will, that Ruby should not be tampered with.
While that ideology may be changing in the near future as the result of team development, the fact is that there are unstable elements within the team, there is action and consequence, and these factors cannot be ignored. I understand that it may not be everyone’s cup of tea to deal with the ramifications of all this, and I have read so many thoughts on plurk that I’ve become nearly lost in the sheer volume. Still, on my behalf, if you have something to say, something that needs to be addressed then let me know or address it to whomever can best resolve this, or any!, situation that arises in play. We’re all playing a game that we enjoy, so if you don’t enjoy this or that, then numerous accommodations can be made or ignorance can be feigned. If none ofthe above is suitable, then conflict is the heart of character development and adds narrative flavor . . .
I’m going to stress this once more, and outside of the cut, because it is the key point to me: I would truly appreciate everyone being forthright with whomever they need to while the dust still settles with the events that have happened or are in motion with the game.
Ruby is a team that relies on itself. In nearly every incarnation, the team has been more likely to retreat into itself, even after it explodes at each other. They divide, they separate, they come together. Likewise, Ruby seems to have always had a dangerous element to it. Somehow, in the middle of its co-dependency, it always has a person that will react with violence, with madness, or whatever you prefer to call it. It’s a great testament to the team that they always treat these members not as marginal, but as someone who is just as loved as the rest, valuing their opinion, while also balancing it against what the team wants.
Playing C.C. within the team, she always prefers to mediate and dissipate tension. When she arrived within the team, she saw how often it could react explosively, threatening to come apart at the seams at each turn. So, she threw her stake in to make it stay together. In that same breath, she understands the many different personalities that make up a team, and that is always a precarious balance, ready to be upset. In this case, Naha is an explosive, highly possessive character that would like to make an example of hurting those on Ruby. This isn’t a new development by far; Naha has always been the aggressive one of the two “team-mothers”, and C.C. counters her with pacifism and diplomacy. Counters, but does not stop, however. C.C. has no qualm making a public statement, a safety warning if you will, that Ruby should not be tampered with.
While that ideology may be changing in the near future as the result of team development, the fact is that there are unstable elements within the team, there is action and consequence, and these factors cannot be ignored. I understand that it may not be everyone’s cup of tea to deal with the ramifications of all this, and I have read so many thoughts on plurk that I’ve become nearly lost in the sheer volume. Still, on my behalf, if you have something to say, something that needs to be addressed then let me know or address it to whomever can best resolve this, or any!, situation that arises in play. We’re all playing a game that we enjoy, so if you don’t enjoy this or that, then numerous accommodations can be made or ignorance can be feigned. If none ofthe above is suitable, then conflict is the heart of character development and adds narrative flavor . . .
I’m going to stress this once more, and outside of the cut, because it is the key point to me: I would truly appreciate everyone being forthright with whomever they need to while the dust still settles with the events that have happened or are in motion with the game.
no subject
no subject
no subject
no subject