Interface

[shiffman]

• [x] start and stop drill
• [x] toggle bias (keyboard control?)
• [x] retract drill

[kfahn22]

I have a reverse button working. Do you want one?

[frnco]

Interface dimensions also deserve some love here, it's quite tiny on a high-DPI screen (About a third of the browser window's width, with default zoom). It's bad enough that I started playing at 170% zoom.

I do realize the draw() function callls drill() which means the drilling speed is tied to the framerate, meaning changing drilling speed is non-trivial, but it's still worth it to think of a way to control drilling speed. It should be especially helpful for adjusting difficulty level. It could be done either by not calling drill every other run of draw (or calling it multiple times), or by having a way to scale the change in angle/position. Seems worth checking.

[alin256]

• retract drill

I managed to make a button to pull back until an even number of pipe lengths. From there one can start drilling again to hopefully get a better result.

update: I changed the boulders to places where you get STUCK instead of LOSE. Seems to improve playability.

In the current version, there is a problem with removing the first segment of the well.

My version is available for testing here: https://al-digital.no/Directional-Boring/

[kfahn22]

My version reverses direction: https://kfahn22.github.io/Directional-Boring/

(It also changes the scoring a bit. I made it a weighted average of time and path.length

[alin256]

@kfahn22 I like your idea, but it is a bit more difficult to implement.

Currently, you seem to have a bug when going backwards with another bias (see the attached picture). Do you want to help me with the animation of going back? I store old trajectories pieces in oldPaths array. My fork is here: https://github.com/alin256/Directional-Boring

[kfahn22]

@alin256 I have edited the code slightly so that the aiming lines are only visible when the drill is in forward mode as a minimal fix. Feel free to come up with something better, though! Thanks!

[alin256]

@kfahn22 I still have an unrealistic trajectory in the deployed version: