Attack Rate Bug. Does anyone have the fix to it?

[Stanizzle]

So I have researched this problem for a while, I have tested by editing the server files left and right, and still haven't found a solution. I didn't really want to post this question until I have exhausted every single option I had, because I know I would get answers like "use the search button," or "google is your friend," etc. I HAVE googled it, I HAVE searched it, but haven't stumbled upon a solution. So if you don't have a significant answer for me and your best advice is to google and search, please do not bother posting here.

So as I have found, the maximum attack rate that the cabal game accepts is 214926. Once you add another attribute that gives attack rate, the rate goes straight down to 1.

So I figured the two solutions would be:

1. Make a script that doesn't allow the attack rate to go any higher than 214926, meaning that any time the attack rate goes higher than that value, the script sets it to 21496 right away. I have no clue how to make a script like that, so I would need your help to do this.

2. Edit how much attack rate each attribute gives, then decrease that value based on the maximum attributes the players can get in your server. It would take away advantages of classes, but it's another option.

Is there any other solution? Please let me know. This would be a major help not only to me, but I think to everyone!

[MentaL]

[Yamachi]

3. Use normal values instead of allowing the players to get insanely high stats... If you do stuff that isn't supposed to be done, of course you're going to run into problems.

[Stanizzle]

I would like for the server to be able to use 300k stats, so your solution doesn't help me Yamachi. Thank you for your answer and care though.

[Yamachi]

300k stats?? Why would you possibly want that many? This "bug" as people are calling it has been discussed many times on the forums already, and we have advised people NOT to use stats that high because the server simply cannot support it. If you choose to go against our advice and do it anyways, you have to expect issues. I don't want to sound like an arsehole or anything (I can assure you I'm not one), but I must be blunt; We're not here to "fix" things that aren't broken if you use them correctly. All I can suggest is that you lower the amount of stat points you are giving people. When you start messing with things like attempting to increase the limit, or decrease the bonuses you get, you are going to experience odd side-effects.

[Stanizzle]

I understand what you're saying... But I like to take risks and test limits. The worst thing that could happen is I have to take my backups and put them where the tested files were. It's no problem at all. Just asking if developers such as yourself have ever tried to play with these numbers and found any solutions to overcome the limits.

And in no way did I think you're an arsehole at all, so don't even worry about how you look in my eyes Yama. I completely understand where you're coming from.

[xXxAxXx]

Problem was solved.For those who encounter this in the future a nice and simple way is to reduce the point received when distributing stats to the user.
For EXAMPLE the Maximum attack rate the server supports is 200000
Now this is for a server with 200 LVL (which gives 1000 stats points)
When you have a server with resets (lets say 100 and keep stats)you have to consider that you will add more points than it was mented.The simplest on logical solution is to distribute those points (200000) on the during those 100 resets.With 100 reset you can gain 100.000 Stats points.



As you can see in the above picture the BL class receives the biggest value of ATT Rate for 1 point of DEX so that is the recommended class to set the maximum ATT Rate value/stats point(Rank.scp from srv and cabal.enc from client)
You reduce the ATT rate until you find the value,then you find how much in % represents from the default one and then you multiply all the other with that to keep the balance between the classes.
After that the hero will gain his normal Max attack rate not after 200 lvl and after 100 resets and reaching lvl 200


Sorry if I am not to clear about this but its 3 AM at me and I struggled with this a lot.
I you guys are interested I can make an very detailed tutorial.

Regards to all.

[PunkS7yle]

A fix for this is decreasing the atk rate coef.
go to rank scp and find

1	8,-5	5,-4	6,-6	7,-7	7,-7	3000,2000,0	1000,1000,3000	1500,1500,0	4000,17500,4000	2000,10000,1000	50	20	30	10	80

Decrease the atk rate coef by a lot ( PS thats warrior data, do it for all classes )

the cabal.enc equivalent for it is in

<class_formula	class="2hand"	class_atk="8,-5"	class_matk="5,-4"	class_def="6,-6"	class_ar="7,-7"	class_dr="7,-7"	stat_atk="20000,2000,0"	stat_matk="1000,1000,3000"	stat_def="1500,1500,0"	stat_ar="4000,17500,4000"	stat_dr="2000,10000,1000"	/>

[SpeedDevil]

Problem was solved.For those who encounter this in the future a nice and simple way is to reduce the point received when distributing stats to the user.

[Stanizzle]

We did solve it, but I wish there was a better way! If anyone ever comes up with a better way, it would be highly appreciated.

[PunkS7yle]

Well, which way did you use ?

[Yamachi]

But your "solution" now means that people have much less attack rate than they should do, which is going to cause more misses when attacking mobs.

[xXxAxXx]

not if we edited the same thing to the mobs Yama ;)

[Stanizzle]

We made the value of attack rate that is given for each attribute less. Depending on how many resets your server has and the maximum stats your server can give, that's how you determine the value of how much attack rate each attribute gives.

Now since we decreased every characters attack rate received from the stats, the challenge was that the mobs defense rate would be too high and we wouldn't hit the mobs enough... The next step was to lower the defense rate OF THE MOBS by the same percentage you lowered the attack rate your character receives, and now you have the same base and everything works fine.

Problem solved! Just took a little bit of testing and mathematical thinking.

[PunkS7yle]

But your "solution" now means that people have much less attack rate than they should do, which is going to cause more misses when attacking mobs.

The hell does that matter when they use freaking hundred of k of stats.

[Yamachi]

The hell does that matter when they use freaking hundred of k of stats.

It matters when they're NOT using a high amount of stats, smartarse. What about new characters? Exactly... Do yourself a favour and try not to let your personal grudges affect the way you post in future.

[PunkS7yle]

It matters when they're NOT using a high amount of stats, smartarse. What about new characters? Exactly... Do yourself a favour and try not to let your personal grudges affect the way you post in future.

Now you're just trippin'. A solution besides that is increase the atk rate via an upgrade/buff/ whatever.

[emi]

Besides greed for what the hell would you add houndreds of thousands of stats?

[Stanizzle]

Now you're just trippin'. A solution besides that is increase the atk rate via an upgrade/buff/ whatever.

There is a maximum attack rate amount that you can reach before it goes back to 1... If you reach over that limit, your attack rate goes back to 1. The exact limit that the server takes of attack rate is 214926. If your attack rate goes over 214926, then your attack rate goes back to 1.

Example, the blader gets 2 attack rate for every dex/str point. When you put 107373 into dex/str, the attack rate becomes 214926. If I put 1 more point into dex or str, the attack rate becomes 214928, the server doesn't accept that value and the attack rate on the character goes back to 1. If you test it, you will see the result.

What we did was, we changed that for every dex/str point, the blader no longer gets 2 points, but gets as many points as it fits for maximum stat amount on our server.

Now in the end the characters get less attack rate than normal, so we decreased the defense rate of all the monsters by the same percentage as we decreased the stat gain by, that levels the relationship between attack rate of the character and the defense rate of the mobs, and makes the game play perfect even at high resets. All it takes is a bit of math. This works 100%, no need to get mean to each other. Yama is right.

[emi]

There is a maximum attack rate amount that you can reach before it goes back to 1... If you reach over that limit, your attack rate goes back to 1. The exact limit that the server takes of attack rate is 214926. If your attack rate goes over 214926, then your attack rate goes back to 1.

Example, the blader gets 2 attack rate for every dex/str point. When you put 107373 into dex/str, the attack rate becomes 214926. If I put 1 more point into dex or str, the attack rate becomes 214928, the server doesn't accept that value and the attack rate on the character goes back to 1. If you test it, you will see the result.

What we did was, we changed that for every dex/str point, the blader no longer gets 2 points, but gets as many points as it fits for maximum stat amount on our server.

Now in the end the characters get less attack rate than normal, so we decreased the defense rate of all the monsters by the same percentage as we decreased the stat gain by, that levels the relationship between attack rate of the character and the defense rate of the mobs, and makes the game play perfect even at high resets. All it takes is a bit of math. This works 100%, no need to get mean to each other. Yama is right.

I'm sorry but I do not agree. What about pvp or PK?
There is more to work not just a little change here and there, and for what? nothing but getting insane stats.
However you're doing on your responsability and be sure no one it's gonna help when a serious matter will eventually occur.

Do i sence envy?

All you could ever <<sence>> is your <<scent>>
Definitely you have no clue about what are you doing and small changes won't help when you mess up the server.

Good luck to anyone who's forcing server accept things that it's never made for.