~dr|z3d
@RN
@RN_
@StormyCloud
@eyedeekay
@orignal
@postman
@zzz
%Liorar
%cumlord
%snex
+Onn4l7h
+Onn4|7h
+Over
+poriori
+profetikla
+qend-irc2p
+r00tobo_BNC
+uop23ip
Arch
BubbRubb
Dann
DeltaOreo
Guest99
H20
Irc2PGuest27539
Irc2PGuest4895
Irc2PGuest90985
Irc2PGuest95708
Irc2PGuest98114
Meow
Sh0ck
Stormycloud_
T3s|4_
T3s|4__
ac9f
acetone_
anontor
duck
floatyfloatilla
gellegery
mahlay
makoto
nZDoYBkF_
nilbog
ntty
r00tobo[2]
shiver_
simprelay
solidx66
thetia
u5657
vivid_reader56
zer0bitz
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*