Page 2 of 2

Re: Bug: instantiation order is used when evaluating previous action

Posted: 09 Aug 2018, 14:07
by masterplayer
Does anyone care about the bug above? GFX47? Pier4r? Are you still alive?

Re: Bug: instantiation order is used when evaluating previous action

Posted: 09 Aug 2018, 15:05
by pier4r
The only one that can do anything is gfx, what can I do?

Re: Bug: instantiation order is used when evaluating previous action

Posted: 09 Aug 2018, 15:30
by ElvenMonk
I think, for team tags its fine to be discovered at the same tick. More over, team tags are mostly used to do instantiation order related tasks and as such, rely heavily on this feature.

Re: Bug: instantiation order is used when evaluating previous action

Posted: 11 Aug 2018, 00:14
by GFX47
masterplayer wrote:Does anyone care about the bug above? GFX47? Pier4r? Are you still alive?


You want team tag conditions to rely on previous tick state?

Re: Bug: instantiation order is used when evaluating previous action

Posted: 11 Aug 2018, 17:52
by ElvenMonk
GFX47 wrote:
masterplayer wrote:Does anyone care about the bug above? GFX47? Pier4r? Are you still alive?


You want team tag conditions to rely on previous tick state?


If we'll have special instantiation order filter for self target, then I would say probably if same will apply to ordinary tags as well.

It will of course kill usage of tags to workaround current limitations of joining node filters, but:
- it's not appropriate usage of tags anyway
- it will remove many other issues with instant tags, such as if/else problem.

Re: Bug: instantiation order is used when evaluating previous action

Posted: 11 Aug 2018, 18:20
by ElvenMonk
And if we will have instantiation order filter for enemies and allies as well, I will allow uniquely identify all bots, making me even happier about the game, then I am now)

Re: Bug: instantiation order is used when evaluating previous action

Posted: 14 Aug 2018, 11:05
by masterplayer
GFX47 wrote:You want team tag conditions to rely on previous tick state?

No. I explained why instantiation order still exists. This breaks the fairness of point-symmetrical maps.

I want my AI to act symmetrical against itself in sandbox mode to avoid butterfly effects giving real blue / real red team an advantage (same AI + same team setup = always draw game).

Currently this is only true for mirrored maps, but not for point-symmetrical maps. One possible solution would be to have point-symmetrical instantiation orders on point-symmetrical maps.

Re: Bug: instantiation order is used when evaluating previous action

Posted: 21 Aug 2018, 09:29
by GFX47
I don't want to introduce instantiation order in filters, it's too far fetched.
I already regret the instant tagging exception too much...