Whitelist & Blacklist Filter list & Priority list
This feature was requested way back on beta release v1.0.0-beta by the community. This will allow players to create layers of defensive turrets that focuses on certain types of entities (and players) implementing a complex defensive web that complement other turrets' weakness.
Whitelist
The whitelist feature will only target players. It will be the turret's privilege interface, specifying who can modify and remove the turret. This will allow the owner of the turret to have other players manage their turrets' targeting system and privilege system. However, this also meant that players could remove other players on the whitelist. With that in mind, the owner of the turret will be immutable, preventing other players from removing them from the whitelist.
Considerations
- The owner can transfer ownership of the turret to another player.
- Tiered privileges, allowing separation of concerns like how a server has mods and admins.
Blacklist Filter & Priority List
The blacklist is now a dropped idea in favor of the filter and priority lists. However, a turret can only have one of the two: either a filter list or a priority list.
By default, the filter list is the one in used but has nothing in its list, allowing the turret to attack its intended targets (i.e. AA Turret to flying hostiles, Cannon Turret to ground hostiles). A checkbox or a toggle button/switch will be present to switch the type of list the turret will use.
This specific list will offer an interface where they could add and remove players and entity types. As for the interface, it is currently conceptualized to look like the Recipe Book GUI but with different content. This allows the entities to be grouped into different categories for easier browsing.
Filter List
A filter list designates who/what the turret will consider as a target. It allows the turret to target a specific group of entities or a specific player to attack when in range while marking the others as non-targets and thus, not engaging nor shooting them except from those in the filter list.
Priority List.
On the other hand, as the name portrays, the Priority List provides a list of targets that are considered high priority and forcing the turret to attack said entities first before its standard targeting system kicks in.
Considerations
- Visual Indicator of what list the turret is using.
- Turret owner indicator.
User Interface
The User Interface (UI) it will use will be a Graphical User Interface (GUI) screen that can only be accessed using a separate equipment. This will allow the mod to populate the "Equipment" category of the mod instead of just the currently implemented Turret Remover.
The inventory view with the recipe book enabled on the left side. The tabs will be replaced with entity categories "All", "Hostile", "Neutral", "Passive", "Misc". The 5-column recipe content will be replaced with a 3-column entity display for easier recognition.
Configuration Scope
The scope of the lists is only to the respective turrets. While this means more data to store per turrets, this will also allow for a more complex experience when playing the mod with the turrets.
Whitelist &
BlacklistFilter list & Priority listThis feature was requested way back on beta release
v1.0.0-betaby the community. This will allow players to create layers of defensive turrets that focuses on certain types of entities (and players) implementing a complex defensive web that complement other turrets' weakness.Whitelist
The whitelist feature will only target players. It will be the turret's privilege interface, specifying who can modify and remove the turret. This will allow the owner of the turret to have other players manage their turrets' targeting system and privilege system. However, this also meant that players could remove other players on the whitelist. With that in mind, the owner of the turret will be immutable, preventing other players from removing them from the whitelist.
Considerations
BlacklistFilter & Priority ListThe blacklist is now a dropped idea in favor of the filter and priority lists. However, a turret can only have one of the two: either a filter list or a priority list.
By default, the filter list is the one in used but has nothing in its list, allowing the turret to attack its intended targets (i.e. AA Turret to flying hostiles, Cannon Turret to ground hostiles). A checkbox or a toggle button/switch will be present to switch the type of list the turret will use.
This specific list will offer an interface where they could add and remove players and entity types. As for the interface, it is currently conceptualized to look like the Recipe Book GUI but with different content. This allows the entities to be grouped into different categories for easier browsing.
Filter List
A filter list designates who/what the turret will consider as a target. It allows the turret to target a specific group of entities or a specific player to attack when in range while marking the others as non-targets and thus, not engaging nor shooting them except from those in the filter list.
Priority List.
On the other hand, as the name portrays, the Priority List provides a list of targets that are considered high priority and forcing the turret to attack said entities first before its standard targeting system kicks in.
Considerations
User Interface
The User Interface (UI) it will use will be a Graphical User Interface (GUI) screen that can only be accessed using a separate equipment. This will allow the mod to populate the "Equipment" category of the mod instead of just the currently implemented Turret Remover.
The inventory view with the recipe book enabled on the left side. The tabs will be replaced with entity categories "All", "Hostile", "Neutral", "Passive", "Misc". The 5-column recipe content will be replaced with a 3-column entity display for easier recognition.
Configuration Scope
The scope of the lists is only to the respective turrets. While this means more data to store per turrets, this will also allow for a more complex experience when playing the mod with the turrets.