SL22W41: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[SL22W40|◄ SL22W40]] | [[SL22W42|SL22W42 ►]] | [[SL22W40|◄ SL22W40]] | [[SL22W42|SL22W42 ►]] | ||
* Updated implementation of BuyLand, SellLand | *Updated implementation of BuyLand, SellLand | ||
** Updated navigation | **Updated navigation | ||
** Updated popup information | **Updated popup information | ||
** Updated action-list | **Updated action-list | ||
** Work on RegionHelper and BuyLandHelper / SellLandHelper | **Work on RegionHelper and BuyLandHelper / SellLandHelper | ||
** '''Make Screen-Popup and Action use the same logical validation methods (BuyLandAction, BuyLandPopDiv, BuyLandHelper)''' | **'''Make Screen-Popup and Action use the same logical validation methods (BuyLandAction, BuyLandPopDiv, BuyLandHelper)''' | ||
* Fixed Keyboard-Popup overlapping input-field making the text invisible (RelativePosition) | *Fixed Keyboard-Popup overlapping input-field making the text invisible (RelativePosition) | ||
* Added ChatType for chat-messages coloring | *Added ChatType for chat-messages coloring | ||
'''Cleanup Tickets 2020/2021:''' | '''Cleanup Tickets 2020/2021:''' | ||
Revision as of 13:40, 14 October 2022
- Updated implementation of BuyLand, SellLand
- Updated navigation
- Updated popup information
- Updated action-list
- Work on RegionHelper and BuyLandHelper / SellLandHelper
- Make Screen-Popup and Action use the same logical validation methods (BuyLandAction, BuyLandPopDiv, BuyLandHelper)
- Fixed Keyboard-Popup overlapping input-field making the text invisible (RelativePosition)
- Added ChatType for chat-messages coloring
Cleanup Tickets 2020/2021:
- Shop: Add a checker that disables all special-blocks that should not be tradable
- Disable Shulker Boxes in first Version?
- Shops/LibManager generates IDs for shulker boxes (should be correct for logging purposes? make sure we have a lastUsed Timestamp)
- Render service
- Add websocket connection to chunkli service for render.server
- Blueprint Shop?
- Possibly use abo-service, each player can subscribe to other players to get their latest builds
- Possibly buyer-banning; if a builder sees a player copapasta their shit they can ban them from buying ever again
- Pay-what-you-want? Maybe enough already
- (+ Rating sytem, download count, comments?)
- Setup world setting to to re-render dynmap at time X of day
- https://stackoverflow.com/questions/22163662/how-to-create-a-java-cron-job/22164401#22164401
- Implment a "CronManager" that stores quartz jobs as json files to file. This will allow admins to create new jobs at runtime
- Add "Tools" that are considered 'entry keys' for special loot? These keys will use up one whole slot in the inventory. This allows to limit the amount of available space for a given run of the player. In total a player has 36 slots (rust as comparison has 30 slots). By adding 3-5 different entry keys / key cards we can heavily limit the amount of usable space for a player. The same for similar custom items like: Fuel Tank, MedKit, Analytics Tool (research) etc.
- We could add "Upgrade-Blueprints" as well. Items that do not stack and need to be transported to the IRS for usage.
- Desktop: close/reset all websocket connections on token/password change
- Implement a new Event in Kadi that informs about a pw change -> Act in Kson on this and invalidate the spring session & disconnect WS clients