|
|
Post by kurtiswolf on Jan 18, 2006 16:37:23 GMT
After every reset I get that message the first time I relog my guy who's a secret subrace (Daywalker). I know I'm not the only one getting this message. Will I get my guy bugged if I ignore it and just go ahead and keep playing (rather than relogging to get rid of it).
|
|
|
|
Post by Ralkain on Jan 18, 2006 19:03:20 GMT
After every reset I get that message the first time I relog my guy who's a secret subrace (Daywalker). I know I'm not the only one getting this message. I know someone else who gets this for all their secret races as well and maybe one of his non-secret subraces. Its very annoying, he has to always log in twice to get rid of it. Dave. |
|
|
|
Post by hiryuu on Jan 18, 2006 22:09:37 GMT
Not just the secret ones. A friend of mine is getting that, too, with Arctic Dwarf. It started after the update on the 12th.
|
|
|
|
Post by FunkySwerve on Jan 19, 2006 5:52:14 GMT
Im looking into this. I wouldn't ignore the message, simply because of server lag, though it wouldn't be much.
Funky
|
|
|
|
Post by mishimayukio on Jan 20, 2006 2:57:07 GMT
im getting the same problem on Mishima's Bank #2
|
|
|
|
Post by FunkySwerve on Jan 20, 2006 6:04:47 GMT
Found the problem, fixed next update. Was related to characters in names like apostrophes, and was not new at all, just very bizarre.
Funky
|
|
|
|
Post by Ralkain on Jan 20, 2006 13:00:39 GMT
Found the problem, fixed next update. Was related to characters in names like apostrophes, and was not new at all, just very bizarre. Hmmm, maybe there's multiple reasons then. Since my friend only plays on my other computer. I know for a fact he has no special characters in his names and that the relog message never used to come up for them (only once at character creation). He played them for months with no relog message under normal play, then in December, started getting them on 3-4 of his characters, but none of mine have the problem and I have lots of subraces secret and otherwise. Dave. |
|
|
|
Post by FunkySwerve on Jan 20, 2006 16:01:50 GMT
The characters are not the issue, but they are related. The issue is that the tag field on the character is pretty picky about what goes into it, apparently post-1.66. Why is that a problem? Because the subrace system tries to set the tag equal to bicfile name when it edits the character, and in later checks on the character, checks the tag for the bicfile name. Or used to, until I fixed it last night. Characters like Mishima's Bank 2 should appear as mishima'sbank2.bic, but only the part after the apostrophe was getting added to the field (sbank2.bic). Large character names were getting cutoff abruptly, as well, though I haven't figured out the limit.
Funky
|
|
|
|
Post by Ralkain on Jan 20, 2006 17:05:57 GMT
Characters like Mishima's Bank 2 should appear as Mishima'sbank2.bic, but only the part after the apostrophe was getting added to the field (sbank2.bic). Large character names were getting cutoff abruptly, as well, though I haven't figured out the limit. The names of his characters are short and don't have special characters in them. For instance, his character Onyx gets the message. That's only 4 characters long and has no special characters. Though one of his characters Robin Graves has a first and last name, its getting it too, but perhaps its sticking a space in when making a file. Dave. |
|
|
|
Post by FunkySwerve on Jan 20, 2006 17:30:37 GMT
Again, the problem was not the special characters themselves (or the length of the name), it was the tag field itself, and how it was interpolating those characters. I've just listed some of the reasons the field apparently goes awry, but far from a comprehensive list. Both those characters suffered from the problem I described; Onyx's tag field was blank, and Robin's was simply 'bic'. Though it looks like the problem stopped for Onyx recently, unless I miss my guess. Thats because his Lootable field was not zeroed out anymore. What is more troubling is an underlying problem NOT visible from the player client, the fact that the Lootable field is sometimes zero when it should not be. Still trying to piece that together, but I think the likely cause is the error that was causing deletion and edits of old characters (which was fixed months ago). It occasionally edited the wrong file, which could explain the wrong lootable settings. Once incorrectly set the tag error above would prevent the subraces levelup mechanism from setting the lootable as it was supposed to. The good news is that, bacause of the way the LL system was designed, it catches and stops the problem, unless there's another dimension to the problem I'm not seeing. It's also worth pointing out that this error is not the sole cause of the relog message; taking a secret subrace you don't have the tag for, for instance, seems to result in the message as well.
Funky
|
|
|
|
Post by Ralkain on Jan 20, 2006 17:47:59 GMT
Still trying to piece that together... Ok, I was just trying to make sure you had all the data I had to help you fix it. Dave. |
|
|
|
Post by FunkySwerve on Jan 20, 2006 17:50:41 GMT
Edited the post since your reply in an attempt to clarify the issue.
Funky
|
|
