Help me to solve the mystery of time ...
SamuelVarg
Member Posts: 598
Time is a mystery in a programers world. I have yet to decode how the time works in the gaming world of a Forgotten Realms programer.
It's not like Blizzard time when you can double the amount of given time to get a fairly accurate guessing about what they are talking about.
For example: If Blizzard say "It will be out in about one year", the time of the release would happen in about two years from that statement.
In the gaming world of Forgotten Realms everything is "hopefully fairly soon".
This mystery needs to be solved. How does time work for a gaming programer?
It's not like Blizzard time when you can double the amount of given time to get a fairly accurate guessing about what they are talking about.
For example: If Blizzard say "It will be out in about one year", the time of the release would happen in about two years from that statement.
In the gaming world of Forgotten Realms everything is "hopefully fairly soon".
This mystery needs to be solved. How does time work for a gaming programer?
Post edited by LadyRhian on
0
Comments
But if we should name companies I think Overhaul is the correct.
How do we solve the mystery of time in Overhaul?
1) Bugs that existed before, which have yet to be discovered
2) Bugs that were created as a side-effect of a new feature or bug fix
#1 is driven by the size and complexity of the project. BGEE and BG2EE are massive projects, and the IE is a poorly designed, highly complex system. The number of bugs we have fixed is well into the thousands, and clearly more than half of those are fixes for bugs that were in the original game. (actually, a good number of those were "they way things oughta be" enhancements, but that's another debate)
#2 flows from #1 in that there is little if any specification for the game, and the architecture of both the engine and the content lend themselves to a high degree of coupling: global connections and side effects that are relied upon in semi-random places in the code.
Bugs cause schedule uncertainty because a) you can't predict when they will be discovered, b) you can't predict how severe they will be and c) you can't predict how long it will take to fix them. So, we could be ready to ship tomorrow, and find a crash bug today. Now do you fix the bug or ship and fix it later? Choose carefully, because half of your audience will be outraged either way.
Here's the good news: the BGEE engine is getting more stable every day, and BG2EE will be using the same engine. The BG2 content is much better designed than the BG content, in that quests and plot lines are much more self contained and robust than BG. Add to that, most of the development staff for the new content have 5-10+ years of experience developing for the IE.
We are definitely headed in the right direction.
But thanks! :-)