[Trigger] Points

[Empirean]

Ehh is storing point into an indexed variable even possible? I tried storing a point into a temporary variable then stored it into an indexed variable. Im losing the saved point as soon as i destroy the temp point. So i was wondering if you index the point and it gets destroyed during deindex will the spell still properly? Or it can be fixed by simply not storing the point into a temp variable

 

[Bribe]

You have to create a new location from the original location or just not remove the original location.

 

[Empirean]

So, this is really the behavior of point variables in the world editor? Are there other variables that behaves like this?

 

[IcemanBo]

Variables are pointers that point on a part in memory.
If you do "A = B" with objects, it just copies the pointer from "A" to "B" but does not copy the object itself.
A new object won't get created here, but now you have 2 variables pointing on the very same object.
So if you destroy the object from variable "A", the pointed object for "B" also gets destroyed and vice versa.

Your:
Set A = CreatePoint(x,y)
Set B = A
Destroy A
// Now both are destroyed

Solution
Set A = CreatePoint(x,y)
Set B = CreatePoint(x,y)
Destroy A

Or what an idea might be is just not to use a temp variable for it.
I mean you anyway index it, so you might used just the indexed point.

 

[Empirean]

Im storing the same thing for the indexed points so i just add it to the temp point first. So thats whats going on here. Thanks so much!

 

[Wietlol]

I assume primitive variables are raw data, but I might be wrong here.
(integer, real, boolean, string... code?)

 

[Empirean]

If
int x = 1
int y = x
x = 0
is y == 1 ?
i dont have world editor atm so i cant try but i assume that the answer true.

 

[Wietlol]

Yes that works.

When you use methods like this, you simply copy and paste the value of x into y.
So when you set x to something else, y still remains 1.

I dont even want to imagine a language that cant do it like this.