"Offering choice" - that is a nice euphemism for being held ransom by crappy grindy game mechanics.
This game just isn't worth playing at the moment
- Thread starter +Mikie
- Start date
"Offering choice" - that is a nice euphemism for being held ransom by crappy grindy game mechanics.
THat's an interesting thought and conundrum. I guess it depends on the nature of the higer ups at FD, who for the time being, I do not paint as money grabbers. At all. So one has cause for hope.
WTH is wrong with this person? ^ Not enough facepalm in all the galaxy for a statement like this.
Last edited:
didnt see enough rebuys, asks for being KOS?
facepalm yourself.
The higher ups all sold their shares, even DB doesn't control his own compant anymore iirc as he only owns 35% The other two up and sold most what they had.
didnt see enough rebuys, asks for being KOS?
Look at the people who agree with you and those who agree with me, and think about their forum histories and contributions. I got a lot of rep for that first post today.
TBH... i would like to highfive you... with a chair... thats on fire
for suggesting such a thing hehehethats not something i care about, forumrep..Look at the people who agree with you and those who agree with me, and think about their forum histories and contributions. I got a lot of rep for that first post today.
TBH... i would like to highfive you... with a chair... thats on fire
thats not something i care about, forumrep..
I know a way we can work this out. Corvettes at dawn!
Last edited by a moderator:
Look at the people who agree with you and those who agree with me, and think about their forum histories and contributions. I got a lot of rep for that first post today.
Proof positive why companies should NOT be allowed to use predatory online transactions.
its gonna be a Truxican standoff!!
Just not tonight
my mate has gifted me a game so im forced to play that heheI dunno, that's a stretch, maybe though.
I certainly not in favor of the predatory type myself, more like I approve of blizzard turning a blind eye. its gonna be a Truxican standoff!!
Just not tonight
Lololoolollol. Ok mate.
Coding is difficult. As time moves on, more code is added. This new code interacts with the older code. You find a bug in the old or the new code, and....
I was a firmware engineer for over 30 years, and never found it 'that' difficult.
If the core design is sound, and the coder truly understands what they are doing, then feature creep (introducing new or old bugs with a fix) is manageable.
None of my engineers (or myself when I was coding) was allowed to input a change in the firmware until they fully understood what the change impacted, and had done extensive testing to prove that the fix truly is that and won't bring the house down. And then prove it to me. Doing that with a few million lines of C code takes an above average person/engineer.
And then we'd attend a meeting with the software programmers who talk about their great Agile methodology,and just 'refactoring to functionality' when the software breaks and we'd get a good laugh. And I never ever considered hiring anyone from that group. Actually, I had to hire a few C++ software types so we could design/write our own test software as I had grown tired of waiting for anything useful to come out of that group.
The observed behavior of this game software reminds me of the efforts of that test software group.
If the core design is sound, and the coder truly understands what they are doing, then feature creep (introducing new or old bugs with a fix) is manageable.
None of my engineers (or myself when I was coding) was allowed to input a change in the firmware until they fully understood what the change impacted, and had done extensive testing to prove that the fix truly is that and won't bring the house down. And then prove it to me. Doing that with a few million lines of C code takes an above average person/engineer.
And then we'd attend a meeting with the software programmers who talk about their great Agile methodology,and just 'refactoring to functionality' when the software breaks and we'd get a good laugh. And I never ever considered hiring anyone from that group. Actually, I had to hire a few C++ software types so we could design/write our own test software as I had grown tired of waiting for anything useful to come out of that group.
The observed behavior of this game software reminds me of the efforts of that test software group.
I was a firmware engineer for over 30 years, and never found it 'that' difficult.
If the core design is sound, and the coder truly understands what they are doing, then feature creep (introducing new or old bugs with a fix) is manageable.
None of my engineers (or myself when I was coding) was allowed to input a change in the firmware until they fully understood what the change impacted, and had done extensive testing to prove that the fix truly is that and won't bring the house down. And then prove it to me. Doing that with a few million lines of C code takes an above average person/engineer.
And then we'd attend a meeting with the software programmers who talk about their great Agile methodology,and just 'refactoring to functionality' when the software breaks and we'd get a good laugh. And I never ever considered hiring anyone from that group. Actually, I had to hire a few C++ software types so we could design/write our own test software as I had grown tired of waiting for anything useful to come out of that group.
The observed behavior of this game software reminds me of the efforts of that test software group.
Seems to me to be a rudderless ship with trainee sailors..
It's not a long way to travel. It's a tedious way to travel. Assuming your ship can reach an average of 20 LY, you're going to spend the next 10 minutes doing the rote process of jump > avoid star > align > charge > repeat. When you consider the fact we've been doing the same rote process since the game's release, it's easy to see how a 100 LY trip, which isn't really all that long on paper, becomes an arduous exercise in tedium.
I was a firmware engineer for over 30 years, and never found it 'that' difficult.
If the core design is sound, and the coder truly understands what they are doing, then feature creep (introducing new or old bugs with a fix) is manageable.
None of my engineers (or myself when I was coding) was allowed to input a change in the firmware until they fully understood what the change impacted, and had done extensive testing to prove that the fix truly is that and won't bring the house down. And then prove it to me. Doing that with a few million lines of C code takes an above average person/engineer.
And then we'd attend a meeting with the software programmers who talk about their great Agile methodology,and just 'refactoring to functionality' when the software breaks and we'd get a good laugh. And I never ever considered hiring anyone from that group. Actually, I had to hire a few C++ software types so we could design/write our own test software as I had grown tired of waiting for anything useful to come out of that group.
The observed behavior of this game software reminds me of the efforts of that test software group.
What if the core design is not sound? Just saying.