Palace Vase Orb - Revision history

Ruh at 21:28, 2 July 2024

2024-07-02T21:28:49Z

← Older revision		Revision as of 21:28, 2 July 2024
Line 17:		Line 17:

	== Discovery ==		== Discovery ==

			{{Glitches}}

Ruh at 21:28, 2 July 2024

2024-07-02T21:28:14Z

← Older revision		Revision as of 21:28, 2 July 2024
Line 7:		Line 7:

	== Technical ==		== Technical ==
	A comment on Noki Doki's [~~Daxter - The Vase Orb~~ https://www.youtube.com/watch?v=gux9oFKxKeU] video helps to explain what could be happening with this bug.		A comment on Noki Doki's [https://www.youtube.com/watch?v=gux9oFKxKeU Daxter - The Vase Orb] video helps to explain what could be happening with this bug.

	<blockquote>		<blockquote>

Ruh at 21:27, 2 July 2024

2024-07-02T21:27:40Z

← Older revision		Revision as of 21:27, 2 July 2024
Line 7:		Line 7:

	== Technical ==		== Technical ==
	A comment on Noki Doki's "Daxter - The Vase Orb" video helps to explain what could be happening with this bug.		A comment on Noki Doki's [Daxter - The Vase Orb https://www.youtube.com/watch?v=gux9oFKxKeU] video helps to explain what could be happening with this bug.

	<blockquote>		<blockquote>

Ruh at 21:27, 2 July 2024

2024-07-02T21:27:01Z

← Older revision		Revision as of 21:27, 2 July 2024
Line 7:		Line 7:

	== Technical ==		== Technical ==
			A comment on Noki Doki's "Daxter - The Vase Orb" video helps to explain what could be happening with this bug.

	<blockquote>		<blockquote>
	''I think this is an authoring error that can happen when game engine components can be individually copied (orb spawn locations, the breakable vase trigger) but they're not all one thing, and repetitive rooms like this are often populated by copying things around so it's even possible that two breakable vase triggers share the same reference to an orb spawn location -- I'm surprised that this kind of error is not more frequent, but for when the orb spawns far from the container, it's possible that the container itself moved during development. Normally mundane stuff like this doesn't make it through QA so it's interesting in itself.''		''I think this is an authoring error that can happen when game engine components can be individually copied (orb spawn locations, the breakable vase trigger) but they're not all one thing, and repetitive rooms like this are often populated by copying things around so it's even possible that two breakable vase triggers share the same reference to an orb spawn location -- I'm surprised that this kind of error is not more frequent, but for when the orb spawns far from the container, it's possible that the container itself moved during development. Normally mundane stuff like this doesn't make it through QA so it's interesting in itself.''

Ruh at 21:26, 2 July 2024

2024-07-02T21:26:05Z

← Older revision		Revision as of 21:26, 2 July 2024
Line 10:		Line 10:
	''I think this is an authoring error that can happen when game engine components can be individually copied (orb spawn locations, the breakable vase trigger) but they're not all one thing, and repetitive rooms like this are often populated by copying things around so it's even possible that two breakable vase triggers share the same reference to an orb spawn location -- I'm surprised that this kind of error is not more frequent, but for when the orb spawns far from the container, it's possible that the container itself moved during development. Normally mundane stuff like this doesn't make it through QA so it's interesting in itself.''		''I think this is an authoring error that can happen when game engine components can be individually copied (orb spawn locations, the breakable vase trigger) but they're not all one thing, and repetitive rooms like this are often populated by copying things around so it's even possible that two breakable vase triggers share the same reference to an orb spawn location -- I'm surprised that this kind of error is not more frequent, but for when the orb spawns far from the container, it's possible that the container itself moved during development. Normally mundane stuff like this doesn't make it through QA so it's interesting in itself.''

			- EntranceJew
	</blockquote>		</blockquote>


	== Discovery ==		== Discovery ==

Ruh at 21:25, 2 July 2024

2024-07-02T21:25:26Z

← Older revision		Revision as of 21:25, 2 July 2024
Line 8:		Line 8:
	== Technical ==		== Technical ==
	<blockquote>		<blockquote>
	I think this is an authoring error that can happen when game engine components can be individually copied (orb spawn locations, the breakable vase trigger) but they're not all one thing, and repetitive rooms like this are often populated by copying things around so it's even possible that two breakable vase triggers share the same reference to an orb spawn location -- I'm surprised that this kind of error is not more frequent, but for when the orb spawns far from the container, it's possible that the container itself moved during development. Normally mundane stuff like this doesn't make it through QA so it's interesting in itself.		''I think this is an authoring error that can happen when game engine components can be individually copied (orb spawn locations, the breakable vase trigger) but they're not all one thing, and repetitive rooms like this are often populated by copying things around so it's even possible that two breakable vase triggers share the same reference to an orb spawn location -- I'm surprised that this kind of error is not more frequent, but for when the orb spawns far from the container, it's possible that the container itself moved during development. Normally mundane stuff like this doesn't make it through QA so it's interesting in itself.''

	</blockquote>		</blockquote>

	== Discovery ==		== Discovery ==

Ruh: Created page with "In Daxter, precursor orbs can be found hidden in container objects (boxes, vases, etc). By attacking and destroying the container object, the object is destroyed and the precursor orb appears/spawns in and can be collected. In the Baron's Palace, there is a vase that, when destroyed, will spawn in a precursor orb, but the precursor orb will spawn in another location near a different vase. == Tutorial == https://www.youtube.com/watch?v=gux9oFKxKeU ==..."

2024-07-02T21:25:04Z

Created page with "In Daxter, precursor orbs can be found hidden in container objects (boxes, vases, etc). By attacking and destroying the container object, the object is destroyed and the precursor orb appears/spawns in and can be collected. In the Baron's Palace, there is a vase that, when destroyed, will spawn in a precursor orb, but the precursor orb will spawn in another location near a different vase. == Tutorial == <youtube>https://www.youtube.com/watch?v=gux9oFKxKeU</youtube> ==..."

New page

In Daxter, precursor orbs can be found hidden in container objects (boxes, vases, etc). By attacking and destroying the container object, the object is destroyed and the precursor orb appears/spawns in and can be collected.

In the Baron's Palace, there is a vase that, when destroyed, will spawn in a precursor orb, but the precursor orb will spawn in another location near a different vase.

== Tutorial ==
<youtube>https://www.youtube.com/watch?v=gux9oFKxKeU</youtube>

== Technical ==
<blockquote>
I think this is an authoring error that can happen when game engine components can be individually copied (orb spawn locations, the breakable vase trigger) but they're not all one thing, and repetitive rooms like this are often populated by copying things around so it's even possible that two breakable vase triggers share the same reference to an orb spawn location -- I'm surprised that this kind of error is not more frequent, but for when the orb spawns far from the container, it's possible that the container itself moved during development. Normally mundane stuff like this doesn't make it through QA so it's interesting in itself.

</blockquote>

== Discovery ==