Printable View
I just ran into a case where using a spread value of 0 causes a bug, but using a spread value of 1 does not. Can anyone explain what other side effects might be caused from using a spread value of 1? I thought they just controlled whether the index of an object was base-1 or not.
Yes, it only controls which value to start on. If you have 3 objects and spread value 1, they get 1,2 and 3.
What kind of bug does it cause? My guess is that it probably has something to do with your other events.
If you spread the value 5 then the first object will have a value of 5, the second will have a value of six; and so on.
If there is a problem when spreading value 0 it's probably because you have involved an object/extension which works in base one; such as 'list'.
opps popcorn beat me :grin:
Remember to check the the ordering of your actions.
I would imagine that the problem is that one of your objects isn't effected by the actions that the rest are. As Seele mentioned, its because of the whole "base 1" thing, which means an object, or several objects have a one based index. MMF2's built-in fast loops have a zero-based index, meaning the first loop is 0. Objects like the list object and the string parser are by default 1-based, but have a checkbox to make them 0-based. Personally, I prefer 0-based indexes, because I use fastloops in most of my games, and it can be annoying to have to add +1 to everything to make sure it works right.
I am not too sure why it is affecting my file so much. Can anyone take a look:
file
Just change the first line "Always" to spread a value of 1.
When you run the game, one tree is picked at random and should fire a single volley. Then another tree is picked and it will fire a single volley. Each tree should only fire 3 volleys total. This works great when the spread value is 0. But trees start playing animations without firing if I switch it to spread value 1.
I don't see the problem here.. If I understand you correctly, you change spread value from 0 to 1 without doing changes in the loop events.
Since in your test you test if loopindex equals enemyID, it tests only the objects with enemyID 0, 1 and 2. When you set the spread value to 1, the objects will have EnemyID 1,2 and 3, and therefore the third one will not be tested in the loop.
So, are you saying the loop index is always base-0? I assumed that the spread value told it to be base-0 or base-1.
The LoopIndex of fast loops are always 0-based. But if you want you can use LoopIndex("foo")+1 in any relevant expression to make it act as if it were 1-based.Quote:
Originally Posted by mobichan
(makes mental note) Thanks. :D