And the missing buildings also load perfectly fine in the CK, yet that bug is on the list.

Minor bug: When you duplicate an object and rotate the camera around it will go to a bigger radius, so you have to click or deselect and click on the object again so the camera can rotate properly.

Another bug:
When loading Skyrim.esm, with sLanguage=POLISH, errors appear:


*instead of this, many words appear, each containing a Polish diacritic mark like ?, ?, etc.

Also, CK does not show Polish (I assume that other, non-English too) characters properly, showing, for example, "?elazna strzaaa" istead of "?elazna strza?a". It completely breaks translating mods and working with already translated ones.

True true. And just so it gets noticed (third time's the charm?) I guess it should be there regardless. Oh, one I forgot:

Minor:
If your active file has unsaved changes so that it shows a * after the name in the title bar ie Creation Kit - [My Mod.esp] * going into File->Data will clear the * even if no changes were made.

With all these bugs, there's no way this is the system used to make Skyrim, more and more this feels like a hack n slash affair for general release.


Anyway, minor bug I've encountered with levelled lists. It applies to new or copied lists, and adding the level an item or list is picked. It sorts the list in descending level order (which is odd in itself), then, if you use the preview tool, you'll get nothing appearing unless you test the maximum level in the list.

Once you save, and reload the mod, the list is in ascending order, and the preview works as intended.

http://www.gamesas.com/topic/1346664-topic-info-scripts-non-unique-names/

I'm hoping that Bethesda at least acknowledges some of these major bugs.

The list is getting rather large, which isn't ideal for us. But keep 'em coming

With all these bugs, I wonder how they created the game in the first place. I ran into a problem following this http://www.creationkit.com/Bethesda_Tutorial_Planning_the_Quest. At a later stage when you make an error adding properties for a quest script, the plugin becomes unusuable. Even if you add the properties properly, or create a new script, problems still occur.

EDIT: Thanks to some advice, the Problem's solved by deleting files from the scripts folder (pex & psc files). This cleaned up the first error causing the problem. However, its still a bug if you have to keep doing this each time you make an error with the property editor.

Actually I for one will consider it ideal for us if it gets attention. They aren't going to give attention to what needs addressed if they don't know something needs addressing.