Thank you for the video, I have seen this one in particular. The technique this author uses, as well as most other videos I’ve seen explaining edge scrolling, rely on an event tick to check the mouse position constantly. This is currently the same as the functionality I’ve employed in the screenshot in my original post. I’m looking for a method to get away from an on-tick style that is constantly firing, even when my mouse cursor is no where near the screen edges, to a method where the on-tick only begins once the mouse has entered the defined border space (I’ll use a timer by function name to emulate the tick event after an event node is activated by the mouse entering the border space). I’m thinking four event dispatchers, each with a timer and function, but I’m not sure what to use, that isn’t tick-dependent, to fire off that initial activation of the event dispatchers. It would be similar to firing off the on component begin overlap event node, except instead of two collision volumes overlapping it would be the mouse cursor overlapping a 2D section of the viewport.