/legit command on PSO (guide)

[BlueCrab]

So, with your Kabanda, I am able to reproduce the bug on my test server, so I'm looking into how to fix it now.

[BlueCrab]

Stupid bug, simple to fix. r198 fixes the bug. All that was wrong is that Leilla was in the wrong place in my list, so things weren't getting set quite right. Once dctalk updates the server, the bug should be gone (remember, I don't have access to do that -- I just write the code, so it isn't gone just yet on the server as it stands now).

I have to say that I'm pretty pleased that this is really the first time something stupid like this has crept up in the legit checker. Considering how quickly I wrote the code (most of the work was just parsing the config), and the fact that this is the first real time that something legit was being flagged by accident.

The rest of this is a bit of a rant, and I don't want to come across as mean in any of it by any means... Fair warning.

Anyway, remember Sylverant is not a finished product by any means, and its still largely in a testing state (heck, I don't even know that I'd consider it "beta" quality at all). There are bound to be bugs here and there, and the only way to find them is to make them happen. Not to be mean, but if you don't want to play on a testing server, play over at schtserv instead. Their server is a lot more mature, but also lacks features compared to Sylverant (such as the whole idea of a legit checker). Suggesting that a feature be disabled in the server because one bug is found with it is simply ridiculous. If you don't want to be constrained by /legit mode (and thus any bugs that may creep up), don't join /legit games or ask people to not set /legit in the first place. Especially considering that /legit is completely optional (its not forced by any means -- the team leader simply sets the flag), and it can't cause any actual harm to your character (it simply gracefully disconnects you, letting your client save as normal).

[TeamXlink]

Stupid bug, simple to fix. r198 fixes the bug. All that was wrong is that Leilla was in the wrong place in my list, so things weren't getting set quite right. Once dctalk updates the server, the bug should be gone (remember, I don't have access to do that -- I just write the code, so it isn't gone just yet on the server as it stands now).

I have to say that I'm pretty pleased that this is really the first time something stupid like this has crept up in the legit checker. Considering how quickly I wrote the code (most of the work was just parsing the config), and the fact that this is the first real time that something legit was being flagged by accident.

The rest of this is a bit of a rant, and I don't want to come across as mean in any of it by any means... Fair warning.

Anyway, remember Sylverant is not a finished product by any means, and its still largely in a testing state (heck, I don't even know that I'd consider it "beta" quality at all). There are bound to be bugs here and there, and the only way to find them is to make them happen. Not to be mean, but if you don't want to play on a testing server, play over at schtserv instead. Their server is a lot more mature, but also lacks features compared to Sylverant (such as the whole idea of a legit checker). Suggesting that a feature be disabled in the server because one bug is found with it is simply ridiculous. If you don't want to be constrained by /legit mode (and thus any bugs that may creep up), don't join /legit games or ask people to not set /legit in the first place. Especially considering that /legit is completely optional (its not forced by any means -- the team leader simply sets the flag), and it can't cause any actual harm to your character (it simply gracefully disconnects you, letting your client save as normal).

Your server is a lot more stable compared to schtserv, I expected to get FSOD's when I played there, on your server I expect and receive, the closest equivalent of a Sega Phantasy Star Dreamcast Server, I haven't played on one, but by the quality of your server, I don't know how it could be much if any better then yours.

[Saffo]

Anyway, remember Sylverant is not a finished product by any means, and its still largely in a testing state (heck, I don't even know that I'd consider it "beta" quality at all). There are bound to be bugs here and there, and the only way to find them is to make them happen. Not to be mean, but if you don't want to play on a testing server, play over at schtserv instead. Their server is a lot more mature, but also lacks features compared to Sylverant (such as the whole idea of a legit checker). Suggesting that a feature be disabled in the server because one bug is found with it is simply ridiculous. If you don't want to be constrained by /legit mode (and thus any bugs that may creep up), don't join /legit games or ask people to not set /legit in the first place. Especially considering that /legit is completely optional (its not forced by any means -- the team leader simply sets the flag), and it can't cause any actual harm to your character (it simply gracefully disconnects you, letting your client save as normal).

i havent suggested to disable the checker but to disable the kick....
you said yourself it s in testing stage and thats why i reccomended you to remove it....i wouldnt otherwise, that would make the life easyer to the testers...to use your own words, the only way to find bugs is to let em happen and it s a lot easyer to do so if you don t get kicked every time. i went through it first hand since it took a while to figure out what was causing the problem. not to mention the synch loss for all my set of mags after each kick. That said i gave the advice not even thinking to myself since i wouldnt use the checker regardeless, (i play mainly alone and thus i don t need). Mayby you don t know it, but it s a while already that i play in sylverant and i find it wonderfull so i have no complains really and all of my advices were to help you guys out, if you dont think my advice is usefull just dont follow it. The "dont play here if you dont like" thinghy don t have much sense in this case.

[BlueCrab]

i havent suggested to disable the checker but to disable the kick....
you said yourself it s in testing stage and thats why i reccomended you to remove it....i wouldnt otherwise, that would make the life easyer to the testers...to use your own words, the only way to find bugs is to let em happen and it s a lot easyer to do so if you don t get kicked every time. i went through it first hand since it took a while to figure out what was causing the problem. not to mention the synch loss for all my set of mags after each kick. That said i gave the advice not even thinking to myself since i wouldnt use the checker regardeless, (i play mainly alone and thus i don t need). Mayby you don t know it, but it s a while already that i play in sylverant and i find it wonderfull so i have no complains really and all of my advices were to help you guys out, if you dont think my advice is usefull just dont follow it. The "dont play here if you dont like" thinghy don t have much sense in this case.

I've been in kindof a strange mood lately, and hence why I said it was a rant, and I didn't want it to seem mean. Anyway, the whole server is in testing stages, and kicking only happens when /legit has already been enabled in a game. Perhaps it would be a good idea for me to VISIBLY flag games that have legit set on them at the lobby counter so people who don't like it can just avoid them entirely.

That said, if the kick for illegitimacy is removed, what is the point of the legit checker in the first place? That's the part of the whole idea of removing it that makes the least sense to me. Without that part, it makes the whole legit system entirely useless. If there's no teeth, people will ignore it, just like they did on schtserv. That said, if for some reason they wanted to disable the kick here, its not particularly hard to do so in the code. It just kinda defeats the whole purpose of the checker in the first place.

I apologize if you thought I was attacking you, as that was not my intent. I appreciate the fact that you helped nail down that bug by providing what I needed to trigger and thus find a fix for it.

Your server is a lot more stable compared to schtserv, I expected to get FSOD's when I played there, on your server I expect and receive, the closest equivalent of a Sega Phantasy Star Dreamcast Server, I haven't played on one, but by the quality of your server, I don't know how it could be much if any better then yours.

Thanks for the kind words here. However, there are still plenty of bugs out there in the code that still cause people to FSOD randomly (most of which I can never trigger myself). That said, FSODs used to happen all the time on Sega's server too. In fact, I lost many an item to the FSOD back in the day. That said, I have not once managed to FSOD myself on Sylverant...

[Saffo]

i agree with you, the kick is a good feature. i like the idea to have it on a finished product, but at this stage i d rather have something that just notify me for testing purpose.

i just felt a bit involved in this checker cause kireek sent me quite a few mails asking what was legit and what not so it was a bit like i was part of it and i tought to give a hand by digging in that bug.

[K_I_R_E_E_K]

Yes, you and cathy gave me some info that was actually usefull, i still had to find some lose ends by myself but i thank you both for helping me.

Yes, there should be somekind of information on the game, maybe in the game info on the bottom right corner, it currently shows the player or players inside and the level, maybe you can add extra info in that spot. (even if it requires the user to press a button to switch info)

The kick should be enabled, i know a way to bypass it even with it enabled, but ppl won't do a legit game just to trick others i guess, so no worries for now.
I think we won't find more bugs, we may find some false positives, but i doubt it, the odds are really low.

Regarding FSODs on schthack, they blamed the autoconnect disk, because while it worked fine with other dreamcast players, it didn't go well with pc players, so if a PC player joins then a FSOD is most likely, here however that doesn't happen, i have joined several games where the player is a autoconnect disk dc player and nothing happened, not even a FSOD.
Now at schthack FSODs are very rare and that's because most players are on the PC platform

[Macabre]

Yay for finding and figuring out how to fix the glitch

Slightly relieved that it was just mags and no corrupted / hacked items some how materialized into my possession.

[K_I_R_E_E_K]

Bluecrab is human just like all of us, just remember that next time the error may be on my part (i hope not)
Quite a fast fix, i thank him.