Coming Changes to BH/Jedi
02/01/2022
The SWGEmu Team
There is a lot of speculation going on regarding two commits that have been pushed to gerrit. Both commits are what we refer to as "two way doors," which means they can easily be toggled once they go live. So I would like to break down the commits a bit so they are easier to understand for all, as well as a change to the ToS regarding Jedi and Visibility.
First of all Jedi have fallen under a ToS rule when it comes to visibility for a long period of time. That is as follows:
4.1.3 Phishing is defined as deliberately and persistently wandering into the "visibility radius” of a Jedi to force them onto BH terminals. That said, the galaxy’s currently a dangerous place for a Jedi and they can’t expect to be in one location for long without attracting attention.
This has given Jedi an unbalanced amount of protection when it comes to their visibility. We are going to remove and/or revise this policy because part of playing a Jedi is the fact that you can get visibility and land on the Bounty Hunter Terminals. With that being said there are still rules in place for harassment for all players and should be followed.
The proposed changes:
[Added] Config option to anonymize jedi missions on bounty hunter boards- With the AnonymousBountyTerminals configuration enabled the missions will not show the name of the player directly on the terminals when the mission is listed.
[Changed] Mission rewards to anonymous Jedi missions to static amounts with additional bonus credits upon completion based on target difficulty- Payouts are listed as a static amount and the remainder of the payout based on mission difficulty will be given as a bonus upon completion of the bounty mission.
[Added] Additional message to seeker droids with target name if missions are anonymous- The name of the player Jedi will be given once a Seeker Droid has found the target
Example:
[added] Config variable to allow for custom bounty mission expiration time- Currently player bounty missions can be held for 48 hours before they expire. We are reducing that amount of time to 24 hours. This is in order to prevent friendly BHs from holding a Jedis mission so they cannot be hunted by those that may wish to see the contract carried out.
[added] config option to disable visibility generated from group members- With this change Jedi will not gain visibility from players that they are grouped with. However, they are still open to gain visibility from all other players and NPC's.
Other issues we are actively looking into:
Pulling AI into a private structure- This is a violation of the ToS. Additionally, we will implement a check to prevent AI from following a target into a privately owned structure.
Jedi in Private Houses Being Listed on Bounty Hunter Terminals- We are aware that it can be frustrating for our hunters around the galaxy to pull a mission, track and find their target is sitting AFK in a private structure. So we are going to look to implement a method that if a Jedi is AFK in a private structure they will not be listed on the Bounty Hunter Terminals. When the Jedi exits the structure, their mission will again be listed on the terminals.
~The SWGEmu Team
