You were not the only one I was referring to. If I was going specifically after you, I would have stated you were the only one at fault.
Hopefully that clears things up. I am not specifically attacking you
There was never an issue with asking for specifics. An issue presents itself when people get angry about it. We’re all mature developers here, well, should be. Displaying anger towards the devs, even if you are angry, contributes nothing good. Period. Some people just need a verbal warning – others, a 2-day-ban, and still others, removal. If someone can’t even keep their cool with something that they know the devs REALLY WANT to implement, and that they did NOT intend for it to break whatsoever, then something needs to be done, whether it be a warning, ban, or removal.
Echo, our definition on angry seems to differ quite a lot. Two of the quotes that you’ve presented, to show developers being angry, are questioning the currently available facts, nothing more or less. Are you saying that developers shouldn’t be able to ask for a realistic timeframe?
CJ asked whether or not it would require a further week whilst Kirky asked whether the update to fix the issue will require another iOS update to be pushed through, both were legitimate questions. If you remember correctly, ROBLOX’s transparency allowed for us to see why they couldn’t just push the update to PC, which, if I remember correctly, was to do with network changes meaning that if iOS user did join a game, they would disconnect everyone. It is reasonable to ask whether it would require another iOS update based on that.
I, personally, have no issue if people want to be angry about something. The only thing I care about is whether they can submit content which has some value. Sure, my reply to the thread was both snippy and heated, but it presented my issues with what was being said - which CodeWriter kindly corrected for me, despite the demeanor I displayed. I apologised.
They’re not going to start dishing out bans just because people question them. You’ve proven that with your quotes of ‘angry people’, where only one is a legitimate claim, in which it displays no useful, or discussable, content. And even if they did, that would mean they’d need to clamp down far more rules for this forum as just having one bannable offense doesn’t ring true.
I know which two you’re talking about. When I read them, I picture them being said in a snarky voice – if they didn’t intend for it to be that way, then that’s another side-effect of the weakness of writing.
Although I did not agree with what you said, I don’t hate you, nor want you removed. If I had said “just warn the members not to be angry with you”, he would have been thinking “We already do that.” – Although removing isn’t exactly what I want, it’s the best word to get the point across. IMO, RbxDev should be a place where ROBLOX devs can speak freely and no ill consequences will follow – if not, it’s the same as posting the update on the normal ROBLOX forums.
Since you edited, I might as well:
Maybe I’m only able to understand this because I worked a bit on projects for FEAR (largest ROBLOX group) with a huge player base. No matter how understanding, nice someone seems on the outside, deep-down, insults from legitimate people (i.e. you) are fucking heartbreaking. Excuse my language, but that’s the only way to express the severity of the issue. It gets even worse when multiple people are displaying anger towards you. When this happened to me, I felt helpless, useless, and unwanted, and I stopped on the project I was developing. So please, keep in mind that ROBLOX employees are people too, and that bashing them can cause serious emotional issues, potentially causing them to lose interest in the project.
I wouldn’t say it’s an issue with the writing, but rather how people have come to know others through closer ties or hearsay. Through these added connections, people add on those notions when reading what other people have said, since for me personally, neither of those two questions posed were snarky when you look at the information provided by ROBLOX, due to their transparency. But that’s neither here nor there, and you are just as entitled to your opinion as I am to mine.
Offence is taken, not given. As you’ve displayed yourself, everyone has a different notion on what is, and isn’t, a display of something. Sure, you could call this a ‘chicken way out’ kind of answer, but I do stick by it. What I said was indeed heated, and lead by my own ego and temperament, but it was in no way meant to reflect an insult.
I agree with you 100%. That’s why we have to be exxxxxtra careful when we’re communicating with the devs. We have no clue how our actions will impact their work ethic. They can be perfectly okay with it, or they might not. You took offense to my earlier post, and I didn’t mean it – you took it. I read those two posts and thought they were snarky – I took it. Let’s just hope CodeWriter isn’t secretly depressed right now.
“Would you be willing to be more lenient* towards the devs if they were more transparent?”
It’s as if we’re naturally angry towards “the devs” if they aren’t transparent… I don’t think this poll was worded correctly, which is why I didn’t vote. It assumes anyone who votes is angry/intolerant towards them if they aren’t transparent. “Willing to be”, sounds like it’s such a hard thing thing to be “more lenient”. Yes, this matters if you’re going to try to collect voices from people. “Would you prefer the devs to be more transparent about upcoming updates?” I think is better. Have you taken Statistics? They cover this completely in the Survey portion of it. I don’t have much other than this and my other post to say about the matter, mostly because I don’t feel developers are responsible for cranking out or owe the audience progress updates.
[quote] It appears that some of this confusion may have come from my post yesterday saying that CSG would not be released yesterday. In the post, I mentioned that an issue had been found that prevented the release. I had made that post in an attempt to provide information as quickly as possible and to keep the community informed about the current status of the release as I knew it. Unfortunately, I didn’t have the details of what the issue was, I didn’t know the root cause of the issue and I didn’t know when it could be resolved. The intention of the post was merely to let everyone know that it would not be that day and to help set expectations correctly.
It seems, though, that my statement was taken as an empty excuse and as an attempt to conceal what was happening. As a result, people became upset and started making accusations. I can only speak for myself, but I know I was left questioning whether I should have mentioned anything without knowing all of the information about why and when the feature would be released. So I am left with the question, should we release information as soon as possible, knowing it isn’t complete, or should we wait until we have a more complete picture even though it will take longer? [/quote]
Wait until you have a more complete picture, kind of a waste of time to update small things anywho
I personally find transparency very important. So ideally, I’d like information as quickly as possible. I also try to be as transparent as possible with my users.
Sometimes there’s missing information, even to the developers. While it would be nice to have that information, if it’s not available, I’d at least like to know that there’s a problem/delay/the feature was abandoned. Because if I know that, I can plan ahead. Perhaps I was waiting for a release so I could update my game. If I know things aren’t going according to plan in time, I can compensate for it.
If I don’t know, I’ll be waiting to make my update. Maybe I’ve already announced my update, and will have people screaming at me if I don’t make it.
I’d like to thank CodeWriter for making his post, and putting up with the massive amount of flak he’s received for it. That information was very useful to a lot of people, including myself. Even if we’re not happy about the delay.
So please do give us information as soon as you have it.