Before support for 1.7.3 ends when 2.0 is out I need help with some stuff, In anticipation for the new expansion I wana make my roster lvl 80 ready. I've been looking at some of the files but I cant seem to quite get it right. So any help in this area would be appreciated.

Why not upgrade to 2.0?

i think u can fix the menu.php in the lib folder
find this

Code: Select all


    $num_lvl_70 = 0;
    $num_lvl_60_69 = 0;
    $num_lvl_50_59 = 0;
    $num_lvl_40_49 = 0;
    $num_lvl_30_39 = 0;
    $num_lvl_1_29 = 0;
 

and make it look like

Code: Select all


    $num_lvl_80 = 0;
    $num_lvl_70_79 = 0;
    $num_lvl_60_69 = 0;
    $num_lvl_50_59 = 0;
    $num_lvl_40_49 = 0;
    $num_lvl_1_39 = 0;
 

and then find

Code: Select all

         case 7:
            $num_lvl_70 += $row['amount'];
            break;
         case 6:
            $num_lvl_60_69 += $row['amount'];
            break;
         case 5:
            $num_lvl_50_59 += $row['amount'];
            break;
         case 4:
            $num_lvl_40_49 += $row['amount'];
            break;
         case 3:
            $num_lvl_30_39 += $row['amount'];
            break;
         case 2:
         case 1:
         case 0:
            $num_lvl_1_29 += $row['amount'];
            break;
         default:


do something like

Code: Select all

         case 8:
            $num_lvl_80 += $row['amount'];
            break;
         case 7:
            $num_lvl_70_79 += $row['amount'];
            break;
         case 6:
            $num_lvl_60_69 += $row['amount'];
            break;
         case 5:
            $num_lvl_50_59 += $row['amount'];
            break;
         case 4:
            $num_lvl_40_49 += $row['amount'];
            break;
         case 3:
         case 2:
         case 1:
         case 0:
            $num_lvl_1_39 += $row['amount'];
            break;
         default:


but the 2.0 has a better framework and alot more bells and whisle's. this code is untested so if its wrong fix it plz.

There's another two or three places in 1.7.3 where you need to fix the level.

For 2.0, you just need to update some values in lib/constants.php.

Anaxent wrote:Why not upgrade to 2.0?

Ive already gone over that in another thread I'd rather not have to explain it again... short answer I'm not to fond of the way it looks.

PleegWat wrote:There's another two or three places in 1.7.3 where you need to fix the level.

For 2.0, you just need to update some values in lib/constants.php.

Could you please point those places out ;-)


@Tennessee, thats the code I've been working with trying to get it to work on my own before I made this post. But I knew I was missing something as Pleeg pointed out.

You also forgot this little bit of code... but I'm sure theres still stuff missin that needs to be modified.

Code: Select all

<ul>
        <li style="color:#999999;">Average Level: '.round($result_avg).'</li>
        <li>'.$wordings[$roster_conf['roster_lang']]['level'].' 1-29: '.$num_lvl_1_29.'</li>
        <li>'.$wordings[$roster_conf['roster_lang']]['level'].' 30-39: '.$num_lvl_30_39.'</li>
        <li>'.$wordings[$roster_conf['roster_lang']]['level'].' 40-49: '.$num_lvl_40_49.'</li>
        <li>'.$wordings[$roster_conf['roster_lang']]['level'].' 50-59: '.$num_lvl_50_59.'</li>
        <li>'.$wordings[$roster_conf['roster_lang']]['level'].' 60-69:: '.$num_lvl_60_69.'</li>                               
        <li>'.$wordings[$roster_conf['roster_lang']]['level'].' 70: '.$num_lvl_70.'</li>

You'll have to search back what got changed for 1.7.2 when wow 2.0 hit - I can't remember from the back of my head. There's a good chance I'll look it up myself at some point to post it for those who need it, but not till after wow 3.0 actually releases.

PleegWat wrote:You'll have to search back what got changed for 1.7.2 when wow 2.0 hit - I can't remember from the back of my head. There's a good chance I'll look it up myself at some point to post it for those who need it, but not till after wow 3.0 actually releases.

Umm 2.0 isnt even fully released yet and I havent seen any sort of news on a 3.0

Also, if anyone has any idea as to whats missing that needs to be changed to make 1.7.3 lvl 80 ready I'm all ears and so is everyone else whos interested in keeping 1.7.3

Edit: I think I found the last bit of missing code to change to make 1.7.3 lvl 80 (Lich King) ready... In constants.php

Find

Code: Select all

define('ROSTER_MAXCHARLEVEL','70');

Change To

Code: Select all

define('ROSTER_MAXCHARLEVEL','80');

If theres anything else that needs to be changed I'm sure I'll find it but I believe this is it becace the lvl "bar graph" on the main roster now shows a small black space for the missing lvls 70-80

http://www.politicalchaos.net/roster/index.php?s=level

There's also some stuff to do professions.

You're misunderstanding me about the version numbers I referred to.

There have been earlier posts about how to convert WoWRoster 1.7.2 to be compatible with World of Warcraft: The Burning Crusade (2.0).

In the same way, there will be posts on how to convert WoWRoster 2.0 (and probably 1.7.3) to be compaible with World of Warcraft: Wrath of the Lich King (3.0).

And that's the last I'll post on the issue until WotLK goes public beta.

PleegWat wrote:There's also some stuff to do professions.

You're misunderstanding me about the version numbers I referred to.

There have been earlier posts about how to convert WoWRoster 1.7.2 to be compatible with World of Warcraft: The Burning Crusade (2.0).

In the same way, there will be posts on how to convert WoWRoster 2.0 (and probably 1.7.3) to be compaible with World of Warcraft: Wrath of the Lich King (3.0).

And that's the last I'll post on the issue until WotLK goes public beta.

Now I gotcha, but in regards to that... Ive been told that once the 2.0 roster comes out support for 1.7.3 will cease to exist. So with that said assuming roster 2.0 comes out before Lich King does then one would assume no support will be given for 1.7.3 on how to make it Lich King ready hence the reason for this post. Also, yes I know professions and other stuff will need to be updated for roster 1.7.3 and 2.0 to make them Lick King ready and any other expansion that Blizzard decides to release when they release them.

OK, my curiosity got the best of me and I checked.

We weren't at 1.7.2, but at 1.7.1 when TBC got released. It needed changing all over there, and it was centralized for 1.7.2. For 1.7.2 or 1.7.3, only constants.php and menu.php need to be fixed. For 2.0, only constants.php need to be fixed.

1.7.x will need fixes all over for deathknight support. So will 2.0.

Ok, so then I'm done editing as far as levels go for making my 1.7.x roster Lich King ready. In regards to support though for people like me that exclusively use and like roster 1.7.x I just hope that future support will atleast be considered if nothing else for Lich King & other future expansions as well as image packs.

for the code posted above

Code: Select all

        <li style="color:#999999;">Average Level: '.round($result_avg).'</li>
        <li>'.$wordings[$roster_conf['roster_lang']]['level'].' 1-39: '.$num_lvl_1_39.'</li>
        <li>'.$wordings[$roster_conf['roster_lang']]['level'].' 40-49: '.$num_lvl_40_49.'</li>
        <li>'.$wordings[$roster_conf['roster_lang']]['level'].' 50-59: '.$num_lvl_50_59.'</li>
        <li>'.$wordings[$roster_conf['roster_lang']]['level'].' 60-69: '.$num_lvl_60_69.'</li>
        <li>'.$wordings[$roster_conf['roster_lang']]['level'].' 70-79:: '.$num_lvl_70_79.'</li>                               
        <li>'.$wordings[$roster_conf['roster_lang']]['level'].' 80: '.$num_lvl_80.'</li>


and open your constants.php and u will see
define('ROSTER_MAXCHARLEVEL','70');
just change that to 80.

OK, this is enough. WotLK will not be relevant for months, very much possibly up to a year. 2.0 will be well distributed by then. Any bugs in it can be reported and fixed. Any visual issues can be fixed in templates. If 1.7.3 is still commonly used by that time it will be patched as well.

Topic locked. Similar new topics will be deleted.