[n2vwz]

I'm running a wired connection. I started out with a 10s delay on .198 and was able to reduce that number to 2s and still have reliable operation.

On .298 and .398, the delay is zero regardless of the number that I specify. That's the problem I am trying to describe. This looks a like a new bug.

Meanwhile, I've switched back to .198 and the delay is working correctly again. Again, I'm using a wired connection, not wireless.

I'm not able to reproduce that here. The delay isn't an absolute value, it's a maximum wait time until the network is up; wired connections are going to be nearly instantaneous, so the delay will likely appear to be zero. What sort of network connections / mappings are you using such that this isn't working?

The delay is needed and used to be present on wired connections. With .198, if I punch in a 60s delay, I must wait 60s for KODI to start. With .298 & .398, if I punch in 60s, the wired connection is instantaneous. Because no delay is present, my NAS shares cannot be seen. I need a minimum delay of 2s on a wired connection for proper operation. The delay needs to be restored for wired connections like it was on older versions.