~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@eyedeekay
@itsjustme
@orignal
@postman
@zzz
+FreefallHeavens
+Xeha
+cumlord
+hk
+onon_
+poriori
+profetikla
+r00tobo
+radakayot
+snex
+uop23ip
Arch
Danny
DeltaOreo
Irc2PGuest17611
Irc2PGuest1833
Irc2PGuest58773
Irc2PGuest67597
Meow
Nausicaa
Ni4ozeiT
Onn4l7h
Onn4|7h
T3s|4__
acetone_
anu
ardu
boonst
deadface
dickless
enoxa
mareki2pb
not_bob_afk
pisslord
qend-irc2p
r3med1tz-
shiver_sc
simprelay
solidx66_
u5657
woodwose
dr|z3d
sounds good. feel free to send over a merge request if you update the docs.
y2kboy23
will do.
T3s|4
o/ dr|z3d - is it possible for a + update to break the wrapper script - or is/was that problem on my end only? iirc, you pushed 3 updates earlier today, and I after restarting into the second one, my wrapper was hosed. However, this only happened on one of my 2 laptops. Both rigs have been running: java-19-openjdk (default) for months without issue
dr|z3d
T3s|4_: not possible, wrapper.config never gets updated after initial install.
T3s|4
dr|z3d: noted (and as ecpected), but curious how that could have possibly happened
T3s|4
^*expected
dr|z3d
local file corruption somewhere, T3s|4. only thing I can think of.
T3s|4
yep dr|z3d, pretty sure that's the only theory that can explain it. In any event, fixed now :)
dr|z3d
*thumbs up*