24 replies to this topic

[JohnMoonlord]

I've encountered Melicamp the Chicken in the Red Canyons area.

He comes to me and initiates dialog. His exact wordings are:


Melicamp: CLUUUUUUCK!! Bwaaaaaal!!

*I click 'continue'*

Melicamp: Buc-becaw! HEEEEELP-becaw!


Then, dialog ends. I initiate dialog with him again and he justs repeats those 2 lines everytime I do.

So basically, I can't pick him up and go on with the quest. I've encountered this problem before in a previous install, using BWP non-beta.

For this quest, my journal entries show only my encounter with the spooked witness, Kissiq, that saw the chicken first and warned me about it.


Here's the WeiDU file. Nothing in either the Baldur.err or ToBEx.log files.

Attached Files

•  Weidu.log   83.7K   413 downloads

[Dakk]

Random thought, are there possibly any INT/WIS/Class-requirements?

[8people]

Have you killed the wolf nearby?

[JohnMoonlord]

Random thought, are there possibly any INT/WIS/Class-requirements?

None that I know of: of the many times I played through the game, modded or not, these are the only two times I had this issue.

[JohnMoonlord]

Have you killed the wolf nearby?

I killed everything on the map, yes. And I did kill any creatures nearby before meeting Melicamp and turning back, then came back later after clearing the map.

[Eagleheart]

Have you killed the wolf nearby?

I killed everything on the map, yes. And I did kill any creatures nearby before meeting Melicamp and turning back, then came back later after clearing the map.

You have not killed the wolf for whatever reason, maybe it didn't spawn or whatever but what you are getting is what happens if you talk to him before you kill the wolf.

[JohnMoonlord]

Have you killed the wolf nearby?

I killed everything on the map, yes. And I did kill any creatures nearby before meeting Melicamp and turning back, then came back later after clearing the map.

You have not killed the wolf for whatever reason, maybe it didn't spawn or whatever but what you are getting is what happens if you talk to him before you kill the wolf.

I did kill a pack of wolves nearby, where Kissiq stood as well and told me about Melicamp, as well as a few elsewhere. Otherwise, I don't remember any wolf that seemed out of the ordinary.

[Mad Mate]

I did kill a pack of wolves nearby, where Kissiq stood as well and told me about Melicamp, as well as a few elsewhere. Otherwise, I don't remember any wolf that seemed out of the ordinary.

I had same problem in my walk-through of BWP. I don't know why it happened but that wolf didn't spawn. I CLUAconsoled it near Melicamp, killed it and dialog went like it should be...

WOLFCH is the name of Melicamp wolf.

[Cerest]

I also had this problem in my play through... >.<

[JohnMoonlord]

I had same problem in my walk-through of BWP. I don't know why it happened but that wolf didn't spawn. I CLUAconsoled it near Melicamp, killed it and dialog went like it should be...

WOLFCH is the name of Melicamp wolf.

Hmmm... Perhaps something to do with BGSpawn?

Thanks for the tip: I'm off to save a chicken!

[Fouinto]

Hmmm... Perhaps something to do with BGSpawn?

Hi,

I'm currently playing a custom BWP 9.10 with BGSpawn (Of course ! One of the best mods !) and I don't have this problem...

[pacek]

Could it be down to SCS changing wolves' behaviours?

this:
~SETUP-SCS.TP2~ #0 #3110 // More realistic wolves and wild dogsS: v19

They sometimes run away from you.

Edited by pacek, 14 May 2011 - 03:28 AM.

[Fouinto]

Could it be down to SCS changing wolves' behaviours?

It COULD be MANY things... but if you want to know what cause this, you will have to find (with NI) who/what makes this particular wolf appear on the map (the ARE file of the area? the .BCS file of the area ? the BCS file of the chicken ? ...).
And then, change-log the file responsible of this...
And only then, witch component(s) did the trick!

[Mad Mate]

I also think that SCS is culprit because AR9600.ARE file suggests that WOLFCH should spawn near Melicamp, but somehow it disappear. By looking at WOLFCH.CRE file it appears that it uses WOLF.BCS script which has SCS wolf behavior:

Spoiler

IF
GlobalTimerNotExpired("DMWWpanickedwolves","GLOBAL")
!See([ENEMY.HUMANOID])
THEN
RESPONSE #100
EscapeArea()
END

IF
Global("DMWWWolvesHostile","GLOBAL",1)
!Allegiance(Myself,ENEMY)
AreaType(OUTDOOR)
!Detect([PC])
THEN
RESPONSE #100
Enemy()
Continue()
END

IF
Global("DMWWWolvesHostile","GLOBAL",0)
Allegiance(Myself,ENEMY)
AreaType(OUTDOOR)
!Detect([PC])
THEN
RESPONSE #100
ChangeEnemyAlly(Myself,NEUTRAL)
END

IF
Range([PC],5)
!Allegiance(Myself,ENEMY)
!GlobalTimerNotExpired("DMWWcowardlywolves","GLOBAL")
THEN
RESPONSE #200
SetGlobalTimer("DMWWcowardlywolves","GLOBAL",TWO_ROUNDS)
RESPONSE #100
Enemy()
END

IF
!Allegiance(Myself,ENEMY)
GlobalTimerNotExpired("DMWWcowardlywolves","GLOBAL")
Range([PC],20)
THEN
RESPONSE #100
RunAwayFrom([PC],30)
END

IF
!Allegiance(Myself,ENEMY)
!GlobalTimerNotExpired("wolfwander","LOCALS")
OR(2)
!See([0.0.WOLF])
Range([0.0.WOLF],20)
THEN
RESPONSE #100
SetGlobalTimer("wolfwander","LOCALS",ONE_MINUTE)
RandomWalk()
RESPONSE #100
SetGlobalTimer("wolfwander","LOCALS",ONE_MINUTE)
END

IF
Allegiance(Myself,ENEMY)
See([0.0.WOLF])
!Range([0.0.WOLF],20)
THEN
RESPONSE #100
MoveToObject(LastSeenBy(Myself))
END

IF
StateCheck(Myself,STATE_REALLY_DEAD)
!Global("hurtwolf","LOCALS",1)
AreaType(OUTDOOR)
HPPercentLT(Myself,60)
!NumCreatureGT([ENEMY],3)
THEN
RESPONSE #100
SetGlobal("hurtwolf","LOCALS",1)
SetGlobalTimer("DMWWpanickedwolves","GLOBAL",SIX_MINUTES)
RESPONSE #100
SetGlobal("hurtwolf","LOCALS",1)
END

IF
StateCheck(Myself,STATE_REALLY_DEAD)
!Global("deadwolf","LOCALS",1)
AreaType(OUTDOOR)
THEN
RESPONSE #100
SetGlobal("deadwolf","LOCALS",1)
SetGlobalTimer("DMWWpanickedwolves","GLOBAL",SIX_MINUTES)
RESPONSE #100
SetGlobal("deadwolf","LOCALS",1)
END

IF
See(NearestEnemyOf(Myself))
!Race(LastSeenBy(Myself),WOLF)
THEN
RESPONSE #100
AttackReevaluate(NearestEnemyOf(Myself),15)
END

So, if wolf gets panicked it vanishes. I think that's why somebody has wolf, and somebody don't.
Maybe WOLFCH.CRE should be excluded from SCS editing and given separate script...

Edited by Mad Mate, 14 May 2011 - 05:06 AM.

[Fennek]

If this is true, how about posting it in the SCS forum?

[Lollorian]

Maybe WOLFCH.CRE should be excluded from SCS editing and given separate script...

Took the advice and added this code before SCS' wolf.baf is compiled to scs\wolf\wolf.tph:

COPY_EXISTING
   ~%tutu_var%wolfch.cre~ ~override~
           WRITE_ASCIIE 0x258 ~xowolfch~ (<img src='http://www.shsforums.net/public/style_emoticons/<#EMO_DIR#>/cool.gif' class='bbc_emoticon' alt='8)' />
		   
COPY_EXISTING ~%tutu_var%wolf.bcs~ ~override/xowolfch.bcs~

Needs testing in a BGT game though... Just install BGT and SCS (after unpacking this to the SCS folder ) and check in NI whether WOLFCH.cre got XOWOLFCH.bcs as a race script - moreover, go on to check whether the actual script does not contain SCS' timer stuff

Attached Files

•  scs_melicamps_scared_wolf.7z   639bytes   324 downloads

[Lollorian]

You should add quotes

CLUAConsole:CreateCreature("WOLFCH")

... and (this might seem silly but ) make sure you're playing BGI (or BGT or Tutu )