SL21W41 - Revision history

Kademlia at 23:23, 3 November 2022

2022-11-03T23:23:59Z

Kademlia at 20:56, 6 December 2021

2021-12-06T20:56:26Z

Kademlia at 20:54, 6 December 2021

2021-12-06T20:54:32Z

← Older revision		Revision as of 20:54, 6 December 2021
Line 9:		Line 9:
	***'''Add a quick board comparison/equality check by comparing screen-size first (+ tile element count second)? Needed? The BoardHash should do this already right?'''		***'''Add a quick board comparison/equality check by comparing screen-size first (+ tile element count second)? Needed? The BoardHash should do this already right?'''
	**Fix: Screen not refreshing on first open (Land manager)		**Fix: Screen not refreshing on first open (Land manager)
	**'''Fix: Screen Statistics-system no longer correct'''
	**Removed '''current money''' from screen as it makes caching nearly impossible.		**Removed '''current money''' from screen as it makes caching nearly impossible.
	***'''=> Always changing information should not be part of Header/Footer'''		***'''=> Always changing information should not be part of Header/Footer'''

Kademlia at 16:12, 17 October 2021

2021-10-17T16:12:24Z

← Older revision		Revision as of 16:12, 17 October 2021
Line 20:		Line 20:
	***Fix screen position interaction on cubic plants		***Fix screen position interaction on cubic plants
	***Added pixel-perfect interaction for plants (transparent interactions are ignored)		***Added pixel-perfect interaction for plants (transparent interactions are ignored)
	***~~'''~~Hitbox shadows/Plant shadows are annoying/random? can we disable those?~~'''~~		***Hitbox shadows/Plant shadows are annoying/random? can we disable those?
	****~~'''Try placing as riding on armorstand. Might remove shadow'''~~		****! We can only show F3 Hitboxes + Shadows OR NO F3 hitbox and no shadows!
	****'''Try different spawn-order. Hitbox first frames later'''
	****'''Try spawning 0.01 blocks higher/lower'''
	****'''Try different materials'''
	****'''Try adding other metadatas'''
	*Nils intro to Kadi / Chunkli design		*Nils intro to Kadi / Chunkli design
	**'''General setup of Stasi-Plugin, based on Chunkli Api'''		**'''General setup of Stasi-Plugin, based on Chunkli Api'''

Kademlia at 21:27, 16 October 2021

2021-10-16T21:27:12Z

← Older revision		Revision as of 21:27, 16 October 2021
Line 38:		Line 38:
	****'''Assuming the search/query times are 'ok' and the datasize is 'ok' as well we should probably opt for having only one DB as long as possible to reduce complexity'''		****'''Assuming the search/query times are 'ok' and the datasize is 'ok' as well we should probably opt for having only one DB as long as possible to reduce complexity'''
	****'''Even "optimized" documents like ('''https://blog.couchbase.com/the-series-on-time-series-in-couchbase-episode-1/) '''are probably not worth it until far later in the project.'''		****'''Even "optimized" documents like ('''https://blog.couchbase.com/the-series-on-time-series-in-couchbase-episode-1/) '''are probably not worth it until far later in the project.'''
			**'''Test Geospatial as a save/search format'''
			***https://docs.couchbase.com/server/current/fts/fts-supported-queries-geo-spatial.html
			***https://blog.couchbase.com/how-to-geospatial-polygon-search/
			***https://blog.couchbase.com/geospatial-search-how-do-i-use-thee-let-me-count-the-ways/
			***'''We can use 0.001 as one block in lat/lon'''
			***'''1.000 would be the block at X 1000'''
			***'''Y would be altitude, not directly searchable in geospatial data typically'''
			***'''A blockchange at X -54_321 and Y 150 and Z 765 would be saved as { lat: -54.321, lon: 0.765, alt: 150 }'''

Kademlia at 15:42, 16 October 2021

2021-10-16T15:42:11Z

← Older revision		Revision as of 15:42, 16 October 2021
Line 21:		Line 21:
	***Added pixel-perfect interaction for plants (transparent interactions are ignored)		***Added pixel-perfect interaction for plants (transparent interactions are ignored)
	***'''Hitbox shadows/Plant shadows are annoying/random? can we disable those?'''		***'''Hitbox shadows/Plant shadows are annoying/random? can we disable those?'''
	****Try placing as riding on armorstand. Might remove shadow		****'''Try placing as riding on armorstand. Might remove shadow'''
	****Try different spawn-order. Hitbox first frames later		****'''Try different spawn-order. Hitbox first frames later'''
	****Try spawning 0.01 blocks higher/lower		****'''Try spawning 0.01 blocks higher/lower'''
	****Try different materials		****'''Try different materials'''
	****Try adding other metadatas		****'''Try adding other metadatas'''
	*Nils intro to Kadi / Chunkli design		*Nils intro to Kadi / Chunkli design
	**'''General setup of Stasi-Plugin, based on Chunkli Api'''		**'''General setup of Stasi-Plugin, based on Chunkli Api'''

Kademlia at 15:42, 16 October 2021

2021-10-16T15:42:04Z

← Older revision		Revision as of 15:42, 16 October 2021
Line 21:		Line 21:
	***Added pixel-perfect interaction for plants (transparent interactions are ignored)		***Added pixel-perfect interaction for plants (transparent interactions are ignored)
	***'''Hitbox shadows/Plant shadows are annoying/random? can we disable those?'''		***'''Hitbox shadows/Plant shadows are annoying/random? can we disable those?'''
			****Try placing as riding on armorstand. Might remove shadow
			****Try different spawn-order. Hitbox first frames later
			****Try spawning 0.01 blocks higher/lower
			****Try different materials
			****Try adding other metadatas
	*Nils intro to Kadi / Chunkli design		*Nils intro to Kadi / Chunkli design
	**'''General setup of Stasi-Plugin, based on Chunkli Api'''		**'''General setup of Stasi-Plugin, based on Chunkli Api'''

Kademlia at 15:30, 16 October 2021

2021-10-16T15:30:45Z

← Older revision		Revision as of 15:30, 16 October 2021
Line 20:		Line 20:
	***Fix screen position interaction on cubic plants		***Fix screen position interaction on cubic plants
	***Added pixel-perfect interaction for plants (transparent interactions are ignored)		***Added pixel-perfect interaction for plants (transparent interactions are ignored)
			***'''Hitbox shadows/Plant shadows are annoying/random? can we disable those?'''
	*Nils intro to Kadi / Chunkli design		*Nils intro to Kadi / Chunkli design
	**'''General setup of Stasi-Plugin, based on Chunkli Api'''		**'''General setup of Stasi-Plugin, based on Chunkli Api'''

Kademlia at 15:30, 16 October 2021

2021-10-16T15:30:14Z

← Older revision		Revision as of 15:30, 16 October 2021
Line 15:		Line 15:
	***'''=> "Adspace" on right could now be a separate screen !'''		***'''=> "Adspace" on right could now be a separate screen !'''
	***'''Separation of these spaces would make caching much more effective (board / pre render caching)'''		***'''Separation of these spaces would make caching much more effective (board / pre render caching)'''
			**Fix: Plant interaction
			***Fix hitbox positioning of plants
			***Fix hitbox count for cubic plants
			***Fix screen position interaction on cubic plants
			***Added pixel-perfect interaction for plants (transparent interactions are ignored)
	*Nils intro to Kadi / Chunkli design		*Nils intro to Kadi / Chunkli design
	**'''General setup of Stasi-Plugin, based on Chunkli Api'''		**'''General setup of Stasi-Plugin, based on Chunkli Api'''

Kademlia at 15:21, 16 October 2021

2021-10-16T15:21:04Z

← Older revision		Revision as of 15:21, 16 October 2021
Line 14:		Line 14:
	***'''=> "Adspace" on top could now be a seperate screen !'''		***'''=> "Adspace" on top could now be a seperate screen !'''
	***'''=> "Adspace" on right could now be a separate screen !'''		***'''=> "Adspace" on right could now be a separate screen !'''
	***'''Separation of these spaces would make caching much more effective'''		***'''Separation of these spaces would make caching much more effective (board / pre render caching)'''
	*Nils intro to Kadi / Chunkli design		*Nils intro to Kadi / Chunkli design
	**'''General setup of Stasi-Plugin, based on Chunkli Api'''		**'''General setup of Stasi-Plugin, based on Chunkli Api'''

← Older revision		Revision as of 23:23, 3 November 2022
Line 7:		Line 7:
	***Got rid of most of the special caching / update flags for desktop this way		***Got rid of most of the special caching / update flags for desktop this way
	***Code reduction as the general purpose cache now works nicely		***Code reduction as the general purpose cache now works nicely
	***~~'''~~Add a quick board comparison/equality check by comparing screen-size first (+ tile element count second)? Needed? The BoardHash should do this already right?~~'''~~		***Add a quick board comparison/equality check by comparing screen-size first (+ tile element count second)? Needed? The BoardHash should do this already right?
	**Fix: Screen not refreshing on first open (Land manager)		**Fix: Screen not refreshing on first open (Land manager)
	**Removed '''current money''' from screen as it makes caching nearly impossible.		**Removed '''current money''' from screen as it makes caching nearly impossible.
Line 22:		Line 22:
	****! We can only show F3 Hitboxes + Shadows OR NO F3 hitbox and no shadows!		****! We can only show F3 Hitboxes + Shadows OR NO F3 hitbox and no shadows!
	*Nils intro to Kadi / Chunkli design		*Nils intro to Kadi / Chunkli design
	**~~'''~~General setup of Stasi-Plugin, based on Chunkli Api~~'''~~		**General setup of Stasi-Plugin, based on Chunkli Api
	***Think/Test persistence layer		***Think/Test persistence layer
	***~~'''~~Make sure we respect shulker boxes in some way?~~'''~~		***Make sure we respect shulker boxes in some way?
	***95% of data is archival data mostly? Important is mostly just worldchanges ~7 days + chat ~3 month; rest can be slow / compressed?		***95% of data is archival data mostly? Important is mostly just worldchanges ~7 days + chat ~3 month; rest can be slow / compressed?
	***Most likely PostgreSQL + time-series => Timescale db? on an external logging server with batched, async, streamed inserts?		***Most likely PostgreSQL + time-series => Timescale db? on an external logging server with batched, async, streamed inserts?

← Older revision		Revision as of 20:56, 6 December 2021
Line 11:		Line 11:
	**Removed '''current money''' from screen as it makes caching nearly impossible.		**Removed '''current money''' from screen as it makes caching nearly impossible.
	***'''=> Always changing information should not be part of Header/Footer'''		***'''=> Always changing information should not be part of Header/Footer'''
	***~~'''~~=> "Adspace" on top could now be a seperate screen !~~'''~~		***=> "Adspace" on top could now be a seperate screen !
	***~~'''~~=> "Adspace" on right could now be a separate screen !~~'''~~		***=> "Adspace" on right could now be a separate screen !
	***~~'''~~Separation of these spaces would make caching much more effective (board / pre render caching)~~'''~~		***Separation of these spaces would make caching much more effective (board / pre render caching)
	**Fix: Plant interaction		**Fix: Plant interaction
	***Fix hitbox positioning of plants		***Fix hitbox positioning of plants
Line 23:		Line 23:
	*Nils intro to Kadi / Chunkli design		*Nils intro to Kadi / Chunkli design
	**'''General setup of Stasi-Plugin, based on Chunkli Api'''		**'''General setup of Stasi-Plugin, based on Chunkli Api'''
	***~~'''~~Think/Test persistence layer~~'''~~		***Think/Test persistence layer
	***'''Make sure we respect shulker boxes in some way?'''		***'''Make sure we respect shulker boxes in some way?'''
	***~~'''~~95% of data is archival data mostly? Important is mostly just worldchanges ~7 days + chat ~3 month; rest can be slow / compressed?~~'''~~		***95% of data is archival data mostly? Important is mostly just worldchanges ~7 days + chat ~3 month; rest can be slow / compressed?
	***~~'''~~Most likely PostgreSQL + time-series => Timescale db? on an external logging server with batched, async, streamed inserts?~~'''~~		***Most likely PostgreSQL + time-series => Timescale db? on an external logging server with batched, async, streamed inserts?
	****~~'''~~Specifically the data compression would be handy here for non-confirmant itemstacks where all data needs to be logged and not just a LibId~~'''~~		****Specifically the data compression would be handy here for non-confirmant itemstacks where all data needs to be logged and not just a LibId
	****~~'''~~"Small datasets typically see no performance advantage on TimescaleDB vs PostgreSQL (in fact, they might be slightly slower)"~~'''~~		****"Small datasets typically see no performance advantage on TimescaleDB vs PostgreSQL (in fact, they might be slightly slower)"
	****~~'''~~"The queries run (they should typically be time-oriented restriction clause)"~~'''~~		****"The queries run (they should typically be time-oriented restriction clause)"
	***~~'''~~We need to test couchbase for this~~'''~~		***We need to test couchbase for this
	****~~'''~~Assuming the search/query times are 'ok' and the datasize is 'ok' as well we should probably opt for having only one DB as long as possible to reduce complexity~~'''~~		****Assuming the search/query times are 'ok' and the datasize is 'ok' as well we should probably opt for having only one DB as long as possible to reduce complexity
	****~~'''~~Even "optimized" documents like (~~'''~~https://blog.couchbase.com/the-series-on-time-series-in-couchbase-episode-1/) ~~'''~~are probably not worth it until far later in the project.~~'''~~		****Even "optimized" documents like (https://blog.couchbase.com/the-series-on-time-series-in-couchbase-episode-1/) are probably not worth it until far later in the project.
	**~~'''~~Test Geospatial as a save/search format~~'''~~		**Test Geospatial as a save/search format
	***https://docs.couchbase.com/server/current/fts/fts-supported-queries-geo-spatial.html		***https://docs.couchbase.com/server/current/fts/fts-supported-queries-geo-spatial.html
	***https://blog.couchbase.com/how-to-geospatial-polygon-search/		***https://blog.couchbase.com/how-to-geospatial-polygon-search/
	***https://blog.couchbase.com/geospatial-search-how-do-i-use-thee-let-me-count-the-ways/		***https://blog.couchbase.com/geospatial-search-how-do-i-use-thee-let-me-count-the-ways/
	***~~'''~~We can use 0.001 as one block in lat/lon~~'''~~		***We can use 0.001 as one block in lat/lon
	***~~'''~~1.000 would be the block at X 1000~~'''~~		***1.000 would be the block at X 1000
	***~~'''~~Y would be altitude, not directly searchable in geospatial data typically~~'''~~		***Y would be altitude, not directly searchable in geospatial data typically
	***~~'''~~A blockchange at X -54_321 and Y 150 and Z 765 would be saved as { lat: -54.321, lon: 0.765, alt: 150 }~~'''~~		***A blockchange at X -54_321 and Y 150 and Z 765 would be saved as { lat: -54.321, lon: 0.765, alt: 150 }


			Stasi couchbase result => Works super well, Geospatial does not really help.