next »

[gabarram]

Hi people

I´ve seen in echelon that sometimes a player ( as it happened to me, and I´ve never changed my nick, I swear) is shown as having many aliases ( which are the nicks of other players one has been playing with), the guid is the same, but it appears as if one has changed the nick many times playing in the same PC.
It´s different to the case where a player has different guids meaning he has played in different PCs, and perhaps changed the nick for unknown causes.

I´m using echelon v1 and B3 1.5.0b2

Thanks

[Courgette]

could you empty the alias table from your mysql database and keep a close eye on it. Tell us how quickly you notice new errors with aliases.
Also, try to find a b3.log showing B3 saving a wrong alias (this can be hard to find) as it would make clear what's going wrong

[gabarram]

could you empty the alias table from your mysql database and keep a close eye on it. Tell us how quickly you notice new errors with aliases.
Also, try to find a b3.log showing B3 saving a wrong alias (this can be hard to find) as it would make clear what's going wrong

I´m sorry, I have a lot of info stored  and I cannot risk losing it,or worse, messing it all up. I was just asking for hints, since this issue disturbed me. But echelon is in general working fine, and I fear I could make a total disaster for something that is not so serious.

Thanks Courgette for the reply.

[MordyT]

I can try this.

We have had this issue since day one on our cod4 server... I think in the end someone mentioned that if someone connected while game was changing maps in a slot someone else just left, it would mark it as a aliases.

Regardless, I will empty the aliases table for my name, play, and test my theory...

[82ndAB.Bravo17]

I managed to see what is causing at least some of the false aliases are from pb giving the wrong slot number, it happened tonight and pb had dropped the 7 from slot 17 and so b3 saw it as slot 1 and gave the person in slot 17 the alias of the person in slot 1, who had just joined.

[gabarram]

I managed to see what is causing at least some of the false aliases are from pb giving the wrong slot number, it happened tonight and pb had dropped the 7 from slot 17 and so b3 saw it as slot 1 and gave the person in slot 17 the alias of the person in slot 1, who had just joined.

As 82nd states, this is happening to him because of pb, but what is to be said in the case of mw2 which has no punkbuster?
Could it be a cod issue, not B3´s?

Any approach/test to overcome this issue is appreciated.

Thank you xlr8or for unlocking this topic.

[82ndAB.Bravo17]

I think I have fixed it for PB enabled servers, I was really surprised at how many random errors were appearing in the players list!

For your COD6 server, could you post the results of a status command, it should appear in your b3 log file if you have the log_level low enough.

If they appear in slot order then we should be able to apply the same test to spot out of order slots and ignore the associated player details if they appear.

[gabarram]

I think I have fixed it for PB enabled servers, I was really surprised at how many random errors were appearing in the players list!

For your COD6 server, could you post the results of a status command, it should appear in your b3 log file if you have the log_level low enough.

If they appear in slot order then we should be able to apply the same test to spot out of order slots and ignore the associated player details if they appear.

Thanks for the suggestion!

I´ll do it asap and post results, but, what do yuou mean by "log level low enough".
I´ve set it to 9, what log_level number do you suggest?

[MordyT]

I think 8 is what we debugged CoD4 with. 8 shows the status results where 9 does not.

[gabarram]

I think 8 is what we debugged CoD4 with. 8 shows the status results where 9 does not.

Well´I´m sorry for taking so long to reply, but this is it

http://pastebin.com/QM8ZQmZ5

B3 version 1.7.1
log_level 8

I hope this helps.

Thank you very much

[82ndAB.Bravo17]

If you want to check out the q3a\abstractParser.py here

https://www.github.com/82ndab-Bravo17/big-brother-bot

It may fix at least some of the phantom aliases - the PB version has done so for us.

If you try it, please check that all players are still authenticated as usual, as I don't have a non PB server to test it on.

If you do get slot number errors there will be a message in the log

"Duplicate or Incorrect slot number - client ignored  #  lastslot"


You should then be able to check the slot numbers in the previous status result to see if there was indeed an error, they should go up in order.



You can also get an idea of how many random errors you are getting in status by looking at the ipaliases - it's fairly easy to spot IP's that are just a missing digit away from each other.

[gabarram]

Thank you for the fix, I´ll be trying this.
Greetingz

[Mariodu62]

Hi,

Just a question, Not for Windows B3 i suppose.

Thx

[MordyT]

Hi,

Just a question, Not for Windows B3 i suppose.

Thx

Probably not until the next version, since python files are normally already compiled.