SL22W28: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
[[SL22W27|◄ SL22W27]] | [[SL22W29|SL22W29 ►]] | [[SL22W27|◄ SL22W27]] | [[SL22W29|SL22W29 ►]] | ||
<br /> | |||
* Making desktop/panels & plants work the same way & adding public screens & adding group screens | |||
*# PlayerId caller in RenderOrDeliverJob needs to be a list of people (allows for group-screens) | |||
*# Have a default state for a screenmodel | |||
*## Needs to be created to reduce amount of renderings. | |||
*## All panels and plants will have the same state for all players initially => only render once | |||
*## Try to reuse a plant-render for all plant instances (of the same type) as their default-state should be the same | |||
*## | |||
* Globally public screens have a single state that changes/updates on interaction | |||
* private screens (some plants) have a single default state that can be used for all players and all plants of the same type | |||
** On interaction of a player a state is created and save in the temp-states of the player | |||
* '''NOT SUPPORTED:''' Screens that can be in the same state for an amount X of players. Only global public or private is allowed. | |||
* | |||
<br /> | <br /> |
Revision as of 16:35, 17 July 2022
- Making desktop/panels & plants work the same way & adding public screens & adding group screens
- PlayerId caller in RenderOrDeliverJob needs to be a list of people (allows for group-screens)
- Have a default state for a screenmodel
- Needs to be created to reduce amount of renderings.
- All panels and plants will have the same state for all players initially => only render once
- Try to reuse a plant-render for all plant instances (of the same type) as their default-state should be the same
- Globally public screens have a single state that changes/updates on interaction
- private screens (some plants) have a single default state that can be used for all players and all plants of the same type
- On interaction of a player a state is created and save in the temp-states of the player
- NOT SUPPORTED: Screens that can be in the same state for an amount X of players. Only global public or private is allowed.
- Creating a working player with test-recording replay
- /player set test Kademlia
- /player recordvariant test 1
- /player setactivevariant test 0
- /player setpda test movetest playplayermotion test,player_test_0_1