On tweaks vs. fixes, this is obviously a hard topic and needs much discussion. I had similar problems with
BGT-
WeiDU so I am familiar with the difficulty of these logistics. On to the specific features discussed:
Add BG2 kits to joinable NPCs in BG1: Horribly, a tweak...no way this is a fix. However, there are actually existing problems with the stats of the joinable NPCs in original
BG1. Why does Quayle have a flail and proficiency in flails when
AD&D rules decree that he cannot use it because he has <13 STR? Do you "fix" this, or do you "tweak" it?
Worldmap update: I think game engine limitations say that the
BG1 map should merge with the
SoA map ONLY IF a transition is present. I introduce the idea of a 'faithful' conversion here (and how 'faithful' a conversion can be is also an important discussion point). In order to be 'faithful', the
SoA map would be replaced entirely by the
BG1 map. However, since I do not agree that you should have a separate
BG2 install to play the
SoA portion of the game (which TuTu forces you to do), I don't agree with overwriting the
SoA map with the
BG1 one.
Map notes: Really, this is a tweak. It is very simple to add using the ADD_MAP_NOTE function in
WeiDU. This is not a fix because it isn't like
BG1 map notes are broken when you use the areas in
SoA. It is because map notes didn't exist in that game. So, tweak for me.
Journal entries and titles: This is a fix. Having direct
BG1 journal entries in
SoA produces spacing errors in the journal. This is a problem, and thus needs fixing in my opinion. Whether you divide the entries into QUEST, DONE QUEST, JOURNAL, INFO, USER, could be considered a tweak, but considering that the only way to do this is to either perform cumbersome and limited hex offset patching of DLG files, or recompiling every single D file with journal entries, I would vote sorting journal entries as a fix, not a tweak.
BG1->BG2 transition: This isn't existing as part of any game of the
BG Trilogy. Tweak.
Summons rebalancing and BG1-style summons,
Walking speed,
Hooded avatars: This depends on how 'traditional' one should get. It may be more faithful to include these in the core installation, but I do not believe that this is practical. As I do not support the notion of having two installs - one to play the
BGT/TuTu merger, and one to play
SoA/
ToB - it really is stupid to make a mod to 'restore'
BG2-style summons, walking speed, and hooded avatars when it was originally overwritten in the first place. Although you can make these components optional, there is, as was mentioned, the possibility of 'cross-contaminating' into the
SoA/
ToB portion of the game. One way around this could be to patch only
BG1 resources, therefore actually making use of the prefix, but I don't this would work for the summons or the avatars. On the 'faithful' conversion topic, we also should question what is meant by 'Play
BG1 using the
BG2 engine'. I particularly point to the word USING. If the
BG2 engine has faster (or slower, whatever it is) walking speeds by default, is changing the speed back to the
BG1 engine style really USING the
BG2 engine? Is changing the summons to
BG1 style USING the
BG2 engine? Where do we draw the line between what is
BG2 ENGINE and what is not
BG2 ENGINE?
On optional components, and I quote Borsook,
"I'd say that as long as the player is asked whether or not to install something it doesn't really matter where it is included." I don't agree that this is the issue. I believe that the problem is making sure that the core installation is distributed as updates as few times as possible. This ensures that users don't have to re-install from scratch when a new version of the core component is released
because an optional component was updated. Sure, the core component can always have bugs and needs fixing up, but including optional extras increases the likelihood that the entire core package be re-distributed, which forces people to re-install. I'd rather the optional components be separate so that no installation from scratch is required. Although you can't really go that far, I liken this to forcing someone to re-install
BG2 because you released a new version of
BG2 (not patch-wise, but entire game-wise).
On renaming resources, I think that something like a '_' prefix COULD be added to the resource names to make it easy to distinguish
BG1 resources from
SoA resources, but I really do not like the way how resources like MTOWBASN, FTOWBASN, are handled (i.e. crazy things like _28_OWBA, or whatever it is). It simply isn't clear what resources they were originally without comparing the CRE colours! Some other non-CRE resources follow the same line of naming which is awful. For areas, I think the
BGT-
WeiDU naming system sucks, and the FW#### is the way to go to preserve the
BG1 numbers. Similary, the area scripts should correspondingly be named FW####.BCS and not _AR####.BCS.
On spawns, TuTu spawns are preferable due to the levelled nature.
BGT-
WeiDU spawns work (I don't know what people mean by 'broken') but statically spawns CREs independent of the level of the player. Therefore, I would support removal of spawn points and their replacement by info/trigger/exit points that basically work like traps to spawn levelled creatures. On the comment that spawns should be totally be removed, I think that is a tweak and could be quite easily done.
On ToB and TotSC requirements, I think it would be more complete to ensure that
ToB and
TotSC are not required. Having said that, I do agree that not having
TotSC could cause a number of installation hassles and thus may be too much of a burden not to include. At the same time, I hope that fixes can avoid using
ToB updates to the engine (which I am sure it can), which I think is no problem. I think that
TotSC/
ToB requirements seem more important to other modifications (Mulgore and Xavia NPCs is all that I can think of at the moment, but the 'Mequel' project may make use of XNEWAREA.2DA that is only available in a
ToB installation) than a base conversion like the
BGT/TuTu merger. Thus, my current standpoint is to have at least
TotSC a requirement. It might be better to start a poll and see what current and potential
BGT and TuTu players have before a further decision be made on this point.
My 16 dollars... B)