Axebeard on 15/8/2016 at 02:20
Pretty simple: I have a book in my FM, and it defaults to a pbook(?) Bookart. I changed it to parch2, Alt+G, looks fine. Save the mission, go back later, it reverts back to pbook. Any ideas?
Steele on 15/8/2016 at 03:54
My only thought: When you edit the Book Art property, are you expanding its existing properties until you find it, or are you adding the property from the pop-up list?
If it's the former, Domed/thief is probably overriding it with the default, since you were trying to edit the hierarchy item instead of the individual item. If it's the later... well, I have no idea, sorry =/
LarryG on 15/8/2016 at 06:50
It depends on whether you mean that the change is gone after you reload DromEd and the mission or not. If so, I'm betting two things: 1) you aren't saving a cow file, but a gam and mis file instead, and 2) that you made the change to the archetype but only saved the mis file.
Axebeard on 15/8/2016 at 07:19
Yes, I've only been saving the Mission file. What does the COW file even contain?
Unna Oertdottir on 15/8/2016 at 08:10
cow=mis+gam (mission and gamesys)
Axebeard on 15/8/2016 at 09:10
I assumed that was one of those things I wouldn't have to worry about until release time.
Unna Oertdottir on 15/8/2016 at 10:07
You should always save as cow to be sure you don't lose anything accidentally.
Yandros on 15/8/2016 at 12:17
You're changing it on the archetype and not your concrete book object. Changes to archetypes (negative object numbers) are stored in the gamesys (.gam file). Archetypes are like the definition of what an object is, the template basically. Changes to instantiated (concrete) instances of archetypes (positive object numbers), i.e. objects in your mission, are stored in the .mis file. The .cow file is simply the .mis and .gam all in one file. As Unna said, I highly recommend saving as .cow until you go to package up the mission to test through a mission loader, since distributing the mission requires the separate .mis and .gam files.
To do that from a .cow, you follow these steps:
* Save the gamesys with any filename, e.g. example.gam
* Set the mission to point at that .gam file using the command set_gamesys; in the command area enter set_gamesys example.gam
* Save the mission with the right filename based on the mission number you're using, e.g. miss19.mis (this should also be set in the Dark Mission Description)
LarryG on 15/8/2016 at 13:36
Quote Posted by Axebeard
I assumed that was one of those things I wouldn't have to worry about until release time.
You got it backwards. You don't have to worry about mis and gam until release time.
You also shouldn't change the book archetype to specify book art. If you do that, then all your concretes will change to that. You specify book art on the concretes.
If you do change the book art on a concrete, you should also specify a physical model which matches it. Parch2 is really a scroll's book art, and not appropriate to a book. Scrolls are descended from a different archetype in the hierarchy (Household>Scroll) than books and use a different standard script (scroll vs. StdBook). They can be picked up and carried about. Books have to be read in-place. That's a function of the script they use. This is a Thief convention that you don't want to mess with unless you have a very good reason. Players have been trained to it.
Axebeard on 15/8/2016 at 20:50
Okay, so save the COW file until release time then?
The reason I switched to parchment is because I have a thief's journal as a readable, but the default book art (and all of the bookart from what I can tell) are like guilded fancy-ass pages. Doesn't make any sense.
And I'm working in Thief 2, which I have some questions about for another thread maybe, but I guess I can ask here:
What's the difference between Thief 2 and Thief Gold as far as the Dromed-ing goes? I hate the Victorian stuff from T2, and I also hate the robots and Mechanists, so should I just stick to Thief Gold? I had to use some Thief 1 textures in my map anyway. And I'm assuming NewDark makes them technically the same, right?