Release | SR Proxy the best way to protect your private server!

Radoslavski · 09/04/2018, 21:14

Quote:

Originally Posted by Isoline*

Hi, i appreciate your feedback, i wish all posts were like this.

if it comes down to just a few stuff, i will make it compatible for BR as long as i have some free time, but you will have to keep testing yourself since i never had interest in BR files.

also, can u be more specific what in-game message isnt working ? the pink gm notice ? or the blue game notice ?
as for the dupe bug, you will have to know how its done, so i can disable it.

Actually it's only sending a notice to the client, which isn't working, if you fix that the other things will work just fine. Even tho the OPCODE is same, seems like the structure is different with BR Files. (the pink GM notice). At least that's the only problem I found till now.

Unlike other filters, which are trying to gather information such as char lvl etc by reading the S-->C packets, I noticed your filter gets most of the information directly from the database which gives an advantage in compatibility since there is almost no change in database of both VSRO and BRFiles.

Isoline* · 09/05/2018, 00:21

Quote:

Originally Posted by Radoslavski

Actually it's only sending a notice to the client, which isn't working, if you fix that the other things will work just fine. Even tho the OPCODE is same, seems like the structure is different with BR Files. (the pink GM notice). At least that's the only problem I found till now.

Unlike other filters, which are trying to gather information such as char lvl etc by reading the S-->C packets, I noticed your filter gets most of the information directly from the database which gives an advantage in compatibility since there is almost no change in database of both VSRO and BRFiles.

well, as for info gathering, it is a question of performance vs. data integrity.

on the one had, getting the info from the server packets is preferable, because we want to avoid slow sql queries.

on the other hand, getting that info from a packet might be in-accurate (Event-Wise, or when it occurs exactly to be more precise), that will lead to data-integrity issues.

so its basically a mixture of of those, some data is more sensitive.
is the blue message in client working for you ?
or its just the pink GM's notice...
im sure its just a different structure thats all no biggie

Radoslavski · 09/05/2018, 03:52

Quote:

Originally Posted by Isoline*

well, as for info gathering, it is a question of performance vs. data integrity.

on the one had, getting the info from the server packets is preferable, because we want to avoid slow sql queries.

on the other hand, getting that info from a packet might be in-accurate (Event-Wise, or when it occurs exactly to be more precise), that will lead to data-integrity issues.

so its basically a mixture of of those, some data is more sensitive.
is the blue message in client working for you ?
or its just the pink GM's notice...
im sure its just a different structure thats all no biggie

I further tested the Filter with Black Rogue files and found that both Pink GM Notice and Blue Notification are crashing the client.

Also captured the packets which are crashing the client.

Code:

===============================
==== THIS ONE IS A BLUE NOTIFICATION ====
===============================
[S -> C][300C]


1C 0C 01 15 00 55 49 49 54 5F 53 54 54 5F 47 4C   .....UIIT_STT_GL


4F 42 41 4C 5F 44 45 4C 41 59                     OBAL_DELAY......


================================
=== AND THIS ONE IS THE PINK GM NOTICE ===
================================
[S -> C][3026]


07 17 00 54 45 53 54 49 4E 47 20 50 49 4E 4B 20   ...TESTING.PINK.


47 4D 20 4E 4F 54 49 43 45 21                     GM.NOTICE!......

I also tested the same PINK GM message which is sent directly from the server without using the filter so you can compare both, and here it is.

Code:

=========================================
=== THIS IS THE CORRECT PACKET FOR BlackRogue Client ===
=========================================
[S -> C][3026]
07                                                ................
17 00                                             ................
54 00 45 00 53 00 54 00 49 00 4E 00 47 00 20 00   T.E.S.T.I.N.G...
50 00 49 00 4E 00 4B 00 20 00 47 00 4D 00 20 00   P.I.N.K...G.M...
4E 00 4F 00 54 00 49 00 43 00 45 00 21 00         N.O.T.I.C.E.!...

As you can see from this comparsion, the operation code is same but the packet has a different structure.

Even if you don't fix the problem, as a workaround you can just add an option to disable notifications and notices.

B1Q · 09/05/2018, 16:39

you need to send Unicode instead of Ascii for string to work with the BR client
that's for isoline btw

TrashBag · 09/05/2018, 17:45

free ver 500 players limit?

Isoline* · 09/05/2018, 23:32

Quote:
Originally Posted by Radoslavski
I further tested the Filter with Black Rogue files and found that both Pink GM Notice and Blue Notification are crashing the client.

Also captured the packets which are crashing the client.
Code:
===============================
==== THIS ONE IS A BLUE NOTIFICATION ====
===============================
[S -> C][300C]


1C 0C 01 15 00 55 49 49 54 5F 53 54 54 5F 47 4C   .....UIIT_STT_GL


4F 42 41 4C 5F 44 45 4C 41 59                     OBAL_DELAY......


================================
=== AND THIS ONE IS THE PINK GM NOTICE ===
================================
[S -> C][3026]


07 17 00 54 45 53 54 49 4E 47 20 50 49 4E 4B 20   ...TESTING.PINK.


47 4D 20 4E 4F 54 49 43 45 21                     GM.NOTICE!......
I also tested the same PINK GM message which is sent directly from the server without using the filter so you can compare both, and here it is.
Code:
=========================================
=== THIS IS THE CORRECT PACKET FOR BlackRogue Client ===
=========================================
[S -> C][3026]
07                                                ................
17 00                                             ................
54 00 45 00 53 00 54 00 49 00 4E 00 47 00 20 00   T.E.S.T.I.N.G...
50 00 49 00 4E 00 4B 00 20 00 47 00 4D 00 20 00   P.I.N.K...G.M...
4E 00 4F 00 54 00 49 00 43 00 45 00 21 00         N.O.T.I.C.E.!...
As you can see from this comparsion, the operation code is same but the packet has a different structure.

Even if you don't fix the problem, as a workaround you can just add an option to disable notifications and notices.

I will still need a test BR server to have a look around

Quote:

Originally Posted by B1Q

you need to send Unicode instead of Ascii for string to work with the BR client
that's for isoline btw

Thanks buddy.

Quote:

Originally Posted by TrashBag

free ver 500 players limit?

There is no concurrent players limitation whatsoever (in any of the versions).

kotsh · 09/10/2018, 06:08

is the last ver free for ever ?

Isoline* · 09/11/2018, 11:43

Quote:

Originally Posted by kotsh

is the last ver free for ever ?

of course, it has always been like that.

kotsh · 09/12/2018, 06:35

Thank you bro
but it without pc limit
right ?

SubZero** · 09/12/2018, 15:31

Quote:

Originally Posted by kotsh

Thank you bro
but it without pc limit
right ?

of course, it premium feature as i think

asksro · 09/12/2018, 15:52

Do you support Chinese?

Radoslavski · 09/12/2018, 15:52

Quote:

Originally Posted by asksro

Do you support Chinese?

You mean CSRO-R files?

Isoline* · 09/12/2018, 16:03

Quote:

Originally Posted by asksro

Do you support Chinese?

What do you mean?

Quote:

Originally Posted by Radoslavski

You mean CSRO-R files?

+1

~~toto5555~~ · 09/19/2018, 14:48

can i ask u something , old version have bug , dc etc? right!

thebigbody · 09/19/2018, 19:22

Does disable job mode usage disable the job mode itself so noone can even wear job suite ?