So the Demons Of Samarlogh are a special encounter, the one the "delirious hunter" spoke of. I actually saw them walking along the western edge of the map and made a straight path straight to them. Unfortunately, I was intercepted by a couple different enemies (firenewts and batiri) and the demons of samarlogh were gone before I could get to them. I've read that once they are gone, they are gone for good. I am admittedly something of a completionist so I wanted to know if there is a way to spawn them from the console. I've heard about things like,
dm_spawncreature <Demons of Samarlogh>
rs ga_create_obj("C", "Demons of Samarlogh")
But these do not work (and yes, I do type DebugMode 1 prior to trying this). Is there a way to manually spawn these demons or is it possible that they could come back again?
Can I Spawn Demons Of Samarlogh By Console?
Débuté par
jlwelch
, juin 02 2011 02:17
#1
Posté 02 juin 2011 - 02:17
#2
Posté 02 juin 2011 - 01:27
The Special Encounters in SoZ are set up in a complicated fashion. I was a bit choked myself when One of Many proceeded to eat my party and then didn't come back for a second match! So I did a bit of poking and eventually found this in 'globals.xml':
Supposedly that's the Demons. Short of figuring out how to spawn them manually ... try running from the console (in DebugMode)
rs ga_global_int("g00_ac_fiendish_spider_FIRED", "0")
this should allow them to respawn in the proper terrain ..
g00_ac_fiendish_spider_FIRED 1
Supposedly that's the Demons. Short of figuring out how to spawn them manually ... try running from the console (in DebugMode)
rs ga_global_int("g00_ac_fiendish_spider_FIRED", "0")
this should allow them to respawn in the proper terrain ..
Modifié par kevL, 02 juin 2011 - 01:28 .
#3
Posté 02 juin 2011 - 07:53
I'm not so sure about that command. I used it, and it said the script executed successfully, but the demons never spawned. I figured it just required patience, but then I wanted to see if the script did anything so I typed in things like,
rs ga_global_int("g00_ac_penus_FIRED," "0")
rs ga_global_int("g00_ac_demons_of_samarlogh_FIRED," "0")
and so on, and it kept saying it executed successfully, even though it didn't do anything. I'm not sure that command even has a function really. Still, I very much appreciate your attempt to help me out. I really do.
rs ga_global_int("g00_ac_penus_FIRED," "0")
rs ga_global_int("g00_ac_demons_of_samarlogh_FIRED," "0")
and so on, and it kept saying it executed successfully, even though it didn't do anything. I'm not sure that command even has a function really. Still, I very much appreciate your attempt to help me out. I really do.
Modifié par jlwelch, 02 juin 2011 - 07:54 .
#4
Posté 03 juin 2011 - 12:26
The problem is little more complex. In addition to globals.xml, global variables are also stored in your character sheet (playerlist.ifo) under VarTable. While you can edit it with GFFEditor, I haven't found a good way to search that.
I managed to spawn OneOfMany once in a game where he hadn't shown up (and I was through waiting for him) by editing the proper OM encounter 2da so he was the only possible encounter. You might be able to do this with the Demons, but you probably need to change that variable - OR change the encounter itself so it's not one-shot. In any case, I raised their time on map in the 2da so they don't expire so fast.
I managed to spawn OneOfMany once in a game where he hadn't shown up (and I was through waiting for him) by editing the proper OM encounter 2da so he was the only possible encounter. You might be able to do this with the Demons, but you probably need to change that variable - OR change the encounter itself so it's not one-shot. In any case, I raised their time on map in the 2da so they don't expire so fast.
Modifié par I_Raps, 03 juin 2011 - 12:35 .
#5
Posté 03 juin 2011 - 03:43
So I think I owe KevL an apology, I used his console command and over the next several hours I saw the demons of samarlogh several more times. Each time, they got away from me almost immediately. I went into the 2DA files for regular encounters in Samarach and special encounters and discovered something very interesting. Among other variables, all encounters have a variable "nLifespan" which basically determines how long the creature will remain until they despawn. For regular encounters the number is usually 60 but with all the special encounters, the number is -1. I believe they programmed it so that the special encounters like delirious hunter and OneOfMany would remain there forever once spawned (until interacted with). However, I suspect this backfired with the mobile special encounters. I read in other forums that there is a chicken related special encounter on the sword coast that is the same way.
I went into the appropriate 2DA file and changed the nLifespan value for fiendish spider to 60, used kevL's command, and waited for them to spawn again. It worked, they didn't despawn right away. I honestly believe the developers screwed up with the nLifetime thing for mobile special encounters. I don't honestly believe it was meant to be that way.
I went into the appropriate 2DA file and changed the nLifespan value for fiendish spider to 60, used kevL's command, and waited for them to spawn again. It worked, they didn't despawn right away. I honestly believe the developers screwed up with the nLifetime thing for mobile special encounters. I don't honestly believe it was meant to be that way.
#6
Posté 03 juin 2011 - 03:46
Also, there is a DC of about 30 or so with the demons of samarlogh (according to 2DA file) that you have to make with spot/listen in order to detect them. I don't think they are a rare spawn, I just had to walk around as my rogue with detect mode on to find him.
#7
Posté 03 juin 2011 - 03:48
np jl
to make up fer it, i'm gonna use yer fix for nLifespan
c'est le SoZ
to make up fer it, i'm gonna use yer fix for nLifespan
c'est le SoZ
#8
Posté 03 juin 2011 - 04:49
ps. I_Raps,
i think those are localInts in VarTable; tried cross-referencing w/ globals and it was no go.
i think those are localInts in VarTable; tried cross-referencing w/ globals and it was no go.





Retour en haut






