|
|
-
???MDP?? ?? (New MDP Algorithm)
06. 12. 2013 19:37
 Recommend : 3
jedizorro
|
My humble proposal:
1) Winning Points, Sinking Points, Credits Earned Points, only take effect if you stay in EACH GAME for at least 5 minutes;
2) Anyone should spend at least 60 minutes in NF EACH WEEK in order to be eligible for the top ranking;
3) New rankings should be calculated based on following formula (sort the results descendingly):
For Top Players in Winning Points:
(TOTAL Winning Points gained LAST WEEK) / (Total Time Spent in NF LAST WEEK)
For Top Players in Sinking Points:
(TOTAL Sinking Points gained LAST WEEK) / (Total Time Spent in NF LAST WEEK)
For Top Players in Credits Earned Points:
(TOTAL Credits Earned Points gained LAST WEEK) / (Total Time Spent in NF LAST WEEK)
[Begin of EDIT]
The denominator in above formulae can be further improved to:
*Total Time Spent in BATTLE AREA LAST WEEK
(this is to exclude the time spent in trade area, harbor, etc)
or
*Total Time Spent AFTER BATTLE BEGAN IN BATTLE AREA LAST WEEK
(this is to exclude the waiting time in battle rooms)
[End of EDIT]
This new algorithm clearly takes into account players' efficiency (an indicator of player skill?) and actually makes it very dominant factor. Basically, the way to measure the 'dominance' of a player has become:
1) How many Winning Points can you gain per hour?
2) How many Sinking Points can you gain per hour?
3) How many Credits Earned Points can you gain per hour?
Of course NF can always adjust the algorithm if NF expects players to spend more time each week (e.g. Eligilibity for top ranking requires 120 minutes per week, or more, etc).
This algorithm also discourages those players who keep DisConnecting in order to keep a high winning rate, because the "Total Time Spent in NF LAST WEEK" records everything, and no one can change his/her efficiency through DisConnecting. To make this point clearer, DisConnecting will only make the denominator larger (i.e. increased total time spent), but keep the numerator the same (i.e. unchanged Winning Points/Sinking Points/Credits Earned Points), which makes the ratio smaller.
Something for NF to consider, anyways...
|
-
Re : ???MDP?? (New MDP Algorithm)
06. 12. 2013 19:42
Superduckie
|
... these figures on the ships also indicate who to target first, lmboooooooooo
|
-
Re : ???MDP?? (New MDP Algorithm)
06. 12. 2013 19:48
jedizorro
|
Originally Posted by Superduckie
... these figures on the ships also indicate who to target first, lmboooooooooo
Of course, this is exactly the point, isn't it? Making everything more competitive, interactive and intereseting.... xD
|
-
Re : ???MDP?? (New MDP Algorithm)
06. 12. 2013 21:09
Mahler
|
?? ??? ??? ???? ????...??
|
-
Re : ???MDP?? ?? (New MDP Algorithm)
06. 13. 2013 14:04
jedizorro
|
Any opinions? People? Benser? Rehor? ...
Why is everyone panicking as soon as we are talking about efficiency?
|
-
Re : ???MDP?? ?? (New MDP Algorithm)
07. 02. 2013 22:37
DemFuhrer
|
Sir, You are Adding DIVISION OPERATION to the MDP functions????
You know how heavy task the DIVISION OPERATION will put on the server..? Each integer division consumes more than 100 times the computing resource needed for an ADDITION operation, and floating point division consumes even dozens of times more than an integer division...
SDE's programmer haven't learnt how to corretly deal with SUBTRACTION. And now you want them to do DIVISION..?!?!
Do you think our Pentium 386 server is able to safely handle the SDE code involving DIVISION, without causing more lag and crash?
|
-
Re : ???MDP?? ?? (New MDP Algorithm)
07. 03. 2013 04:25
KKKaPPP
|
|
-
Re : ???MDP?? ?? (New MDP Algorithm)
07. 03. 2013 06:06
skindeep2366
|
Good recommendation but do you really have any concept as to how much code this would take to apply? The current MDP system is really cut and dry simple code but when you get in to all of these conditions of when to and when not to apply you have created a holy hell nightmare to code. They need to worry about fixing the game issues before they devote the amount of time it would take to implement this algorithm successfully.
Secondly this is lopsided and doesn't level the playing field AT all for Blitz players. Quite Simply blitz players CANNOT have the per hour damage output of bb2-6 players. They can't have the points/credit winnings per hour verse upper lvl AA boats and upper lvl CV'S. This doesn't even take in to account the SS's... This in no way would promote the Blitz game play and would further hurt the game as a whole.
This whole drastic turn in mindset and mentallity is what is helping to push this game off the cliff faster. Play the game and be happy it's still alive. This garbage crap "I'm the best player on the server is well.... Just plain stupid little kid on the playground junk.
What I am saying is this. This is a game. After this game dies and is gone are you going to lose sleep over it? If someone is the MDP for 5 straight years is it going to make national news? If skindeep2366(I used my name to keep from violating rules) knocks down 5 people to get to the top does it count for crap? The answer to all of that is NO.
Don't talk SDE into making for fail additions or changes. Leave the game AS IT is content wise and JUST FIX the fails.
|
-
Re : ???MDP?? ?? (New MDP Algorithm)
07. 03. 2013 06:44
skindeep2366
|
Originally Posted by DemFuhrer
Sir, You are Adding DIVISION OPERATION to the MDP functions????
You know how heavy task the DIVISION OPERATION will put on the server..? Each integer division consumes more than 100 times the computing resource needed for an ADDITION operation, and floating point division consumes even dozens of times more than an integer division...
SDE's programmer haven't learnt how to corretly deal with SUBTRACTION. And now you want them to do DIVISION..?!?!
Do you think our Pentium 386 server is able to safely handle the SDE code involving DIVISION, without causing more lag and crash?
I think you need to read up on programming a bit. First ..... Floating point division and Integer Division consume the same basic amount of cycles. 100 times? Where do you get that number at and keep in mind simple addition and subtraction still take 1 - 2 cycles. Division either FP OR INT use around 40 cycles. Divisions are not Pipe-able, however, with multiplication a new multiplication can be added every cycle but if you spend 10 cycles adding new multiplications you still have to wait the full 10 cycles for each individual one to finish. You are talking about something that is so minor it goes completely against any programming logic. If you must divide, then you must divide. You really don't grasp that his Algorithm provides for a cut and dry method to do the Calculations you are so worried about being server side intensive. Logically for his algorithm to work correctly as layed out the calculations could not be done but once a week. So what better time to run it then during weekly maint. really no more than what would need to be calculated the logic in your reply is far from anything correct. Lastly the servers are FAR above Pentium 386's... The problem is they are running OLD POORLY DESIGNED SOFTWARE. That is where the instability is coming from. Nothing less nothing more. I will go back to my cave now glad I could help with your life altering confusion.
|
-
Re : ???MDP?? ?? (New MDP Algorithm)
07. 18. 2013 11:29
jedizorro
|
Originally Posted by skindeep2366
Originally Posted by DemFuhrer
Sir, You are Adding DIVISION OPERATION to the MDP functions????
You know how heavy task the DIVISION OPERATION will put on the server..? Each integer division consumes more than 100 times the computing resource needed for an ADDITION operation, and floating point division consumes even dozens of times more than an integer division...
SDE's programmer haven't learnt how to corretly deal with SUBTRACTION. And now you want them to do DIVISION..?!?!
Do you think our Pentium 386 server is able to safely handle the SDE code involving DIVISION, without causing more lag and crash?
I think you need to read up on programming a bit. First ..... Floating point division and Integer Division consume the same basic amount of cycles. 100 times? Where do you get that number at and keep in mind simple addition and subtraction still take 1 - 2 cycles. Division either FP OR INT use around 40 cycles. Divisions are not Pipe-able, however, with multiplication a new multiplication can be added every cycle but if you spend 10 cycles adding new multiplications you still have to wait the full 10 cycles for each individual one to finish. You are talking about something that is so minor it goes completely against any programming logic. If you must divide, then you must divide. You really don't grasp that his Algorithm provides for a cut and dry method to do the Calculations you are so worried about being server side intensive. Logically for his algorithm to work correctly as layed out the calculations could not be done but once a week. So what better time to run it then during weekly maint. really no more than what would need to be calculated the logic in your reply is far from anything correct. Lastly the servers are FAR above Pentium 386's... The problem is they are running OLD POORLY DESIGNED SOFTWARE. That is where the instability is coming from. Nothing less nothing more. I will go back to my cave now glad I could help with your life altering confusion.
Friend, DemFurer was being sarcastic, can't you tell?
|
-
Re : ???MDP?? ?? (New MDP Algorithm)
07. 18. 2013 11:47
jedizorro
|
[QUOTE=skindeep2366]
Good recommendation but do you really have any concept as to how much code this would take to apply? The current MDP system is really cut and dry simple code but when you get in to all of these conditions of when to and when not to apply you have created a holy hell nightmare to code. They need to worry about fixing the game issues before they devote the amount of time it would take to implement this algorithm successfully.
[Jedizorro] This is not necessarily hard. First of all, this new MDP, or to call it, M Efficient P, can be updated ONCE A WEEK, during maintenance window. All it has to do was a simple division operation in the database. I'm from IT industry as well and I don't see why this is hard. And in my opinion it should not be hard to tell how much time a player has spent in game. SDE is already capable of determining whether a player has spent more than 5 min in game, remember? Otherwise how can SDE to give Premium awards to a player? All SDE has to do is add these minutes-in-game for each player, on weekly basis, should be simple enough.
Secondly this is lopsided and doesn't level the playing field AT all for Blitz players. Quite Simply blitz players CANNOT have the per hour damage output of bb2-6 players. They can't have the points/credit winnings per hour verse upper lvl AA boats and upper lvl CV'S. This doesn't even take in to account the SS's... This in no way would promote the Blitz game play and would further hurt the game as a whole.
[Jedizorro] Well, for one thing, Blitz player may have very high ranking in Sink Points per Hour (e.g. Kita) and Winning Points per Hour (e.g. blocking shooting York, Baltimore, Motzke, etc). Yes it will be hard for Blitz players to get a high ranking for Credit Points per Hour, but why do Blitz players have to get high ranking in all aspects? Is that a good way to promote GB players???
This whole drastic turn in mindset and mentallity is what is helping to push this game off the cliff faster. Play the game and be happy it's still alive. This garbage crap "I'm the best player on the server is well.... Just plain stupid little kid on the playground junk.
What I am saying is this. This is a game. After this game dies and is gone are you going to lose sleep over it? If someone is the MDP for 5 straight years is it going to make national news? If skindeep2366(I used my name to keep from violating rules) knocks down 5 people to get to the top does it count for crap? The answer to all of that is NO.
Don't talk SDE into making for fail additions or changes. Leave the game AS IT is content wise and JUST FIX the fails.
[/QUOTE]
|
|
|
