Multiplayer: Difference between revisions

Multiplayer (view source)

Revision as of 22:10, 6 November 2008

44 bytes removed , 6 November 2008

more accurate?

Gumby

826

edits

Revision as of 02:42, 14 October 2008 (view source) Geyser (talk \| contribs) (more flexible kitty, i would think) ← Older edit		Revision as of 22:10, 6 November 2008 (view source) Gumby (talk \| contribs) (more accurate?) Newer edit →
Line 27:		Line 27:
	OniPlayer was a project coordinated by typhen and involving [[User:Alloc\|Alloc]], [[User:Kumo\|Kumo]], and [[User:ssg\|ssg]]. Up to the departure of typhen, the project remained in the address-finding phase, with applications limited to Alloc's OniTrainer and typhen's OniFly (the Trainer allowed the user to set or freeze most of the known variables on demand, whereas OniFly performed elaborate freezing on character positions based on their aiming vector). Later, [http://neonew.oni2.net neonew] put the knowledge to use with OniHook, actually tracking and patching a character's animations as if synchronizing action over a network.		OniPlayer was a project coordinated by typhen and involving [[User:Alloc\|Alloc]], [[User:Kumo\|Kumo]], and [[User:ssg\|ssg]]. Up to the departure of typhen, the project remained in the address-finding phase, with applications limited to Alloc's OniTrainer and typhen's OniFly (the Trainer allowed the user to set or freeze most of the known variables on demand, whereas OniFly performed elaborate freezing on character positions based on their aiming vector). Later, [http://neonew.oni2.net neonew] put the knowledge to use with OniHook, actually tracking and patching a character's animations as if synchronizing action over a network.

	Current knowledge of Oni's game-state and character-state structures is very nearly sufficient for multiplayer, ~~either through brute~~ memory watching and patching ~~or (better)~~ driven by Oni's own events, hooked for the purpose. ~~There is no~~ development ~~planned in the short term, however, except~~ for minimal patches to the engine (implementing stuff like [[chr_focus]] and [[chr_location]] for ~~PC demo and~~ the Mac, disabling [[MELE]] loss for dying characters so as to take advantage of Oni's frag/damage counters, making Oni's combat stats accessible from [[BSL]], ...).		Current knowledge of Oni's game-state and character-state structures is very nearly sufficient for multiplayer, combining memory watching and patching driven by Oni's own events, hooked for the purpose. Current development includes for minimal patches to the engine (implementing stuff like [[chr_focus]] and [[chr_location]] for the Mac, disabling [[MELE]] loss for dying characters so as to take advantage of Oni's frag/damage counters, making Oni's combat stats accessible from [[BSL]], ...) and [[AE:Flatline\|Flatline]].