Fixed small issue regarding inconsistencies between types and moved to int16_t

[RudideC]

Why int16_t?

• 32 thousand is way more than enough pings and the benefits of having a signed int outweigh those that come from having double the max as no one will use it
• I am aware that some compilers turn int to int16 by default but this solution works on everything
• int8_t or uint8_t could be used, but I chose not to because they don't provide much headroom.

I haven't done much testing but it fixed my issue and seems stable. I would appreciate if someone else tested if it works

[dvarrel]

Hi,
have you got compiling issue ?
esp8266 library is now 3.x

[RudideC]

This is completely unrelated to the ESP8266 issue. Just fixes a small bug i was facing

[RudideC]

Does this PR work for you?

[dvarrel]

perhaps better use uint16_t when it's > 0 ?

[RudideC]

not really. in the case that someone wants the amount of pings to be entered by the user, the following could happen:

• if we use uint16_t, if a negative number is accidentally inserted it will turn into an insanely high number which the program cannot detect
• if we use int16_t we can just add a negative number check and throw an error

also no one will ping a machine 32 thousand times, let alone 64 thousand