loginPinCode in bRO.pm and twRO.pm!?Move to receive/send.pm?

[Kaspy]

I noticed that in this twRO using exactly the same system that the PIN used in bRO...

Would not it be better to move everything receive.pm and send.pm?

[kLabMouse]

If it uses new Packet. Then Shure. But if it's working on top of Existing code, then no.

[Maple]

cRO has PIN code too.
Using an Androin or iOS app lock to generate random 6-digits ligin PIN code.
Would rather to have a sample.

[Kaspy]

cRO has PIN code too.
Using an Androin or iOS app lock to generate random 6-digits ligin PIN code.
Would rather to have a sample.

This system seems to be different from the PIN used in bRO and twRO

[DrKN]

Not sure about the loginPinCode right now because twRO just updated to a new version.

[Kaspy]

Implement in r8518 by iMikeLance

[kLabMouse]

Implement in r8518 by iMikeLance

You guy's made ST0 unusable by others. With a few ST0 updates. (like the one that affected iRO and pRO ST).
Please, if it's something bound to packet ID's (like the one that affected iRO), please keep it out of ST0. Or check if OpenKore works on other Servers too.

ST0 is a core for all ST. So keep it clean as much as possible.

[iMikeLance]

Implement in r8518 by iMikeLance

You guy's made ST0 unusable by others. With a few ST0 updates. (like the one that affected iRO and pRO ST).
Please, if it's something bound to packet ID's (like the one that affected iRO), please keep it out of ST0. Or check if OpenKore works on other Servers too.

ST0 is a core for all ST. So keep it clean as much as possible.

What's wrong with the latest commit?

EDIT: It wasn't any of our commits that caused that. Anyway, fixed it for iRO.

Revision: 8520
Author: marcelofoxes
Date: quinta-feira, 25 de abril de 2013 00:53:33
Message:
* fixed revision 8485 bug that affected iRO (and probably pRO too)

----
Modified : /openkore/trunk/src/Network/Receive/ServerType0.pm