2014-01-13, 04:54 PM
Good to see such an active thread about this here. I've been trying to get this solved through tickets and the maple community forums without any luck. To contribute some data, I can confirm the following statements:
-Guild and buddy notifications ('character has logged in') do manage to pop up when you attempt logins for other people.
-Characters affected by it, also got affected by error code 38 when accesing monster life from that character.
-Character affected is usually played often and/or main character.
-Shortly before having the character locked down, error code 38 would trigger when entering the cash shop.
-Last action before lockdown (temporal and permanent, see below) was changing channels.
-Character has expanded inventories.
-Character suffered from Error 38 on entering cash shop bug 3 years ago (http://www.southperry.net/showthread.php?t=34911). (Also suffered from the error 38 lockdown during december 2012 - february/march 2013)
-Character was created and used from before the shut down of the MTS.
-Affected accounts are from a foreign region (outside North America and Oceania), created before the "new account area restriction".
The following are plausible:
-Items seem to be the cause. Having items past a certain point trigger the Monster life lockdown, further into it, Cash shop lockdown, and further into the limit, full lockdown, link skills seem to add towards the limit, so exceeding the limit and then removing link skills can also result in lockdown removal temporarilly, as long as the limit is kept. (Unlinking skills didn't seem to help getting unglitched)
-The locked down character is available to relog back for a variable ammount of time (estimated around 2 hours) ONE time, before becoming finally 100% locked down. (I WAS able to get unglitched at two occasions if I recall correctly, but I blame this on patches/server checks)
Can't say that it's good to see some fellow bugged people from before because I don't wish this upon anyone, but at least I'm not alone. I remember Combattente that helped keep the threads alive last year. Weren't you the one who made contact with GM Girasol to take a look at the issue back then?
Good luck to everyone affected!
-Guild and buddy notifications ('character has logged in') do manage to pop up when you attempt logins for other people.
-Characters affected by it, also got affected by error code 38 when accesing monster life from that character.
-Character affected is usually played often and/or main character.
-Shortly before having the character locked down, error code 38 would trigger when entering the cash shop.
-Last action before lockdown (temporal and permanent, see below) was changing channels.
-Character has expanded inventories.
-Character suffered from Error 38 on entering cash shop bug 3 years ago (http://www.southperry.net/showthread.php?t=34911). (Also suffered from the error 38 lockdown during december 2012 - february/march 2013)
-Character was created and used from before the shut down of the MTS.
-Affected accounts are from a foreign region (outside North America and Oceania), created before the "new account area restriction".
The following are plausible:
-Items seem to be the cause. Having items past a certain point trigger the Monster life lockdown, further into it, Cash shop lockdown, and further into the limit, full lockdown, link skills seem to add towards the limit, so exceeding the limit and then removing link skills can also result in lockdown removal temporarilly, as long as the limit is kept. (Unlinking skills didn't seem to help getting unglitched)
-The locked down character is available to relog back for a variable ammount of time (estimated around 2 hours) ONE time, before becoming finally 100% locked down. (I WAS able to get unglitched at two occasions if I recall correctly, but I blame this on patches/server checks)
Can't say that it's good to see some fellow bugged people from before because I don't wish this upon anyone, but at least I'm not alone. I remember Combattente that helped keep the threads alive last year. Weren't you the one who made contact with GM Girasol to take a look at the issue back then?
Good luck to everyone affected!