Official Game Feedback
-
<sarcasm>Yeah, maybe I should just rewrite half of my script to get around this wonderful bug. Forgetting about mouse hotkeys 'cause I can no longer detect Ctrl\Alt\Shift sounds amazing too.</sarcasm>
Nah, I'll wait until it's fixed.
-
@arK (View Post)
Uh .. ? I was just nicely suggesting a simple workaround. Only the keyup events are broken, keydown works fine. Are you saying that keydown is broken too? Because my script is triggered by crtl+` and still works.
I was really rushed this morning so couldn't look into it for very long. But is should be trivial to fix your scripts. I am still going to try fixing it when I get home. -
@arK (View Post)
I guess the fix may take a while. I've been busy the entire weekend ... working on an ARG / puzzle thing.
I'll try to make another snapshot when it is done. I don't think you can publish saves in snapshots because @Simon hasn't updated the website yet though. -
Jacob1
I just found that when you continuously sprk gold then gold just gets converted into its ctype.
Try it set btry and gold and use prop to set gold's ctype to something like fire and see what happens.
Is it intentional.iam using latest snapshot and official version. Please check this. -
@cracker1000: That's an implementation detail. Sparked conductors actually turn into SPRK and store their previous state in their ctype. When SPRK timeouts, it turns back into its ctype, yielding the original conductor. When you set SPRK's ctype to FIRE, you tell SPRK to turn back into FIRE. Puffs of smoke is what you get.
Edited 6 times by LBPHacker. Last: 19th Apr 2016 -
@arK (View Post)
I see the issue. Looks like you will be able to fix all your scripts very easily right now because all the key data actually is still being sent.
Some background: SDL sends two pieces of useful information about what key was pressed: the keycode, and the character that it represents. In older versions, lua scripts only received the keycode, and also something which was the equivalent of string.char(keycode%256). So like, if you pressed a it would send 97 and 'a', if you were previously holding shift it would also just send 97 and 'a'. That was a problem for tptmp or any other script that needed to support multiple keyboard layouts, it wouldn't know the proper shift of 'a' in your keyboard layout.
So I fixed the character argument to actually use the character that SDL tells us that key is. But it looks like on key up, SDL always puts 0 as the character for some reason. This turns into a null string when passed into lua, and it made you think that all the events (including keycode and ctrl/shift status) were missing. Really everything is there, except for the first argument (character).
Anyway, not ideal but I just changed the first argument for keyups back to how it used to be. The only difference is that stuff like ctrl/shift won't have that %256, so left ctrl won't send '2' and right shift won't send '/', instead they'll just continue be null string.
To fix it for now, don't use the first argument, just use the second one: string.char(keycode%256). Or, use the latest snapshot (can't publish saves with this until Simon updates the website)Edited once by jacob1. Last: 27th Apr 2016 -
And maybe can we get some different tool shapes because the circle one is just annoying to use now...
-
Edited once by jacksonmj. Last: 1st May 2016
-
@jacob1 (View Post)
i dont know why but Vacuum(element not tool) is allowing fire to pass through it when a gas only wall is placed before it and fire being projected towards vacuum in left to right direction. please reply and if you want then i can make an save for illustrations.thanks
