tanohmz

I just see ORK 2.6.0 source code and found a lot of .Equals() function was replaced by == .
Would you mind if i ask this was effected with performance or something ?

If this effected maybe I should changed all of source code in my project follow ORK.

gamingislove

Moved to scripting :)

Well, it depends - Equals has a slightly bigger overhead (resulting in a little bit more GC allocation) but is typesafe, while == is quick and dirty.

I've replaced all Equals with == for the enum comparisons (i.e. pretty much every kind of type selection in ORK, like dialogue types, etc.) because they summed up to a large amount of GC allocation in some use cases (mostly for stuff happening each frame, like global events or HUD game state checks) and don't really need type safety. The effect is only noticable if this is done very often, e.g. like in my test with 100 global events checking and changing multiple variables (i.e. in total around 500 variables checked and 500 variables changed each frame - with each having multiple enum type checks).

tanohmz

This is my new knowledge.
Thank you very much GIL. :)