Just to recap, all the bugs I and all others in many skins games have experienced since the last maintenance:
* Camera views messed up - sometimes you can get your green / approach view working, sometimes not. Sometimes there is a camera icon for a green overview, sometimes not. Even when the green overview camera is there, often you cannot click on it.
* Game seems really jerky or choppy, both the game visuals and the meter. No amount of flash and browser cache clearing helps at all. Game is now the most difficult in terms of choppy meter that it has been for me in about a year or more.
* Flag disappearing - the flag just disappears, typically only for approach-to-green shots. Happened to all 4 players today in a skins game at Merion. You now need to remember where your aim marker is at the start of any approach shot, as it is impossible to now see the hole with no flag from any distance.
* Regular game crashes / flash crashes. I rarely or almost never had in-game crashes. Now, today only, the game window has crashed 3 times, twice in one game, with either a blue screen of nothing, or a white window with an exclamation box.
* Chat window loses focus on every shot / refresh. The game now does not maintain itself, but after every shot from every player, if you are typing in the chat window it gets stopped and loses focus. Not a huge problem, but annoying when you, and others have a lot of chat that gets cut off mid sentence.
* As well, the flashing "play now" button in any wgt normal window still there. I don't usually get it for the first wgt window that opens, but every subsequent window is still doing it an has been doing it for many months now.
Look, no offense, but if you are hiring student programmers to "update" the game, why not employ real programmers from the web to fix your code remotely? The simple fact is as I see it, the fact that when changes are made, more bugs are introduced, tells me quite clearly that your programmers, student or whatever, do not have the proper training on how to modularize code effectively. Proper modular code means that when something is changed in one part of the codebase, it does not affect other parts of the code. So if you introduce new changes, it does not break existing code, at least it won't if your code is properly modularized. So in OOP parlance, we were taught over and over again in first year C++ object oriented programming: "Private data, public functions or methods". That means that any existing code does one thing, does it well, and can only have its data changed through a public method, not any other way. And with a properly built class instance this way, the public method only calls and can change static or static local variables. This way, if you bring in new features into the Wgt game, the worst it can do is break the new features, the existing code can not have its data erroneously changed as it's member data is private, and only accessible through public method calls.