Creates a ScoreMessage to be used in the designer.

Freezes the location of the message for timeSeconds seconds.

For internal use only; this is used by the custom inspector GUI to show the next ScoreFlash in testing mode.

Shortcut for pushing messages directly using this ScoreFlashFollow3D instance.

Shortcut for pushing messages in a specific color directly using this ScoreFlashFollow3D instance.

Performs a couple of checks to ensure that everything is set up correctly after an upgrade to a new version.

If assigned, instead of using ScoreFlash.Instance, this ScoreFlashFollow3D will use the assigned ScoreFlash instance when messages are pushed directly via Push(Object).

Message that is shown while in design mode.

Unity doesn't properly support updating the GameView when an object is deselected, so if you disable this, the design will stay in the game view until it is updated once more. I have a hack for this - but unfortunately, it's causing trouble when the object is being deleted (there's an exception that I cannot catch). Both is not a real problem, it's just a little annoying.

Freeze any message pushed directly to this ScoreFlashFollow3D at its read state.

Use this to control the anchor / alignment of the messages sent using this instance of ScoreFlashFollow3D.

Design mode allows you to use the scene view to set up the positioning of this ScoreFlashFollow3D. This works both while playing and while not playing, however, if you have moving options, you might want to pause the game to set things up (otherwise you might chase your messages around ;-) ).

Use this to show random messages.

If this is set to true, ScoreFlash will actually not follow the object anymore but just use the settings to determine the position at the time the message is sent.

Should the game object "leave" the messages behind or should the messages immediately follow the game object?

When the game objects is destroyed, should the messages lose the momentum or not?

Should test messages be directly pushed on this ScoreFlashFollow3D using Push(Object)? If this is checked, you can also test the behavior of freezeOnRead.

The camera that shows this game object to the user. If this is not assigned, Camera.main is used, which should be fine in most cases; but if you have a weird scene setup, you can use this. If you want to use ScoreFlash in a split screen set up ... please contact me ;-)

References to one or more instances of ScoreFlash for testing. If you do not assign any here, ScoreFlash.Instance is used instead; if you do, one instance after the other gets messages.

2D offset in screen coordinates.

Renderer of the game object that this ScoreFlashFollow3D follows. This is very important because it is needed to determine whether the object is actually visible. Like, if it's behind the camera, for instance, you don't want those messages to show in front of you (and they will, if you forget to set this up correctly ;-) ). For this to fully work reliably, make sure to also assign the proper referenceCamera.

The usual delay between two messages in seconds. Use this to increase or decrease the frequency in which test messages are being sent to ScoreFlash. NOTE: This does not have an effect on messages sent via includeMessageSpam (these are always sent in a burst without any delay. Also be aware that this is based on real time (so Time.timeScale has no effect).

3D offset in world coordinates.

Provides access to the current message, which is always the last message that was sent through Push(Object) or Push(Object, Color). You can use this to change the message without going through the animations. This is usually used together with freezeOnRead.

Publicly accessibly ScoreFlash instance that this ScoreFlashFollow3D uses. If it is not assigned, simply returns ScoreFlash.Instance.

The inner anchor for this ScoreFlashFollow3D instance.

Is the designer actually switched on?

Returns true while the location is frozen. FreezeLocation(Single).

Returns false. As there is no screen alignment, locking the inner anchor wouldn't make sense.

Always returns true.

The maximum width of the items.

The minimum padding of the items.

For internal use only; this is used by the custom inspector GUI to show the next ScoreFlash in testing mode.

Screen offset position. See screenPositionOffset.

World position. See worldPositionOffset.

Always returns BottomCenter. ScoreFlashFollow3D is always relative to objects in 3D space, so screen alignment doesn't make sense.

Returns true.

Returns false. ScoreFlashFollow3D is always relative to objects in 3D space, so screen alignment doesn't make sense.

Renderer of the game object that this ScoreFlashFollow3D follows. This is very important because it is needed to determine whether the object is actually visible. Like, if it's behind the camera, for instance, you don't want those messages to show in front of you (and they will, if you forget to set this up correctly ;-) ).