Decide the quality level for tracking, i.e. how effective will it be?

now that spells can be aimed at walls and what not, they should have some visual effects instead of just going poof.

https://assetstore.unity.com/packages/tools/particles-effects/quick-outline-115488

We want to feature a scenario where an enemy is behind a wall. Player will then need to figure out the best way to hit the enemy behind the wall.
To showcase this scenario, the player should be able to know that there is an enemy behind a wall. We can do that with outline.

https://medium.com/@aboutin/host-unity-games-on-github-pages-for-free-2ed6b4d9c324

This is particularly important for certain spell types. You might want to aim the AoE pull at the ground. Right now, it requires the other object to be IDamageReceiver.

1. Virtual Joysticks to rotate
2. Tap anywhere on screen to fire
3. Crafting Menu Button
4. Resolution tweaks

The UI is in-game, i.e. the player can switch in/out of crafting mode by simply pressing a key.

https://docs.unity3d.com/Manual/class-ScriptableObject.html

We need to track some values for a Spell Component.

Consider "Widen"
It will increase the model and collider's scale in the axis x y z by a particular value a.
In next version, it should cost mana of b to utilize.
string: "widen"
effect: "scale"
dimension: "x, y, z"
value: a
mana cost: b

How should we store, access, modify these values?
SpellComponent.cs : MonoBehaviour?
SpellComponnet.cs?
SpellComponent.cs : ScriptableObject?

currently, "SpellComponent" is just represented by an enum or sometimes a string. This is a problem because it doesn't have all the additional information mentioned above.

https://docs.unity3d.com/Manual/script-Terrain.html

https://www.youtube.com/watch?v=smnLYvF40s4

@tyang863 If you want to help:

Take a look at projectile_spell_shootable.cs
In Update() we call Process() which will then call Move(). We have the Enum_SpellBehaviors.Tracking for homing missiles and SpellBehaviors.Path forStraight Move.

However, what we want is that there are 3 levels of Tracking. None, Partial, Full.
Then regardless of the type of tracking, we can have different projectile paths.

1. Straight
2. Spiral
3. Curved
4. Manhattan
5. Arc
6. Sin Wave

This should be implemented in the partial class/file SpellBase.Behavior

Arc and Curved are the same things but on a different axis.

These should probably be done by modifying the acceleration in different axis with certain values.

On contact, the spell turns into a tornado that pulls enemies within a radius for a period of time.

UI text to appear that way the player will know how much damage they are doing. Also useful for feedback.

1. Projectile can be fired with a parabola arc that goes high up in the air and down
2. ideally, we also visualize what the arc will look like; you might want to refer to XRITK's teleportation ray. Also, google grenade throw visualization.

Mana will be associated with each element, form and component. Levels are like puzzles that require planning of mana usage.

https://www.google.com/search?q=decal+unity&sxsrf=AJOqlzXK3L2SSySJe08gkw3HmZ5QZQRmtg%3A1675722323546&ei=U37hY7n6IOmrqtsPr42p4Ac&ved=0ahUKEwj579iO-IH9AhXplWoFHa9GCnwQ4dUDCBA&uact=5&oq=decal+unity&gs_lcp=Cgxnd3Mtd2l6LXNlcnAQAzIHCAAQQxCRAjIGCAAQBxAeMgYIABAHEB4yBggAEAcQHjIGCAAQBxAeMgYIABAHEB4yBAgAEB4yBggAEAgQHjIGCAAQCBAeMgYIABAIEB46CggAEEcQ1gQQsANKBAhBGABKBAhGGABQ9AhY9AhgnQpoAnABeACAAaEBiAGhAZIBAzAuMZgBAKABAcgBA8ABAQ&sclient=gws-wiz-serp

XROSUI is currently using Linear. Though I would need to check if we NEED linear space.

Might be easier to just move it to Gamma for performance

Right now, Subservice_Sorcery tracks the SpellComposition of a Launcher via a string identifier (e.g. "Player")
Each Launcher is only associated with 1 SpellComposition.

Given Launcher is like a gun and SpellComposition is like a bullet,
we might want to move to have a data structure of SpellComposition instead.

Subservice Sorcery would have its API modified to support launchers with a single shot, multiple shots, and so on.

Consider the different properties of Launcher and its associated UI, how would they interact with Subservice_Sorcery?
What if you want to represent a revolver and stick a bullet in?

Our system should support casting multiple spells at once.

For example, the case of AoE + Pull at the same time as Projectile or consider AoE + Pull and AoE + Damage at the same time.

For example, consider Spell Component such as Duplicate or Split; we might end up with 5 magic missiles instead of 1 magic missile.

We can leave it as is.

We can find a free skybox.

Or, I have this package if anyone think we needs it
https://assetstore.unity.com/packages/vfx/shaders/polyverse-skies-low-poly-skybox-shaders-104017

Though someone will have to learn how to use it.

Increases the scale of the chosen form by a constant factor.

https://forum.unity.com/threads/mouse-sensitivity-in-webgl-way-too-sensitive.411574/

The new input system is being used. Need to define new bindings and add input manager to switch between crafting and casting mode.

Time	x seconds after launch
Contact	after it come into contact with some object
User	after user follow up with an action
Distance	x meters after launch
Expire	When spell fizzles out at the end of its lifetime

Above are different types of trigger.
These triggers can be associated with another SpellComposition so that when a fire+sphere spell hit the floor, it will create an AoE + fire + damage.

Spells must be able to support multiple spell components simultaneously such as speed up, concentrate, AoE, etc.

Speed up the spell projectile by a constant pre-configured factor.

Spells do different damage to same element vs. other element
Same element: full damage
Other element: no damage (maybe)
Gray: Reduced damage to all elements

Enemy should support: HP, element created from, handle spawn/death

https://www.youtube.com/results?search_query=aiming+laser+unity+C%23

Can refer to XROSUI's ray interactor, though that might be too complicated.

I think what we want is just a laser, made with lineRenderer that fades out as it goes further.

Currently we have the component SpeedUp. We can make a SpeedDown version. Possibly it will kind of solve the problem that parabola run too far away.

Spawn text outside of the boundary

Stage

1. Appearing
2. Staying
3. Disappearing

adjust alpha
adjust size
adjust position

Increase the spell's HP by a constant pre-determined factor.

1. Option to save current spell selection for later use as a preset
2. Remember last X spells crafted and present them as buttons or something the player can select
3. Default Button / Clear Current Selection

On contact, the spell applies one-time damage (equal to its HP) on all targets within a radius.