@RN
@RN_
@T3s|4
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
%ardu
%cumlord
%mareki2p
+FreefallHeavens_
+HowardPlayzOfAdmin
+MissTerry
+Onn4l7h
+Sh0ck
+Xeha
+bak83_
+bpb
+hk
+profetikla
+qend-irc2p
+r00tobo
+uop23ip
+wew
+xHarr
Arch
BubbRubb
C341
Danny
DeltaOreo
Irc2PGuest10122
Irc2PGuest21522
Irc2PGuest74664
Irc2PGuest79607
Meow
Over1
SigSegv
St1nt
acetone_
anontor
dr|z3d
duck
fakeirc3e2232
halloy13412
nZDoYBkF
nilbog-
nnm--
not_bob_afk
poriori_
pory
r00tobo[2]
romer
shiver_
simprelay
solidx66
thetia
u5657
woodwose
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*