The "correct" tp2 file was lost in TeamBG land and I can't currently fix the link.  Don't worry, things will be coming very soon.

A great big THANK YOU to FW for taking over. The website's been up for a short time, but in the next few days we'll be updating everything as well as the links and all. Stay tuned for that.

Any chance a "short-cut" could be implemented?

I doubt he will.

Nope, I'll never be doing that.  

broadening of quest availability?

Nope, I won't be doing that either.  In an unmodded, Bioware/interplay game, you can only get one stronghold and the quests for that stronghold.  That's how it will be for CtB.
Besides, some of the quests (like the class super-quests) "overlap": the same sequences happen but in a different order or requirements.

primarily with the worldmap,

  

As far as I know, this is the ONLY major hurdle left since we've successfully "weidu'd" areas.  It still remains on my To-Do list, which hasn't really changed much since I lost TeamBG, but hopefully I'll be able to figure something out in the coming weeks or months.

moment later I was flooded by endless mage reinforcements Even if cowleds really had such forces - which is quite unfair, I'd say - where was them few days ago, when I slay one by one all their enforcer groups?

So would it be better if the "endless reinforcements" were some sort of summoned being rather than a Cowl?


I'm actually quite pleased to hear that you found that quest.... it's pretty elusive by design.  As to the city of Hlondeth, there are currently 3 quests available there, with another one packaged up waiting for the website fixes, and another one in the works.

Did you read this?

http://www.spellhold...ckthebodies.htm

and click on the "Features" page?

Again,

Did you read this?

http://www.spellhold...ckthebodies.htm

and click on the "Features" page?

Quest Notes:


    * The "tutorial" area of Candlekeep
          o This is the very first thing you'll notice about Check the Bodies.  It is not an optional quest, and takes quite some time to complete.
          o There are four 'chores' that must be completed each day.  At the end of the day, if you've completed the chores, of course there's a nice reward for you.
          o Once you've finished with the Candlekeep introduction, things will progress back to the normal BG II introduction and you're on your way to becoming a skilled adventurer.

With the help of my original host, here's an update.

(I assume that this applies to most mods as well since TheWizard hosts many of the big ones.)

Hi CB,

A little worried that putting CtB on one server isn't safe enough?
Well, worry no more!  Thanks to the help of Black Wyrm, IEGMC now has a
second server, and it is an exact replica of the original site.  So, now
CtB is hosted conjointly at IEGMC Asia (the original) and IEGMC Europe.
This will help relieve some traffic from IEGMC Asia.

You know the links for IEGMC Asia, now for the IEGMC Europe links:

http://mirror.blackw...B_CoreFiles.exe
http://mirror.blackw...8_GameFiles.exe

There is no rush to update the CtB web site, as I know you have quite a
bit on your plate right now.  Whenever you get around to it is fine.  In
the meantime, I'll continue to spread the word about IEGMC Europe on the
forums.

Bob

Hopefully, I'll be able to update the website soon and get everything back in order.


CB

Again, from the Instructions page:

7)  If you receive an error while installing, open the backup directory of 'checkbod'.  If you have folders in there, delete them.  If you don't have folders in there, make folders named "0", "1", and "2".  That should only be done if you're getting an error installing CtB for the very first time.

The errors regarding those spells are new to me. I know I took them straight from the BGII-ToB patch Spell.IDS, so they should be listed on it. I'll take a look at them though. The only thing that I can say off hand as a possible cause is that:
a) you don't have your game patched
B) you installed smaller weidu mods prior to installing CtB
or
c) I put those spell entries in the list and they aren't parsed correctly.

As to the "parsing errors" regarding .BAM files, don't worry about them. You can't parse .BAMs so weidu gets all twitchy when it tries to parse them. That won't affect the game.

Nope, I never had the chance to change them to .zips before teambg died.  They're .exe's for Windowns.

Finally found one of my old mails I sent to answer this question before we had the forums again.  Here's the process if you don't have the .tp2 that was lost- I don't even have it.  (And hopefully once I can update the website, I'll have the newer .tp2)

Unfortunately, the "correct" .tp2 file has been lost in TeamBG land and I can't get it for you.  What you can do- if you think you can do it- to fix the crash is this:  search the .tp2 file in your BG II directory for the text "COPY_EXISTING ~AR0500.ARE~" and delete from that line to the next "COPY_EXISTING" command then insert the following text at that point.  If you can't do that, there's no current way that I can help you, and I hope that you understand that it's not really my fault, it's just the fact that I didn't expect TeamBG's servers to get hacked.

Here's the Text you need to replace:
-----------------------------------
COPY_EXISTING ~AR0500.ARE~ ~override/AR0500.ARE~
  READ_SHORT ~0x058~ ~#ofActor~
  READ_SHORT ~0x054~ ~actorOff~
  READ_SHORT ~0x05a~ ~#ofTrigg~
  READ_SHORT ~0x05c~ ~triggOff~
  READ_SHORT ~0x064~ ~#ofSpawn~
  READ_SHORT ~0x060~ ~spawnOff~
  READ_SHORT ~0x06c~ ~#ofEntra~
  READ_SHORT ~0x068~ ~entraOff~
  READ_SHORT ~0x074~ ~#ofConta~
  READ_SHORT ~0x070~ ~contaOff~
  READ_SHORT ~0x076~ ~#ofItems~
  READ_SHORT ~0x078~ ~itemsOff~
  READ_SHORT ~0x080~ ~#ofVerti~
  READ_SHORT ~0x07c~ ~vertiOff~
  READ_SHORT ~0x082~ ~#ofAmbia~
  READ_SHORT ~0x084~ ~ambiaOff~
  READ_SHORT ~0x08c~ ~#ofVaria~
  READ_SHORT ~0x088~ ~variaOff~
  READ_SHORT ~0x09c~ ~#ofExplo~
  READ_SHORT ~0x0A0~ ~exploOff~
  READ_SHORT ~0x0A4~ ~#ofDoors~
  READ_SHORT ~0x0A8~ ~doorsOff~
  READ_SHORT ~0x0AC~ ~#ofAnima~
  READ_SHORT ~0x0B0~ ~animaOff~
  READ_SHORT ~0x0B4~ ~#ofTiled~
  READ_SHORT ~0x0B8~ ~tiledOff~
  READ_SHORT ~0x0BC~ ~songsOff~
  READ_SHORT ~0x0C0~ ~restcOff~
  READ_SHORT ~0x0C8~ ~#ofAutom~
  READ_SHORT ~0x0C4~ ~automOff~
  WRITE_SHORT 0x05a (~%#ofTrigg%~ + 1)
  INSERT_BYTES (~%triggOff%~ + ~%#ofTrigg%~ * 196) 196
  WRITE_SHORT 0x060 (~%spawnOff%~ + 196)
  WRITE_SHORT 0x068 (~%entraOff%~ + 196)
  WRITE_SHORT 0x070 (~%contaOff%~ + 196)
  WRITE_SHORT 0x078 (~%itemsOff%~ + 196)
  WRITE_SHORT 0x07c (~%vertiOff%~ + 196)
  WRITE_SHORT 0x084 (~%ambiaOff%~ + 196)
  WRITE_SHORT 0x088 (~%variaOff%~ + 196)
  WRITE_SHORT 0x0A8 (~%doorsOff%~ + 196)
  WRITE_SHORT 0x080 (~%#ofVerti%~ + 5)
  INSERT_BYTES (~%vertiOff%~ + ~%#ofVerti%~ * 4 + 196) 20
  WRITE_SHORT 0x0A0 (~%exploOff%~ + 216)
  WRITE_SHORT 0x0B0 (~%animaOff%~ + 216)
  WRITE_SHORT 0x0B8 (~%tiledOff%~ + 216)
  WRITE_SHORT 0x0BC (~%songsOff%~ + 216)
  WRITE_SHORT 0x0C0 (~%restcOff%~ + 216)
  WRITE_SHORT 0x0C4 (~%automOff%~ + 216)
  WRITE_ASCII (~%triggOff%~ + ~%#ofTrigg%~ * 196) ~CbMaltes~
  WRITE_ASCII (~%triggOff%~ + ~%#ofTrigg%~ * 196 + ~e~
  WRITE_ASCII (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 16) ~~
  WRITE_ASCII (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 24) ~~
  WRITE_SHORT (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 32)  0
  WRITE_SHORT (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 52) 0
  WRITE_ASCII  (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 56) ~~
  WRITE_ASCII (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 64) ~~
  WRITE_LONG (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 96) 01
  WRITE_LONG (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 100) ~-1~
  WRITE_LONG (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 104) 00
  WRITE_LONG (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 106) 00
  WRITE_LONG (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 108) 01
  WRITE_LONG (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 110) 00
  WRITE_LONG (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 112) 1141
  WRITE_LONG (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 114) 3321
  WRITE_ASCII  (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 116) ~~
  WRITE_ASCII  (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 124) ~CBMALMGE~
  WRITE_ASCII  (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 188) ~~
  WRITE_LONG (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 34) 1039
  WRITE_LONG (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 36) 3163
  WRITE_LONG (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 38) 1244
  WRITE_LONG (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 40) 3477
  WRITE_SHORT (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 42) 5
  WRITE_LONG (~%triggOff%~ + ~%#ofTrigg%~ * 196 + 44) ~%#ofVerti%~
  WRITE_SHORT (~%vertiOff%~ + ~%#ofVerti%~ * 4 + 196) 1039
  WRITE_SHORT (~%vertiOff%~ + ~%#ofVerti%~ * 4 + 196 + 2) 3241
  WRITE_SHORT (~%vertiOff%~ + ~%#ofVerti%~ * 4 + 196 + 4) 1116
  WRITE_SHORT (~%vertiOff%~ + ~%#ofVerti%~ * 4 + 196 + 6) 3477
  WRITE_SHORT (~%vertiOff%~ + ~%#ofVerti%~ * 4 + 196 + 1244
  WRITE_SHORT (~%vertiOff%~ + ~%#ofVerti%~ * 4 + 196 + 10) 3396
  WRITE_SHORT (~%vertiOff%~ + ~%#ofVerti%~ * 4 + 196 + 12) 1156
  WRITE_SHORT (~%vertiOff%~ + ~%#ofVerti%~ * 4 + 196 + 14) 3163
  WRITE_SHORT (~%vertiOff%~ + ~%#ofVerti%~ * 4 + 196 + 16) 1039
  WRITE_SHORT (~%vertiOff%~ + ~%#ofVerti%~ * 4 + 196 + 18) 3241
----------------------------------------------------


After you do that, I strongly suggest you not use your save game as that may also cause problems because of the way the game works.

CB

See my post in the "CtB doesn't install" topic regarding the .tp2 file- it's the cause of the Bridge Crash.

Does anybody know if the big CB is nearly done yet?

First, that's MISTER Big CB to you  

Second, yes, Big CB is done.  v150 and the website updates sits quietly on my HD.  All we need is someway for me to FTP them to FW.

The entries from CtB's *copied* SPELL.IDS which is a Bioware/Black Isle patch 26498 file:

2325 WIZARD_MELF_METEOR
2326 WIZARD_TRUE_DISPEL_MAGIC
2401 WIZARD_CONFUSION

and

1716 CLERIC_SPACE_WARP

The procedure Weidu uses to update the SPELL.IDS file for CtB:

APPEND ~Spell.IDS~
~3510 CB_ENCHANT_SWORD
3511 CB_ENCHANT_DAGGER
3512 CB_ENCHANT_AXE
3513 CB_ENCHANT_HALBERD
2140 WIZARD_EAGLES_SPLENDOR
2240 WIZARD_DECASTAVE
2241 WIZARD_CATS_GRACE
2440 WIZARD_MORDENKAINENS_FORCE_MISSILES
2540 WIZARD_BALL_LIGHTNING
2541 WIZARD_LUTZAENS_FREQUENT_JAUNT
2640 WIZARD_DARTS_OF_BONE
2641 WIZARD_ANTIMAGIC_FIELD
2642 WIZARD_LICH_TOUCH
2643 WIZARD_TROLLISH_FORTITUDE
2840 WIZARD_IRON_BODY
2060 WIZARD_HAKESHAR_EFFECTS_5
2061 WIZARD_HAKESHAR_EFFECTS_7
2062 WIZARD_HAKESHAR_EFFECTS_9
2063 WIZARD_COWLED_VD
3514 WIZARD_ADVANCED_ALCHEMY
3515 CB_ADV_ENCHANT_SWORD
3516 CB_ADV_ENCHANT_DAGGER
3517 CB_ADV_ENCHANT_AXE
3518 CB_ADV_ENCHANT_HALBERD
2360 CB_ELMINSTERS_LIGHTNING
2841 CB_WIZARD_MIND_BLANK~
END

which also appear in TBP's SPELL.IDS as their own entries, so if the BP is installed, CTB doesn't duplicate entries.

Nowhere in the BP's SPELL.IDS file can I find CLERIC_SPACE_WARP but there is

1716 CLERIC_ANIMATE_TREE

which shouldn't affect the compiling of the BAFs.

As to the non-parsing of BAFs in CtB because of this, I don't know. But like I've always said, it's best to install BGII-ToB, patch, TBP, patch, CTB, *then* any smaller mods as it'll cut down on the potential for errors.

Yeah, apparently I did do more quests for mages than any other class.  I don't think I had planned it as such when building, but it just worked out that way.  In fact, I don't even think I've every truly played any of the IE games with a single classed mage, so not sure why I would do it like that.  Regardless, I think the quests as a mage are pretty cool, so like the others suggest, do a run through if you'd like with a mage.

2 Questions,

1) what new changes?

2) you will keep us informed when it is available for download eh

From Led Zepplin's Kashmir:

SIT AND WAIT AND ALL WILL BE REVEALED....

Answers:  

1) Not a whole lot: dialog revisions, area fixes, installation fixes, etc, and a bigger surprise for dungeon crawlers.

2) No.  I will keep it a secret forever.

but I did review my own scripts and I wasn't able to find one of the codes, so I'll go back through it and play test it again.

Like I said, I did go back through all the codes and I must apologize. Seems when I redid the weidu'ing code to make the original areas "weidu'ified", I forgot to add in the creature for one of the areas. Sorry, and I did redo it for the upcoming build.

If you are playing the game version 148, anytime you're in the government building---
ONLY IN THE GOVERNMENT BUILDING WHERE YOU CAN FIND BYLANNA!!!!---- use your console and create the creature "CBCWLWRY". That's the one that you'll need to talk with for the quest. If you've done the planer sphere quests and you talk to him, you'll get the quest. If anyone hasn't done the sphere quests yet, you can still talk with him- but the quest won't 'activate' until you do the sphere.

Ok folks: I've uploaded the next version and it'll be on the public server by the end of the weekend. Unfortuanately, we're still having some issues with updating the website. The current version- v_148_GameFiles - has been 'restricted' on the public server until the new download is available, so you won't find it there. Sit tight for the next one, and you'll get the links as soon as we can update the website.

All my best
CB

Update:

The website is now current- Thanks to Hlid and all his hard work helping explain it to me!- but the actual file hasn't been cloned to the public server yet. Keep trying!

...

Crimy.... that's not good. Checking and shooting. Standby.

Yes, yes... seems that indeed the file that is/was on the public server was corrupted. I'm uploading it again for TheWizard- the file should be 75mb- and at the moment we're 73% of the way through the upload. Bob's waiting patiently by his computer for the upload to be complete, and once he's got it, he'll clone it to the pubic server and I'll "activate" the website links again. Hopefully, we'll be done within the next two hours or so.

And I've reactivated the links on the website. Please proceed to

http://ctb.spellholdstudios.net/

in an orderly fashion.

Thank ye Hlid.

That error is repeated on line 7999, so do the same there. Sorry!

Ok, first things first:

How to open a .tp2 file:

I'm going from memory here, but if you click on a file Windows doesn't know how to open, it asks you if you want to pick it from a list. Do so, and choose Wordpad- or any text editor (I use MED)- and if you want, you can click the button that says "always use this program to open this kind of file". A .tp2 file is a simple text document, readable in any text editor like Microsoft Word, Notepad, StarOffice, MED, or even as a last resort, your internet browser.

Second, please be sure to add in those Tildes:

in the Setup-CheckTheBodies v150.tp2 file, add a tilde at the very end of line 3002 and line 7999 (MED automatically numbers the lines, so it's easily spotted) or search for the text

~override/CB3661.ARE

and make it read

~override/CB3661.ARE~

Third, let's keep the .tp2 open and search for the text

@6610118

.

It's at line 2708. Now, just change that to

@661018

--- as you can see, there's an extra 1 in the tp2 that shouldn't be. Sorry.

Hopefully, that'll take care of it. I'm not sure what happened, but I know that I got those same errors during my own test install, and I am sure I changed them, but perhaps I forgot to use the 'updated' file in my build or I forgot to save the changes.

I've also posted the updated .tp2 on the website, so if you don't think you can do the process I just described, grab it off there- probably take around 20seconds with a 56kmodem.

CB