Welcome!

Join our community of MMO enthusiasts and game developers! By registering, you'll gain access to discussions on the latest developments in MMO server files and collaborate with like-minded individuals. Join us today and unlock the potential of MMO server development!

Join Today!

v1.5.5 Client Downgraded and Translated

Elite Diviner
Joined
Jan 5, 2017
Messages
475
Reaction score
345
I'm not sure, but I think there was a new celestone introduced... I doubt the old gs would know to use them... The celestones look the same, but have a different ID, I think peeps on the new public server was feeding there genies with them... :)
 
Elite Diviner
Joined
Jan 5, 2017
Messages
475
Reaction score
345
Activating reflection anywhere (aka Open Reflection) tis right and also tis old news as it was introduced somewhere around 2015...

Wrechid - v1.5.5 Client Downgraded and Translated - RaGEZONE Forums


As for crashing, I mentioned from the start that this was not meant to host publicly or for production, but as something to play and learn from... If I remember correctly, the problem was due to Dynamicobjects.data... I do not plan on continuing support to this as I have moved beyond it... My server is using this same client as a base, but is now downgraded from v1.6.2... You are more than welcome to download it, and do what you want...

 
0, 1, 1, 2, 3, 5, 8, 13,
Joined
Sep 8, 2011
Messages
601
Reaction score
168
Your most recent client.
Thanks to you Wrechid for providing client and server and great ideas to work on.
I had a problem on the a91 map, Tremolos, where after 1 minute the client side was server error.
The server was not affected, only client.
Throwing in the region.clt from PWI recent files squashed the server error, but brought map data out of phase.
So it was region.
Looking at your excellent conversions, they are perfect server side.
I found the difference in region.clt, and on modification it runs perfect now with no annoying map data out of phase, no server error.
For anyone experiencing this problem, here is the modified region.clt for a91.
 

Attachments

You must be registered for see attachments list
Last edited:
0, 1, 1, 2, 3, 5, 8, 13,
Joined
Sep 8, 2011
Messages
601
Reaction score
168
Atm i've just finished exploring the Loma maps and new pwi maps added, and adding all the other Loma maps now, just to squeeze Loma for all it's goodness.
Then adding mobs after everything is added.
Thanks for the heads up, i'll have a look after maps sorted and post anything positive i find.

server error -cont'd
ok, i have found something interesting, in part a correction on my earlier solution.
I had a problem with Lothranis and Mormagannon server error.
Nothing seemed to be able to fix.
Region on server and client matched precisely.
In taking out the regions within the region file client side, it did work, which only left the trans remaining.
Adding back slowly the regions until the error was produced, left [STRIKE]a specific part of[/STRIKE] the regions that were causing the errors, in hell and heaven.
I would guess this method would work anywhere else the server error is present, but the server and client regions are perfect and should work!.
Look i'll demonstrate.
Here is the un-edited and original 155 region.clt for a21 on client.
Code:
//  Element region file (client version)

version  5
1436092305

[COLOR="#0000FF"][region]
"白莲居"
1  13
-656.758606  203.303116  520.937439
-694.804993  205.453812  511.817566
-709.906128  201.005386  477.728455
-702.443726  198.617371  419.313232
-673.236206  202.622086  371.329285
-589.785828  200.824127  371.409546
-516.766785  187.151276  375.501801
-481.753204  197.472717  416.697815
-479.655426  188.910675  442.262085
-497.990448  191.374176  502.763580
-527.198059  197.000198  534.057434
-606.475891  187.096848  538.229980
-656.546143  203.200211  520.916565[/COLOR]

[trans]
123  121  0
235.114166, 189.778046, 260.322571
4.000000, 4.000000, 4.000000
330.265015, 610.000000, -264.100006

[COLOR="#0000FF"][region]
"清幽居"
1  57
835.993652  205.315460  -359.156616
827.829224  203.840012  -357.852600
814.950562  201.805099  -352.917786
799.920654  198.723022  -348.705139
779.445313  194.030899  -345.214661
764.645996  191.841354  -342.807434
757.746521  191.331940  -344.251770
744.145691  193.080597  -348.103333
732.229980  193.096085  -353.399231
720.474182  193.096085  -362.256134
707.104980  189.730591  -376.699463
700.966553  190.622009  -390.848755
698.679688  192.714401  -400.942261
698.559326  194.960785  -416.228119
702.170166  194.387512  -425.736633
704.577393  192.999222  -436.820892
705.299561  191.717957  -451.866028
704.697754  196.272797  -479.173584
702.290527  194.308441  -505.003296
699.401855  197.371033  -531.792908
694.828125  196.383942  -553.369507
695.550293  192.667465  -569.573792
699.040771  191.484436  -586.149841
705.179199  191.484833  -599.492249
714.687683  191.758636  -609.602600
731.052856  195.515381  -620.642090
746.377136  196.009903  -625.476379
766.158997  192.649918  -628.605774
790.765991  193.597580  -633.660950
807.811646  199.189987  -635.707092
823.005188  203.998322  -637.031067
824.544434  193.084717  -606.638611
826.174622  192.277832  -604.263855
835.803467  193.279495  -594.882629
848.686401  196.459442  -588.411499
855.546997  197.507751  -584.078491
862.933228  199.142853  -576.255005
867.747681  201.900162  -564.958740
868.108704  195.809418  -546.467590
870.275208  196.271530  -537.099487
876.774719  207.849487  -524.318970
882.449097  217.137177  -516.502441
886.300659  215.710037  -506.495544
887.744995  200.164902  -488.367889
887.143188  206.984695  -469.833862
881.606567  194.681503  -451.187805
879.319763  197.921936  -443.648987
872.098083  201.586136  -433.418304
862.348877  194.596359  -426.317017
854.164307  189.530701  -415.387146
853.923584  190.027863  -410.211639
859.339844  189.645584  -399.632172
859.219482  189.895966  -393.240936
855.247559  195.281219  -383.250977
847.039673  194.142517  -373.821472
841.382690  194.991241  -366.755798
835.966431  206.632660  -359.173035[/COLOR]

[COLOR="#0000FF"][region]
"飘渺城"
1  9
341.699280  213.943741  -775.650146
333.762817  234.015686  -780.639038
335.280640  269.280762  -796.129517
340.609802  279.596924  -803.379333
343.952911  288.413849  -808.363525
365.984802  241.071457  -791.717529
357.616821  211.831741  -782.554321
348.267761  206.534149  -775.802979
341.699280  213.943741  -775.650146[/COLOR]

[trans]
1  121  0
866.498535, 219.221344, -631.667603
12.500000, 12.500000, 12.500000
-2824.729004, 379.201996, 3091.210938

[trans]
172  121  89
353.900208, 433.181061, -796.567261
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998

[trans]
173  121  89
350.460907, 433.181427, -798.920898
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998

[trans]
174  121  89
355.175537, 433.181427, -794.697144
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998

[trans]
175  121  89
352.290466, 433.176910, -797.966919
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998
The file below is the true fix, for a21.
Code:
//  Element region file (client version)

version  5
1436092305

[trans]
123  121  0
235.114166, 189.778046, 260.322571
4.000000, 4.000000, 4.000000
330.265015, 610.000000, -264.100006

[trans]
1  121  0
866.498535, 219.221344, -631.667603
12.500000, 12.500000, 12.500000
-2824.729004, 379.201996, 3091.210938

[trans]
172  121  89
353.900208, 433.181061, -796.567261
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998

[trans]
173  121  89
350.460907, 433.181427, -798.920898
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998

[trans]
174  121  89
355.175537, 433.181427, -794.697144
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998

[trans]
175  121  89
352.290466, 433.176910, -797.966919
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998
This same worked for a22.
I'm guessing it will probably work for all maps that should work, but throw the server error client side.
I didn't remove the offender on reg.sev side, but did remove on reg.clt (client) side, everything working as it should.

Regarding a91, wonderland, some questions.
What are the regions for anyway?, i mean, there's no mobs in the map...
Why do they even have safe zones in a91?.
For now i have removed them completely, because it serves no point, that i can understand.
It leaves only this behind
Code:
//  Element region file (client version)

version  5
1505359255

[trans]
191  191  0
-195.721832, 33.310020, -253.569565
1.000000, 5.000000, 1.500000
-187.175003, 32.113998, -242.772003
No more errors.
[STRIKE]One more edit.
It looks to me as if some of the coordinates could be overlapping?.
Could an overlap cause the error?
In swapping one lot for the other in a22, it seems to confirm that maybe this is the problem.
Lets look at [/STRIKE]a22.
Fix tested and works
Code:
//  Element region file (client version)

version  5
1411630743

[trans]
124  122  0
301.704132, 294.794281, 525.119507
25.000000, 25.000000, 30.000000
-394.112000, 164.000000, -466.688995

[trans]
1  122  0
-708.053894, 259.008392, -489.858978
15.000000, 10.000000, 15.000000
-2824.729004, 379.201996, 3091.210938

Edit, it turned out on server reboot, the only way was to completely remove the regions.
I'd love to know why the regions on these two maps are producing server error, got me stumped, but at least this is a work around until a better solution is found.
Post edited.
 

Attachments

You must be registered for see attachments list
Last edited by a moderator:
Initiate Mage
Joined
Jul 6, 2020
Messages
11
Reaction score
0
Im using your files and having trouble with a97 map. Mobs just disappear after going through certain coordinates... they spawn and then disappear.

Look at this image:

NPCs stay there, tho. The problem is only happening with monsters.

Can you help me please??
 
Elite Diviner
Joined
Jun 26, 2013
Messages
486
Reaction score
91
If the hmap and rmap for a97 are not allowing for correct monster movement inside the dungeon you must re-generate it using a tool which is capable of doing so.

Your exact symptoms are there are certain parts of the hmap generated where it is mapped under the ground on the terrain instead of the .bmd and thus the mob is trying to walk on the terrain under the dungeon instead of the .bmd itself.

@Steve Langley
 
Last edited:
Initiate Mage
Joined
Jul 6, 2020
Messages
11
Reaction score
0
If the hmap and rmap for a97 are not allowing for correct monster movement inside the dungeon you must re-generate it using a tool which is capable of doing so.

@Steve Langley

Can sMAPtool do the job? I know it has some heightmap editing, but I am not sure how it should be modified in order to fix this bug.

I've just noticed that flying mobs do not disappear, but ground mobs do.

Screenshot:

----- UPDATE

LOL, mobs are just falling down... they re below ground

Screenshot:

Now I have to figure out how to fix those .hmap files... that looks hard
 
Last edited:
Initiate Mage
Joined
Jul 6, 2020
Messages
11
Reaction score
0
.hmap has to be correctly generated. sMAP won't be able to do it.

I've just noticed that 11 out of 12 .hmap files of a97 map are all black (0 height I guess) , except for one (print screen below)

Screenshot:

It seems I will have a lot of work to do then to generate those .hmap files correctly, omg.

Anyways, thanks a lot, at least I found the reason for this problem :)
 
Last edited:
Joined
Feb 26, 2013
Messages
62
Reaction score
88
This is not due to hmap. Its caused by dhmap being wrong. You need to create the dhmap and rmap properly in order for mobs to know where they are allowed to walk.

Wrechid - v1.5.5 Client Downgraded and Translated - RaGEZONE Forums
 
Initiate Mage
Joined
Jul 6, 2020
Messages
11
Reaction score
0
This is not due to hmap. Its caused by dhmap being wrong. You need to create the dhmap and rmap properly in order for mobs to know where they are allowed to walk.

Wrechid - v1.5.5 Client Downgraded and Translated - RaGEZONE Forums

Hi, I've just pust a .rmap file which is all white (Enter: True) and ALL the mobs from this dungeon fell down. If I put it black they wont be able to walk I guess. How can I edit dhmap?
 
Elite Diviner
Joined
Jun 26, 2013
Messages
486
Reaction score
91
yeah dhmap is what I meant sorry typo :dancemental:

dhmap is the file that tells which heights the mobs need to walk at for each vertex of the mob movement grid of the map
 
Elite Diviner
Joined
Jun 26, 2013
Messages
486
Reaction score
91
I've just seen this post and I really liked it. It would be very useful since there is no tool for creating rhmap/dhmap in PW.

Are you still developing it? I really need this tool.
I don't know how to edit .dhmap file. It just opens an encoded file.

Everything besides GFX is currently displayable / editable with the tool. This includes technical stuff such as dhmap / rhmap which is the invisible grid telling mobs which heights they can walk at and which they cant. When I used it it has two modes (Dungeon or Regular) where it considers the BMD's as the walk-able area and then the other mode where it considers terrain the walk able area for automatic generation and has a section where you can fine tune and adjust it by hand to include certain bmd's as walk-able even in the regular mode of terrain etc.




other than his tool I can't think of anything else that would be capable of editing it correctly. Other than official PW CN tools which currently aren't compile-able.
 
Joined
Oct 14, 2009
Messages
5,493
Reaction score
2,299
server error -cont'd
ok, i have found something interesting, in part a correction on my earlier solution.
I had a problem with Lothranis and Mormagannon server error.
Nothing seemed to be able to fix.
Region on server and client matched precisely.
In taking out the regions within the region file client side, it did work, which only left the trans remaining.
Adding back slowly the regions until the error was produced, left [STRIKE]a specific part of[/STRIKE] the regions that were causing the errors, in hell and heaven.
I would guess this method would work anywhere else the server error is present, but the server and client regions are perfect and should work!.
Look i'll demonstrate.
Here is the un-edited and original 155 region.clt for a21 on client.
Code:
//  Element region file (client version)

version  5
1436092305

[COLOR="#0000FF"][region]
"白莲居"
1  13
-656.758606  203.303116  520.937439
-694.804993  205.453812  511.817566
-709.906128  201.005386  477.728455
-702.443726  198.617371  419.313232
-673.236206  202.622086  371.329285
-589.785828  200.824127  371.409546
-516.766785  187.151276  375.501801
-481.753204  197.472717  416.697815
-479.655426  188.910675  442.262085
-497.990448  191.374176  502.763580
-527.198059  197.000198  534.057434
-606.475891  187.096848  538.229980
-656.546143  203.200211  520.916565[/COLOR]

[trans]
123  121  0
235.114166, 189.778046, 260.322571
4.000000, 4.000000, 4.000000
330.265015, 610.000000, -264.100006

[COLOR="#0000FF"][region]
"清幽居"
1  57
835.993652  205.315460  -359.156616
827.829224  203.840012  -357.852600
814.950562  201.805099  -352.917786
799.920654  198.723022  -348.705139
779.445313  194.030899  -345.214661
764.645996  191.841354  -342.807434
757.746521  191.331940  -344.251770
744.145691  193.080597  -348.103333
732.229980  193.096085  -353.399231
720.474182  193.096085  -362.256134
707.104980  189.730591  -376.699463
700.966553  190.622009  -390.848755
698.679688  192.714401  -400.942261
698.559326  194.960785  -416.228119
702.170166  194.387512  -425.736633
704.577393  192.999222  -436.820892
705.299561  191.717957  -451.866028
704.697754  196.272797  -479.173584
702.290527  194.308441  -505.003296
699.401855  197.371033  -531.792908
694.828125  196.383942  -553.369507
695.550293  192.667465  -569.573792
699.040771  191.484436  -586.149841
705.179199  191.484833  -599.492249
714.687683  191.758636  -609.602600
731.052856  195.515381  -620.642090
746.377136  196.009903  -625.476379
766.158997  192.649918  -628.605774
790.765991  193.597580  -633.660950
807.811646  199.189987  -635.707092
823.005188  203.998322  -637.031067
824.544434  193.084717  -606.638611
826.174622  192.277832  -604.263855
835.803467  193.279495  -594.882629
848.686401  196.459442  -588.411499
855.546997  197.507751  -584.078491
862.933228  199.142853  -576.255005
867.747681  201.900162  -564.958740
868.108704  195.809418  -546.467590
870.275208  196.271530  -537.099487
876.774719  207.849487  -524.318970
882.449097  217.137177  -516.502441
886.300659  215.710037  -506.495544
887.744995  200.164902  -488.367889
887.143188  206.984695  -469.833862
881.606567  194.681503  -451.187805
879.319763  197.921936  -443.648987
872.098083  201.586136  -433.418304
862.348877  194.596359  -426.317017
854.164307  189.530701  -415.387146
853.923584  190.027863  -410.211639
859.339844  189.645584  -399.632172
859.219482  189.895966  -393.240936
855.247559  195.281219  -383.250977
847.039673  194.142517  -373.821472
841.382690  194.991241  -366.755798
835.966431  206.632660  -359.173035[/COLOR]

[COLOR="#0000FF"][region]
"飘渺城"
1  9
341.699280  213.943741  -775.650146
333.762817  234.015686  -780.639038
335.280640  269.280762  -796.129517
340.609802  279.596924  -803.379333
343.952911  288.413849  -808.363525
365.984802  241.071457  -791.717529
357.616821  211.831741  -782.554321
348.267761  206.534149  -775.802979
341.699280  213.943741  -775.650146[/COLOR]

[trans]
1  121  0
866.498535, 219.221344, -631.667603
12.500000, 12.500000, 12.500000
-2824.729004, 379.201996, 3091.210938

[trans]
172  121  89
353.900208, 433.181061, -796.567261
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998

[trans]
173  121  89
350.460907, 433.181427, -798.920898
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998

[trans]
174  121  89
355.175537, 433.181427, -794.697144
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998

[trans]
175  121  89
352.290466, 433.176910, -797.966919
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998
The file below is the true fix, for a21.
Code:
//  Element region file (client version)

version  5
1436092305

[trans]
123  121  0
235.114166, 189.778046, 260.322571
4.000000, 4.000000, 4.000000
330.265015, 610.000000, -264.100006

[trans]
1  121  0
866.498535, 219.221344, -631.667603
12.500000, 12.500000, 12.500000
-2824.729004, 379.201996, 3091.210938

[trans]
172  121  89
353.900208, 433.181061, -796.567261
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998

[trans]
173  121  89
350.460907, 433.181427, -798.920898
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998

[trans]
174  121  89
355.175537, 433.181427, -794.697144
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998

[trans]
175  121  89
352.290466, 433.176910, -797.966919
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998
This same worked for a22.
I'm guessing it will probably work for all maps that should work, but throw the server error client side.
I didn't remove the offender on reg.sev side, but did remove on reg.clt (client) side, everything working as it should.

Regarding a91, wonderland, some questions.
What are the regions for anyway?, i mean, there's no mobs in the map...
Why do they even have safe zones in a91?.
For now i have removed them completely, because it serves no point, that i can understand.
It leaves only this behind
Code:
//  Element region file (client version)

version  5
1505359255

[trans]
191  191  0
-195.721832, 33.310020, -253.569565
1.000000, 5.000000, 1.500000
-187.175003, 32.113998, -242.772003
No more errors.
[STRIKE]One more edit.
It looks to me as if some of the coordinates could be overlapping?.
Could an overlap cause the error?
In swapping one lot for the other in a22, it seems to confirm that maybe this is the problem.
Lets look at [/STRIKE]a22.
Fix tested and works
Code:
//  Element region file (client version)

version  5
1411630743

[trans]
124  122  0
301.704132, 294.794281, 525.119507
25.000000, 25.000000, 30.000000
-394.112000, 164.000000, -466.688995

[trans]
1  122  0
-708.053894, 259.008392, -489.858978
15.000000, 10.000000, 15.000000
-2824.729004, 379.201996, 3091.210938

Edit, it turned out on server reboot, the only way was to completely remove the regions.
I'd love to know why the regions on these two maps are producing server error, got me stumped, but at least this is a work around until a better solution is found.
Post edited.

So I just ran into this (using a different client) working on my release/update!!!

For some reason it WAS happening to me on is21 but NOT is22

and you're not going to believe what seems to have "fixed" it foe me!

literally add a single ZERO ("0") for each "region" region (as follows):

Code:
//  Element region file (client version)

version  5
1436092305

[region]
"白莲居"
1  13
[B][I][U][COLOR="#FF0000"]0[/COLOR][/U][/I][/B]
-656.758606  203.303116  520.937439
-694.804993  205.453812  511.817566
-709.906128  201.005386  477.728455
-702.443726  198.617371  419.313232
-673.236206  202.622086  371.329285
-589.785828  200.824127  371.409546
-516.766785  187.151276  375.501801
-481.753204  197.472717  416.697815
-479.655426  188.910675  442.262085
-497.990448  191.374176  502.763580
-527.198059  197.000198  534.057434
-606.475891  187.096848  538.229980
-656.546143  203.200211  520.916565

[trans]
123  121  0
235.114166, 189.778046, 260.322571
4.000000, 4.000000, 4.000000
330.265015, 610.000000, -264.100006

[region]
"清幽居"
1  57
[B][I][U][COLOR="#FF0000"]0[/COLOR][/U][/I][/B]
835.993652  205.315460  -359.156616
827.829224  203.840012  -357.852600
814.950562  201.805099  -352.917786
799.920654  198.723022  -348.705139
779.445313  194.030899  -345.214661
764.645996  191.841354  -342.807434
757.746521  191.331940  -344.251770
744.145691  193.080597  -348.103333
732.229980  193.096085  -353.399231
720.474182  193.096085  -362.256134
707.104980  189.730591  -376.699463
700.966553  190.622009  -390.848755
698.679688  192.714401  -400.942261
698.559326  194.960785  -416.228119
702.170166  194.387512  -425.736633
704.577393  192.999222  -436.820892
705.299561  191.717957  -451.866028
704.697754  196.272797  -479.173584
702.290527  194.308441  -505.003296
699.401855  197.371033  -531.792908
694.828125  196.383942  -553.369507
695.550293  192.667465  -569.573792
699.040771  191.484436  -586.149841
705.179199  191.484833  -599.492249
714.687683  191.758636  -609.602600
731.052856  195.515381  -620.642090
746.377136  196.009903  -625.476379
766.158997  192.649918  -628.605774
790.765991  193.597580  -633.660950
807.811646  199.189987  -635.707092
823.005188  203.998322  -637.031067
824.544434  193.084717  -606.638611
826.174622  192.277832  -604.263855
835.803467  193.279495  -594.882629
848.686401  196.459442  -588.411499
855.546997  197.507751  -584.078491
862.933228  199.142853  -576.255005
867.747681  201.900162  -564.958740
868.108704  195.809418  -546.467590
870.275208  196.271530  -537.099487
876.774719  207.849487  -524.318970
882.449097  217.137177  -516.502441
886.300659  215.710037  -506.495544
887.744995  200.164902  -488.367889
887.143188  206.984695  -469.833862
881.606567  194.681503  -451.187805
879.319763  197.921936  -443.648987
872.098083  201.586136  -433.418304
862.348877  194.596359  -426.317017
854.164307  189.530701  -415.387146
853.923584  190.027863  -410.211639
859.339844  189.645584  -399.632172
859.219482  189.895966  -393.240936
855.247559  195.281219  -383.250977
847.039673  194.142517  -373.821472
841.382690  194.991241  -366.755798
835.966431  206.632660  -359.173035

[region]
"飘渺城"
1  9
[B][I][U][COLOR="#FF0000"]0[/COLOR][/U][/I][/B]
341.699280  213.943741  -775.650146
333.762817  234.015686  -780.639038
335.280640  269.280762  -796.129517
340.609802  279.596924  -803.379333
343.952911  288.413849  -808.363525
365.984802  241.071457  -791.717529
357.616821  211.831741  -782.554321
348.267761  206.534149  -775.802979
341.699280  213.943741  -775.650146

[trans]
1  121  0
866.498535, 219.221344, -631.667603
12.500000, 12.500000, 12.500000
-2824.729004, 379.201996, 3091.210938

[trans]
172  121  89
353.900208, 433.181061, -796.567261
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998

[trans]
173  121  89
350.460907, 433.181427, -798.920898
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998

[trans]
174  121  89
355.175537, 433.181427, -794.697144
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998

[trans]
175  121  89
352.290466, 433.176910, -797.966919
1.000000, 10.000000, 1.000000
-381.217010, 30.000000, 488.128998

Still in infancy to me, as I literally took a quick sec to make this post (and I must get back to it!), but I will surely follow up if I have anything else to add or if I discover something about it...

But that is literally all I did was add the "zero" that I saw missing from the current retail/official client... Didn't even change the version number (even though the current retail is ONE version newer on the region file)...



Ok, NVM - it didn't give the server error, but upon further (light) testing - the [trans] zones no longer work >.<



So I deleted and started with all fresh client logs, seeing as this does look to be mainly if not purely client side:

The ONLY errors I saw in any/all of the logs that directly pertained to a21 were as follows:

A3D.log:
[10:14:52.286] A3DTerrain2CullHC::LoadHorizonCull, Failed to open file maps\a21\a21.t2hc
[10:14:52.286] A3DTerrain2CullHC::Init, Failed to load file maps\a21\a21.t2hc !

EC.log:
[10:14:52.390] <!> CECScene::LoadBezierNavigate, Failed to open file maps\a21\navigate.dat

[10:14:52.390] <!> CECWorld::LoadSceneObjects, Failed to load scene file maps\a21\navigate.dat

------------------------------------------------------------------------------------------

Yep, color me confused, since I do not seem to be getting any pertinent errors SERVER -or- CLIENT side, but removing the [region] zones client side only does seem to "fix"...

Something (REALLY) not right here!
 
Last edited by a moderator:
Joined
Oct 14, 2009
Messages
5,493
Reaction score
2,299
Ok, after continuing to relentlessly work on this, and having a million windows open on my PC to run "tails" on log files so I could watch them in real time! I am going to persist that this IS purely client side... Despite the fact the client is saying "Server Error", I have seen ZERO indication of ANY server errors, and you actually do remain connected despite not being able to do anything in game - IE not fly, sit/meditate, move/sort inventory/bag, etc (and any nearby mobs only having 0/1 HP) etc etc etc!

So, this tells me the client is still clearly connected to the server, it is just *refusing* to send any more data TO the server... You can replicate this easily by watching your server side log files after your CLIENTS "server" error. You can continue to "move about" but the client never reports this to the server, as I said, it stays connected but REFUSES to send any more data TO the server... So you could walk all the way across the map, and the client will keep reporting to the server that you have not moved... You can see this on the periodic "reports" using "tail" on your log files!

Furthermore, since it concerns region.clt, and more specifically only the [region] tag inside, I tried to get even more/as much info as I could... It does appear that the ONLY time this error happens is when you're IN a safe zone (read: IN a {defined} region)! Yes, when you first enter the maps (a21 or a22) you start out in a SZ, BUT - if you GM teleport (ctrl + click on map) quick enough, OUT of Safe Zone, you can stay connected what seems like indefinitely... So long as you do NOT enter any [region] Safe Zones...! As soon as you enter a SZ, and stay there more than a few seconds, the Client (FALSELY I believe) alleges that there is a "server error"... You then can continue to move around, but pretty much cannot do anything... That is because the client is REFUSING to send any data to the server...

WHY, this is actually happening, and only on a21 and a22, I have NO clue - the log files on the CLIENT side are of NO help either... None of them seem to be spilling any pertinent data/info!

You can indeed leave the matching server side SEV, from your CLT *WITH* the [regions] tags, and the server WILL still enforce SZ's - or at least it appears so (I have not been able to test) because when you empty your client side CLT of the region tags in the CLT, it will no longer crash - and ofc still displays messages that you're "entering" or "leaving" a SZ!

Personally, I don't even know why the damn region.clt exists on the client side in the first place TBH, there's ZERO point; the TWO things it controls /SHOULD/ be PURELY server side anyway... That is, the server would NEVER trust the client to tell it where safe zones are and aren't or where 'teleport' [trans] zones are either (as {duh} that could be EASILY 'hacked')!!!

I suppose the next thing I will have to test is that SZ's still exist and are fully enforced by the server despite/even after removing the [region] zones from the clients CLT side!

Hoping and assuming it will, I guess I may just have to accept this (removing [region]s from CLT) as a "solution" - even if "just for now"!!!
 
Back
Top