fodev.net
Other => FOnline:2238 Forum => Archives => Suggestions => Topic started by: JovankaB on April 27, 2012, 07:30:55 pm
-
I learned that players often get confused by this (and call GM for help, trapped in TB combat).
I believe that most players expect that the combat mode is determined in the moment when they
enter a location first time. However this is not what happens. Combat mode is determined when
the location is spawned.
For normal encounters it doesn't matter, because location is spawned right before player enters it
- so there is no difference in this case. It makes a difference in case of quest locations.
Quest locations (like straded rust ship, railway gang camp etc) are spawned when players talk to
a quest NPC, in a different place on world map, and often long before the player will visit the quest
location. So it's a bit counter-intuitive, especially if someone does a quest first time or switches
combat mode often.
Therefore I suggest to make combat mode in quest locations to behave in more intuitive way and
set it when player enters the location.
-
This sounds good. Even I had times when I was surprised that the location was in rt/tb cause I forgot to set it to the desired one.
-
I learned that players often get confused by this (and call GM for help, trapped in TB combat).
If it's worth anything I'm sorry about that. :)
-
This is actually must to do.
-
Therefore I suggest to make combat mode in quest locations to behave in more intuitive way and
set it when player enters the location.
Define "player".
-
Define "player".
First player character entering the quest location. Doesn't matter I think, because in practice only quest owner sees it.
GM-before-player visit is such a rare occurrence that it can be ignored in my opinion :>
If there is a party entering, then there might be needed a check who is the leader, I don't know.
I suppose quest locations would need some flag if they were visited already or not...
-
This would be quite convenient, agreed.
-
Yes, this would be very helpful and this is how I thought it worked in read the feature in the changelog. Anyway nice suggestion!