#SetJet counts as a death
1 messages · Page 1 of 1 (latest)
I reported this when setjet was released, I guess he forgit
Idk if it falls under the same bug, but when I use setjet at the same time as player death, two jets spawn, kinda like using the dospawn command
I got this as well but I forgot how
lol my bad, yeah it's during the delay and it spawns both
let me fix both these bugs
haha why my code so ugly in places 
You're doing well for a sole dev
haha yeah just today have bumped up against a few things I hacked in right at the start of devleopment when I thought this was a meme 😄
is ok, will fix these bugs, just harder than it should be
@here both fixed in next version
Legacy code affects the best of us ;-;
Still doesn't work for me.
EWH74G
https://jam.attackmove.io/?EWH74G
Is the fix in the next build? Not the yesterday's?
Was there an update? It was supposed to be fixed in the next version after 1.40 one
Yeah the bot said it was fixed but i guess it didn’t work
It says fixed in next version
I think this is it in the build notes
The bot was at 4:10 and the build notes was at 4:40 on the same day
And that update has the nvg
That's nothing to do with setjet
Oh
That’s like the only thing kinda near it so I just put 2 and 2 together
But the bot said it’s fixed in next update and that build notes was right after so idk
@night shore can we get some clarification please
not released yet
I need to hold off on the notes
The notes are from when I make the build, it doesn't make it into the build for at least 24 hours on Apple
I'll make a build today with the fix AND setlives in it
Ahh I understand
Thanks goat 
The bug with losing points on setjet?
Nevermind, I see a video showing it
Exactly
I need someone to confirm it still happens on latest as I can't reproduce it
I'll do a test mission.
Ok. I did it myself on v. 1.345. The last life is not taken because of setlives 1 just before the third setjet.
653KS7
https://jam.attackmove.io/?653KS7
Oh, and BTW in the editor lives are not taken with the playerdied event. So to reproduce this bug you have to start it from the mission screen. Not from the editor.