Post by AvengersWraith on Dec 24, 2003 4:45:48 GMT
I noticed tonight the server lagged me out several times after during DM preparation of the server areas affected for the quest and during the quest.
I heard you mention using a second server through a portal system (or thinking about it), set up a second Fredian on it linked by portals only DMs can allow access to via a locked door blocking a transition. DMs adjust the second Fredian for quests and when ready and players are ready allows players who are going to do the quests to enter the portal on the main server taking them to the other server. After everyone crosses over the DM locks the door and goes to the other server and does the quests.
The up sides:
DM modifications during preparations and on the fly during the quest won't affect the main server.
If the party isn't to huge on the second server it shouldn't lag out either. Make the second server password protected and listed on gamespy during quests and give the password to the players doing the quest (recommend changing the password for each quest) so if they do lag out or crash they have the option of returning to the quest without having to know the second IP for direct connect and can return as soon as possible.
The down side:
No random encounters with other parties not doing the quest. This down side seems small campared to the two upsides to a second server.
Just an idea I had after being lagged out a third or fourth time.
[edited to be easier to understand what I wanted to say]
I heard you mention using a second server through a portal system (or thinking about it), set up a second Fredian on it linked by portals only DMs can allow access to via a locked door blocking a transition. DMs adjust the second Fredian for quests and when ready and players are ready allows players who are going to do the quests to enter the portal on the main server taking them to the other server. After everyone crosses over the DM locks the door and goes to the other server and does the quests.
The up sides:
DM modifications during preparations and on the fly during the quest won't affect the main server.
If the party isn't to huge on the second server it shouldn't lag out either. Make the second server password protected and listed on gamespy during quests and give the password to the players doing the quest (recommend changing the password for each quest) so if they do lag out or crash they have the option of returning to the quest without having to know the second IP for direct connect and can return as soon as possible.
The down side:
No random encounters with other parties not doing the quest. This down side seems small campared to the two upsides to a second server.
Just an idea I had after being lagged out a third or fourth time.
[edited to be easier to understand what I wanted to say]
NWN Server as long as I have seen it run crashes at irregular interevals, it is related to bad memory access from it. Sometimes it runs for hours and hours, other times it has loaded, then crashed. Last night after 3 crashes I ran scandisk on a reboot, no errors BTW, but I wanted to be sure, and it has now run just short of 11 hrs without a crash again, and that included the quest being setup and run. Current server is MORE than capable of handling things hardware wise. Problem we have, and will have until bioware decides that multiplayer is actually interesting to players, is that it is still unstable code, and the more we builders add in the more the problem escalates. Then there is bugs that clients cause from other end by bugged characters thanks to bioware bugs ie: DD DS, the list goes on... welcome to my nightmare, I think most understand that is part of playing online and most times it is not a major issue, so we plod on. Not going to change the second server, which is my dev one into a permanent server no need, we will just carry on as is, after all we had no crashes even on Saturday night and I had 43 players in Castille Castle Main Hall.. AMAZING sight, wish I had a screen shot of you all.
