The Letter is up

[charliesheen]

Witty.

I skipped the technicalities and opted for a silly response, but apparently you want to hear them. It would still lock up the simulation thread. Depending on how they decided to write the game, the simulation thread typically spawns numerous threads to handle IO, physics, AI etc simultaneously. The simulation thread then waits for all threads to complete before restarting its loop. If whatever thread combat is running on never completes due to said retarded loop conditions, you're hooped.

Please don't turn this into a programing debate.

Your response is silly too. All the defenders of the SE order seem to be missing one thing. Yes, this isn't some silly homemade app, but this isn't some silly amateur company either. SE is a global developer and publisher with hundreds (probably thousands) of staff on their payroll. No one, especially not me, is saying that it is simple to recode games or any other complex programs for that matter. What we are saying is that for a company of this size to have so much trouble recoding anything in this game, shows a very big weakness in them. Any programmer worth his salt plans ahead for changes. And any programmer worth his salt doesn't have his code in a giant mess with absolutely no documentation or indicators for different parts of code in each module. You all act as though this is just one giant file of code that they need to eyeball to find things. And you all act like when they are debugging code, the tools give them absolutely no indication of what is causing the problems. In that case, maybe the developers at SE really are working from home, with absolutely no professional tools.

Once again, I point to the case of linkshell member count limitations. Something they have said they "cannot change" due to the way it is coded. Are you people just going to sit there and pipe the same drivel about how complicated programming is? My point from pages back is 100% correct - the code was a complete mess from Day 1, end of story.