Last updated
Last updated
View groupings allow you to assign players an individual or a group view based on certain conditions. Each view has its own default scene setting.
Information on various types of conditions can be found here:
With individual views each player sees an unique view, not shared with other players.
Grouped views make all of the players in the same grouping see the same view. This can be useful for roleplay servers when doing presentations, this can also be useful in splitting views based on teams (red team, blue team).
settings:
dithering: false
reset-on-radius-exit: false
## this example assigns players individual views with different
## default scenes, based on their rank
## grouping priority goes from top, to bottom, so the last grouping
## has the highest priority
view-grouping:
## This grouping is assigned to players with no permissions
grouping-default:
## individual grouping makes all of the players
## see their own individual view
type: individual
## the default scene of this grouping
default-scene: scene1
## This grouping is assigned to players with VIP rank
grouping-vip:
## individual grouping makes all of the players
## see their own individual view
type: individual
## the default scene of this grouping
default-scene: scene2
## conditions to check
access-conditions:
## permission check condition
check1:
type: permission
permission: 'rank.vip'
## This grouping is assigned to players with MVP rank
grouping-mvp:
## individual grouping makes all of the players
## see their own individual view
type: individual
## the default scene of this grouping
default-scene: scene3
## conditions to check
access-conditions:
## permission check condition
check1:
type: permission
permission: 'rank.mvp'
scenes:
scene1:
object1:
type: background
color: red
text1:
type: text
text: 'No permission'
scene2:
object1:
type: background
color: green
text1:
type: text
text: 'VIP rank'
scene3:
object1:
type: background
color: blue
tex1:
type: text
text: 'MVP rank'
## This section should be kept from your original board config
displays:
default: ##...
internal:
plugin-version: ##...
settings:
dithering: false
reset-on-radius-exit: false
## this example splits players into two group views, based on their team
## grouping priority goes from top, to bottom, so the last grouping
## has the highest priority
view-grouping:
## This grouping is assigned to players on team blue
grouping-blue:
## individual grouping makes all of the players
## see their own individual view
type: group
## the default scene of this grouping
default-scene: scene-blue
## conditions to check
access-conditions:
## permission check condition
check1:
type: permission
permission: 'team.blue'
## This grouping is assigned to players on team red
grouping-red:
## group type grouping shares the same view for all players
## in the same grouping
type: group
## the default scene of this grouping
default-scene: scene-red
## conditions to check
access-conditions:
## permission check condition
check1:
type: permission
permission: 'team.red'
scenes:
scene-blue:
object1:
type: background
color: blue
button1:
type: button
color: white
on-click:
## this will switch the scene for all blue team players
## as the grouping type is group instead of individual
switch-scene:
type: switch_scene
scene: 'scene-blue2'
scene-blue2:
object1:
type: background
color: blue
button1:
type: button
color: white
on-click:
## this will switch the scene for all blue team players
## as the grouping type is group instead of individual
switch-scene-back:
type: switch_scene
scene: 'scene-blue'
scene-red:
object1:
type: background
color: red
## This section should be kept from your original board config
displays:
default: ##...
internal:
plugin-version: ##...