This is another hotfix as we realized removing 'context-storage-type' was not a good idea.
 
 Context Storage Type
 
 This is how 'context-storage-type' will work now when used on shared DB storage :
 
 
global - GD will query all claims and ignore LP's server context. If you do NOT want a server to be counted toward's a player's total claim block cost then you should change it's table prefix or move the server to a standalone GD DB.
 
 
server - GD will query all claims that match LP's server context. For example, if you have 3 survival servers all using the LP server context 'survival' and want GD to share blocks across these 3 servers then this is the option you should use.
 
 Note: If you do NOT want to share blocks with any other server then you can have a unique LP server context or set 'force-server-only' to 'true'.
 
 
world - GD will query all claims that match the current server and world UUID. This is used if you want players to have separate block data per world.
 
 
 
2.5.3 Changelog
 
 
 
 
  Code (Text):
 
 
 
  
 * Revert 'context-storage-type' change in 2.5.2.
  
 * Update 'context-storage-type' global logic to account for all claims in DB regardless of LP server context.
  
 * Add 'force-server-only' setting for a server that does not want player block data shared with any other server.
  
 * More fixes for 'protected-worlds'
  
 * Fix entity-damage checking trust for actions such as player fall.