I am currently creating a platform game on Construct 3. I recently read about the difference between Delta Time coding and regular every tick codes. I am trying to convert all my "every tick" code into Delta Time, slow computer-friendly code. I am having some trouble with this though.
The first question I have is related to the player character in the game. This is how my main character is currently set up:
I have a visible character sprite (objBoi) and an invisible rectangular hitbox sprite with the platform behavior (objHitbox).
The code says that every tick, you set the position of objBoi to objHitbox. Given that basic Construct behaviors by default are coded with Delta T in mind, and the hitbox is platform enabled, is it necessary to change this code to make it low FPS-friendly?
The second question has to do with angles and Delta T.
The character in the game is holding a flashlight. The angle of the flashlight follows the mouse cursor. It is currently set up where the base of the cone of light on every tick moves to the base of the flashlight, and its angle on every tick rotates towards the X and Y position on the mouse. This code does not use Delta T for the angle of the flashlight, so I'm afraid that on a slower computer the flashlight would rotate slower. What would be a better way to code the angle of light incorporating Delta T?