My "Unarmed" Is Missing

Zaxx · #1 (**permalink**) 08-19-2007, 10:55 AM

Hi all,

I'm revisiting this game after it collecting dust on my shelf, largely because I read about Wesp5's patch making it more playable than when I first got it. However, 15 minutes into my renewed interest in the game I found a potential bug, and I don't know if it was introduced by the patch (which I admittedly may or may not have applied 100% correctly - and I am using the new 4.0 version) or if it's a known issue.

I started a female Malkavian with the Ninja history. I played through the tutorial and got to the part where I snuck past the Sabbat guard. When Jack had me go kill the guard, I found that I had no fists/unarmed "weapon" to attack with. As in, I couldn't "equip" my fists. What was even stranger was that the guard never attacked me - I could walk right up to him and nothing happened.

I ended up dispatching him with a stealth kill and getting the tire iron. That is now the ONLY weapon (again, no fists) that I can select. I tried using the console access to add item_w_unarmed, but that didn't seem to work. Then I tried starting the same character over and skipping the tutorial altogether...and crashed to desktop.

So, ultimately, I'd like to play my character, but I'd also kinda like to have...hands...

Anyone have any thoughts, or could direct me to a post I may have missed in my searches? Thanks much!

Zaxx · #2 (**permalink**) 08-19-2007, 12:24 PM

Just found an item_w_fists in the list that I overlooked before, and that did it.

Tessera · #3 (**permalink**) 08-19-2007, 07:07 PM

Fixed in True VTMB Patch verion 4.04AT.

TRUE VTMB PATCH 4.04AT -- OFFICIAL THREAD

Wesp5 · #4 (**permalink**) 08-20-2007, 01:32 AM

Quote:

Originally Posted by Tessera

Fixed in True VTMB Patch verion 4.04AT.

That error is a well known random bug which I don't think is easily fixable and it's not mentioned in the readme of your patch. So if this is not just an attempt to advertise the latter, please explain how you solved that issue!

Tessera · #5 (**permalink**) 08-20-2007, 02:51 AM

Quote:

Originally Posted by Wesp5

That error is a well known random bug which I don't think is easily fixable and it's not mentioned in the readme of your patch. So if this is not just an attempt to advertise the latter, please explain how you solved that issue!

If memory serves, it was dealt with in a hotfix after the initial release. The patch notes won't include that info, as they were written prior to the hotfix. In fact, we quickly issued three hotfixes to version 4.04AT after its initial release. The patch file currently available on my site and on Gamespot are up-to-date, and include all hotfixes.

Wesp5 · #6 (**permalink**) 08-20-2007, 05:12 AM

Quote:

Originally Posted by Tessera

If memory serves, it was dealt with in a hotfix after the initial release.

Okay, I downloaded your latest patch but I can't find anything connected. Mind to share the info please?

Tessera · #7 (**permalink**) 08-25-2007, 01:09 AM

Quote:

Originally Posted by Wesp5

Okay, I downloaded your latest patch but I can't find anything connected. Mind to share the info please?

Then you are probably not looking in the right place. I believe Acrimonious dealt with this issue all the way back in version 4.02AT, so if you're looking for some mention of it in the 4.04AT patch notes, you won't find it there. This is old news, in other words.

If any of you are playing with True VTMB Patch version 4.04AT, and if you still have any glitches of this type, then please let us know so that we can incorporate a fix into our next release. We haven't had any such reports thus far from 4.04AT users, but we'd still like to hear from anyone who may be experiencing this or any other unusual behavior.

You can report any and all bugs, or any other anomalies in the official "preview" thread for upcoming True VTMB Patch 4.05AT. That thread can be found at the following link:

WORK STARTED ON NEXT RELEASE - 4.05

Thanks in advance and we look forward to hearing from all of you.

Wesp5 · #8 (**permalink**) 08-25-2007, 11:45 AM

Quote:

Originally Posted by Tessera

Then you are probably not looking in the right place. I believe Acrimonious dealt with this issue all the way back in version 4.02AT, so if you're looking for some mention of it in the 4.04AT patch notes, you won't find it there. This is old news, in other words.

Hmmm, 4.02AT was based on my patch and 4.04AT was started from scratch so if you fixed something there, it should have ended up in the readme. Also doing intermediate hot-fixes without mentioning them seems not right to me.