2011-10-17, 20:47
So, I'm just wondering--given that it's confirmed that this behaviour is due to a change in XBMC, should I wait for this plugin to be updated? Or, instead, is there a temporary patch I should do to a file on my end to get around this issue?