Well I imagine not much has changed in the bigger picture of things since they used the tools to make the game. What they've been working on since then has likely been bug fixes, packaging improvements, and of course steam workshop integration.

that is stupid, which is why i didn't do that. it was more of an observation that particualr page was finished at the start of december. I have no comment as to what that means; i'll let other people argue about that.

EDIT:
@Alexander
derp! that's where i got that quote from! i facepalmed so hard my forehead turned into a backhead. i thought i was going crazy seeing posts that didn't exist.

Imagine how much hullabaloo there would be if Bethesda decided to do a real viral marketing campaign? (Off topic: chrome says that hullabaloo is a word.)

You can't message employees, so my only option is moderators and admins. I think just one good shot towards Gstaff is our best bet. I'm writing it now. Hopefully you can all back me up in this, and we can hopefully get this thing released tomorrow.

It is, and you used it correctly!
http://dictionary.reference.com/browse/hullabaloo

anyone else notice that the script window is in fact notepad++ and that the language is very similar to that of Java

hmm, the wiki compares it to ruby and python

looks like python and java to me

It's not like they're sitting on it and waiting for the best time - they're still ironing out bugs and getting it prepped. Asking, no matter how nicely, isn't going to help. I'd save myself the work.

(Also, I've never had trouble messaging the devs )

Good. The scripting language in TES games was always pretty close to python or Java, but it'll be nice to have an actual proper script editor in the CK this time around.

But someone there has to be able to say, "You know what, release it. We will patch out the bugs afterward." And I think that frankly at this point we would all rather just have it, bugs or not.

I sent him the message. It's not the best letter ever, but with any luck it may sway something. He has no doubt gone home for the night, so I shall see how he replies in the morning.

So, if enough people ask, you'll release your mod before it's done? I suppose it doesn't hurt anything, but I doubt that it'll do anything either.

post patching has never really been done for the past mod tools.....I wouldnt want to risk it.

You do realize that by the time your message gets to him, has a chance to circulate through the office to the right person, and finally be acted upon.... it'll already be next week, right?

Don't encourage them to redo the UI. I'd much rather have a Windows 2000 interface, over a Skyrim 2011 one. We'll have to use a gamepad.

Well, if they designed the game with it, it should be functional enough to do anything, so long as you don't press the buttons in the wrong order, it won't crash. Good enough for me.

The wait is all about Steam integration. That's all there is to it.

If the only thing that was left was minor bug fixing, and there were no massive issues, yes. Oh and there would also have to be like 500,000 people wating for it. I would certainly release it and then fix the bugs after.

Neither has a beta, SW integration, or any real big signs that they actually care. I'd say this has a pretty good chance of being patched up.

Still worth a try. For all we know he will read it tomorrow morning when he comes into work, read to the devs, and the CK is out by lunch. Of course, that's a super crazy best case scenario, but it's got a higher chance of happening then if I don't write him anything...

I wants my Skyrim Creation Kit my Bethesda Lord!!!

I personally have always liked the CS/CK interface.

Then again, I move stuff around, resize it, and customize it heavily to fit my two monitors.

You realize what people would do if the Wiki was released? Now do you see why they won't release that until the tool is released?

To be honest, I've been against post patching. Everyone is inherently lazy, and what you'll end up with is a piece of software with 15-20 minor bugs. These minor bugs can add up to be severe but they usually always have some sort of (often painstaking) workaround.

If you prompt them about fixing these bugs the answer will be along the lines of "it's only a few minor issues, we're waiting to release it when we need to do X". The results is these small and minor bugs never get fixed.

If it wasn't yet released in the first place there's more of an obligation to fix them. You want to get it done the first time, and get it done right. Else we'll never see a polished copy, so to say. That being said, I'm anticipating limitations across the board. Call me a pessimist but I'd rather be impressed than let down. I'm not sure just what kind of 3rd party software/code is involved that will be legally required to be stripped from the toolset.

What? learn everything ahead of time? have something to keep them busy? discuss something other than the release date? If you mean deface it, it's easy to make a wiki read only temporarily.

Of course I cannot speak for BGS, but I've never had an issue with post patching. In fact, the fact that your bringing that extra polish to your product, for so little work is incredibly motivating and rewarding for me. Of course, this is a big issue if you were to have to say, completely redo a part of it. That would svck. But, again, as long as there aren't any major issues, I don't see why they shouldn't release. As at least for me personally, fixing the smaller issues after release is very easy to do, and I still put as much effort into them as I did the original mod. For all three of my released mods, I do not have a single reported bug that I haven't fixed. (Not counting ones that were engine related that I cannot fix) As people report things I wrote them somewhere, then when I had the time I would dive in and get fixin'. I repeated this until bugs were no longer reported. Of course, this may also be different for them as employees of a company, as they may not have the 'infinite' freetime that I had to do so, and bug reports are far less direct and clear.

We've waited for a long time now for the CK. People want any info they can get =P

Yes but it's a different story when you have a passion for modding and your own personal projects vs paying someone to do it for you. Besides this is all pure speculation. I'd bet my money that the CK is and has been for a while deemed ready for release. The holdbacks now are likely integration with steam and associated maintenance, again - speculation.

On another note, I've actually wondered about the beta testers last week and before - if you personally were beta testing and experienced say 10 issues ( everything from misspelled words to desired features) would you post them knowing full well that it would delay the kit for the rest of us? To clarify what I mean is that if the beta kit was functional and could do 95% of what the typical modder would require of it to make a mod, would you try to get them to include this and that if it meant delaying it for another week?

Regardless of whether they are being paid to do it or not, I would hope everyone working at BGS would have a passion for what they do....

If I were testing, I would report every single bug or wayward feature I found. I would also, however, let them know if I thought it was in a state where it was more than ready for public release.