Getting the camera to zoom in on a workbench shouldn't be a problem. Simply place a camera over the workbench (not the easiest thing) and use the camera Id and angle tab in the dlg editor. However, placing a camera means making a new entry in area's git- not the best method if your looking for compatibility as other mods would edit this file. For k2 this would be tslrcm, another mod for k1. An idea is that I edit the .git files of these mods with the permission of the authors. For anybody else I can give instructions on how I edited the .git file.

As you are no doubt wondering what mod I am working on, all I can say is that involves a real time workbench (provided everything works out).

Getting the camera to zoom in on a workbench shouldn't be a problem. Simply place a camera over the workbench (not the easiest thing) and use the camera Id and angle tab in the dlg editor. However, placing a camera means making a new entry in area's git- not the best method if your looking for compatibility as other mods would edit this file. For k2 this would be tslrcm, another mod for k1. An idea is that I edit the .git files of these mods with the permission of the authors. For anybody else I can give instructions on how I edited the .git file.

As you are no doubt wondering what mod I am working on, all I can say is that involves a real time workbench (provided everything works out).

If you're willing to wait, I can probably make a program that will unpack a .mod, open the .git file, and allow you to edit it. I could make it make a list of the changes(similar to the changes.ini of TslPatcher) and then re-pack it. I will need time though, since I have no laptop/computer that I can do whatever I want on and am forced to visit my brother and use his.

Yeah. I have a TSL Patcher currently setup to edit the BattleMusic slot of a .GIT file. It changes the original battle music ID to one corresponding with a newly added 2da line. I ran two instances of this TSL Patcher just now and here are the results:

After the first run the battle music was listed as 100 within the .GIT (and Windows showed that the .MOD had been edited recently). After the next run, the battle music listed as 112 and Windows again showed the .MOD had been recently edited.

This means it was extracting the .GIT, editing it to correspond with the .2da, then repacking it.

The truly fallen cannot return to the light. If someone "falls" and "returns," they never really, truly fell.

Yeah. I have a TSL Patcher currently setup to edit the BattleMusic slot of a .GIT file. It changes the original battle music ID to one corresponding with a newly added 2da line. I ran two instances of this TSL Patcher just now and here are the results:

After the first run the battle music was listed as 100 within the .GIT (and Windows showed that the .MOD had been edited recently). After the next run, the battle music listed as 112 and Windows again showed the .MOD had been recently edited.

This means it was extracting the .GIT, editing it to correspond with the .2da, then repacking it.

Well then, no tool needed. And as for Hunter's Run's worry of compatibility, I think he(or she!) doesn't have anything to worry about, now does he/she?

The only problem I can see is when exactly would he/she want the camera to zoom in. If it's whenever the player clicks on it to use it one could just edit the workbench's default dialogue to have a camera showing the workbench in the opening node.

The truly fallen cannot return to the light. If someone "falls" and "returns," they never really, truly fell.

He actually. I created a new dialogue file for the mod. Thanks for telling me about the TSL Patcher. I'll use that. Is there a tutorial on how to edit the git file with the TSL Patcher or is it in the documentation.

He actually. I created a new dialogue file for the mod. Thanks for telling me about the TSL Patcher. I'll use that. Is there a tutorial on how to edit the git file with the TSL Patcher or is it in the documentation.

You can try here for the basics. It talks about .uti and .utc files, but a .git file is still the same format. I would suggest that you have the .git file from each module with a workbench in a folder, and then have your edited versions in a different folder, and for each file just compare the versions between the folders.

Are you using an animated camera or a static camera? Quite frankly animated cameras are much easier to work with and can be either animated or static. Plus, they only require two files in the override (an MDL and an MDX), so it make it more compatible. The only problem with animated cameras is wether you intend to use a script to switch camera shots in the middle of the dialogue node, because you cannot call animated cameras with that function.

The truly fallen cannot return to the light. If someone "falls" and "returns," they never really, truly fell.