SL21W34 - Revision history

Kademlia at 23:12, 3 November 2022

2022-11-03T23:12:53Z

← Older revision		Revision as of 23:12, 3 November 2022
Line 3:		Line 3:
	<br />		<br />

	*~~'''~~Problem: PlayerFake movements are currently stateless~~'''~~		*Problem: PlayerFake movements are currently stateless
	**1. Showing different data based on positional information would be a shit idea		**1. Showing different data based on positional information would be a shit idea
	**2. Resulting in: We need to save personalized states at least partially for complex things (like tutorial-dad)		**2. Resulting in: We need to save personalized states at least partially for complex things (like tutorial-dad)

2021-09-06T12:57:22Z

← Older revision		Revision as of 12:57, 6 September 2021
Line 25:		Line 25:
	***/move start run		***/move start run
	**'''setPda [playerfake] [playerpdaname] [pdatype] [pdadata...]'''		**'''setPda [playerfake] [playerpdaname] [pdatype] [pdadata...]'''
	***/player setpda kevin testRun1 '''playplayermove kevin,run'''		***Example:
	***kevin,run <- player to be moved ('kevin') + movement to be used ('run')		****/player setpda test test clear
			****/player setpda test test playplayermove test,a2
			***Example
			****/player setpda kevin testRun1 '''playplayermove kevin,run'''
			****kevin,run <- player to be moved ('kevin') + movement to be used ('run')
	**		**

2021-08-29T20:57:11Z

@@ Line 18: / Line 18: @@
 ***needs ID-rewrite in all those connected systems
 **By default have unique id as null/unset to reduce data/lookups
 **

2021-08-25T16:26:24Z

← Older revision		Revision as of 16:26, 25 August 2021
Line 3:		Line 3:
	<br />		<br />

	* '''Problem: PlayerFake movements are currently stateless'''		*'''Problem: PlayerFake movements are currently stateless'''
	** 1. Showing different data based on positional information would be a shit idea		**1. Showing different data based on positional information would be a shit idea
	** 2. Resulting in: We need to save personalized states at least partially for complex things (like tutorial-dad)		**2. Resulting in: We need to save personalized states at least partially for complex things (like tutorial-dad)
	** 3. Saving states for everything would be overkill / shit		**3. Saving states for everything would be overkill / shit
	** 4. Identifying the specific fake is difficult if we want to persist the data		**4. Identifying the specific fake is difficult if we want to persist the data

	<br />		<br />

	* Implementation Fakestuff state management		*Implementation Fakestuff state management
	** Add Unique persistable ids to fakes		**Add Unique persistable ids to fakes
	** By default have unique id as null/unset to reduce data/lookups		***This might cause problems if we allow copy/transfer to other places in the gameworld
			***Copying a player with conneted menu will be difficult as well
			***as will be copying a player with movement connected
			***needs ID-rewrite in all those connected systems
			**By default have unique id as null/unset to reduce data/lookups
	**		**

2021-08-25T15:10:56Z

← Older revision		Revision as of 15:10, 25 August 2021
Line 1:		Line 1:
	[[SL21W33\|◄ SL21W33]] \| [[SL21W35\|SL21W35 ►]]		[[SL21W33\|◄ SL21W33]] \| [[SL21W35\|SL21W35 ►]]

			<br />

			* '''Problem: PlayerFake movements are currently stateless'''
			** 1. Showing different data based on positional information would be a shit idea
			** 2. Resulting in: We need to save personalized states at least partially for complex things (like tutorial-dad)
			** 3. Saving states for everything would be overkill / shit
			** 4. Identifying the specific fake is difficult if we want to persist the data

			<br />

			* Implementation Fakestuff state management
			** Add Unique persistable ids to fakes
			** By default have unique id as null/unset to reduce data/lookups
			**

2021-08-25T11:00:11Z

Created page with "◄ SL21W33 | SL21W35 ►"

New page

[[SL21W33|◄ SL21W33]] | [[SL21W35|SL21W35 ►]]