Aller au contenu

Photo

Druids (as shape changers) in Persistent worlds


  • Veuillez vous connecter pour répondre
4 réponses à ce sujet

#1
Cacodaemon666

Cacodaemon666
  • Members
  • 1 messages
My guess this request will go on deaf ears, but I figure it can't hurt to try.

Druid shpae changers have some flaws specifically when playing on persistant worlds.  The problem has to do with buffs and the auto-save feature that most persistent worlds use. 

The problem that occurs is each time a druid gets into form (any form, bear, dragon, etc) and buffs up...once an autosave kicks in...the autosave pops the druid out of form and then back into form very fast.  This wreaks havoc on many of the buffs the druid casts, making it necessary to rest and rebuff.  It becomes especially troublesome when you are fighting a big boss and the autosave kicks in (removing many of your buffs).

I know Kaedrin has attempted to fix since this with various tweeks, but since this  is deep in the game code, there is only so much he can do.  

I think all persistant works use the autosave and it seems to be set anywhere from 10-15 minutes.

Any possibility that a patch might come out to fix this?  It would really do a lot to make this unique class more enjoyable while playing on persistant worlds.

Modifié par Cacodaemon666, 09 août 2011 - 05:38 .


#2
The Curt Jester

The Curt Jester
  • Members
  • 97 messages
I've never heard of that problem, though it could be because I've never played a shape-shifting druid.   On our PW, Sea of Dragons , we use a custom database with our own autosave feature, so it shouldn't cause any of the problems you've mentioned.  So far we've not had any reports of it.   I'm sure other PWs use custom saves as well, so it may not be as much a problem as you think, unless you've actually gone around and tested all of them.

Jester

#3
painofdungeoneternal

painofdungeoneternal
  • Members
  • 1 799 messages
This issue has been reported, and discussed, and demonstrated, and it just has not been fixed. Other things they fixed actually were more important. At this point there is very very little chance for this to be fixed as all patches are paid for by atari, and they don't seem to be wanting to support NWN2 anymore. I know 1.24 was close to being release when the lawsuit happened with hasbro which stopped everything, and there were many things they ( obsidian ) wanted to fix, but at this point i am not sure how much hope for this to ever see the light of day.

The solution, well kaedrins got some fixes, to get more repaired then it really means you need nwnx. Currently if you have all the work arounds it's tolerable, but once someone points it out, well the game is a lot more fun if someone does not point out all the bugs to you. ( kind of like the spelling error no has noticed for 6 years, once someone points it out, it suddenly becomes totally obvious to everyone )

If it's going to get fixed, it's got to be something done by the community, and it is not one issue, but a lot of little inter-related issues. In the mean time we just got to try to minimize the problems this causes, and as people improve how things work we need to share them.

#4
c i p h e r

c i p h e r
  • Members
  • 261 messages
Has anyone talked to Skywing about this one?

#5
dethia

dethia
  • Members
  • 146 messages
We use the default auto-safe feature that just exports to bics and yeah this has been a really annoying problem.