... and to help the end user better understand what is wrong.
Following up on reports and observations that imply the count of active root agents is getting messed up, doesn't match the actual number of agents in the region. Seen during one of the GT shows earlier in the year.
No real functional changes here, just an incremental change to help diagnose what's going on if we get similar reports. This PR only changes the cosmetics of the messages and is slightly more efficient code:
Factored the SceneGraph.GetRootAgentCount() and removed the need for the +1 math.
Recording of hard and soft limits in the log show current usage and limit.
User sees a different message for hard and soft limits.
Hard limit reached shows user the current usage and limit values.
Soft limit just reports "Region estate limit has been reached" for the limit, since estate staff may temporarily set the limit very small to disable additional agent entry.
... and to help the end user better understand what is wrong.
Following up on reports and observations that imply the count of active root agents is getting messed up, doesn't match the actual number of agents in the region. Seen during one of the GT shows earlier in the year.
No real functional changes here, just an incremental change to help diagnose what's going on if we get similar reports. This PR only changes the cosmetics of the messages and is slightly more efficient code: