** RAWDEAL SINGAPORE RANKINGS ** updated 05 AUG
#ff0000
I'm Most Glorious.
1
0
1
Jul 6, 2014 0:14:57 GMT 8
10
allanglorious*
661
Mar 21, 2011 18:38:35 GMT 8
March 2011
admin
|
Post by allanglorious* on May 15, 2011 15:00:42 GMT 8
RAWDEAL SG RANKINGS 1) JJ / WEED / 1686 POINTS 2) TIANSHENG / RACHELMON / 1613 POINTS 3) ZHI XIAN / BALLS / 1612 POINTS 4) ALLAN / ALLANGLORIOUS / 1584 POINTS 5) JASON / JASONLAI 1575 POINTS 6) WEI JIE / ALONSOCWJ / 1571 POINTS 7) CYRIL / 1568 POINTS 8) ERIC / 1568 POINTS 9) XIUBIN / XBCHEE / 1548 POINTS 10) WINSTON / OJUICE / 1541 POINTS 11) DARYL / DARO / 1541 POINTS 12) HENRY / BRIGHTBACK / 1539 POINTS 13) JARED / TIKIKURA / 1525 POINTS 14) JIE BO / WHITEDRAGON / 1523 POINTS 15) RONNIE / 1511 POINTS 16) HOONSIANG / HOONY / 1508 POINTS 17) KEVIN QUA / KQKB / 1508 POINTS 18) CONSTANTINE / 1507 POINTS 19) LUKE / LUKEBOI / 1501 POINTS 20) JACK / 1500 POINTS 21) LESLIE / EVILBATTY / 1492 POINTS 22) ZHI HONG / 1481 POINTS 23) SMWG / 1480 POINTS 24) WEI DONG / 1480 POINTS 25) CHEN HAO / 1469 POINTS 26) LIN SONG / 1462 POINTS 27) PHAN / AHHUATAH / 1462 POINTS 28) BASIL / 1460 POINTS 29) DE SHENG / FLUSHX / 1460 POINTS 30) ANDRE / CSRINALDO / 1459 POINTS 31) ZENACEPRO / 1457 POINTS 32) MIKE / COLOSSUS / 1456 POINTS 33) KAYDEN / 4TUNEIMPACT / 1456 POINTS 34) JUN HAN / 1448 POINTS 35) RIZUAN / SHAMROCK / 1446 POINTS 36) VICTOR / 1432 POINTS 37) ALEX / ALEXCLUZIVE / 1417 POINTS 38) FADHIL / FATDEW / 1398 POINTS 39) SHERWIN / WWECOLLECTOR / 1373 POINTS 40) NICHOLAS / 1360 POINTS
|
UPDATED AS ON 05/08/11* I didn't show how many game was played, win or lose as its simply not nice to show ppl who played like 10 games but lose all 10, please understand, Thanks !
|
|
#ff0000
I'm Most Glorious.
1
0
1
Jul 6, 2014 0:14:57 GMT 8
10
allanglorious*
661
Mar 21, 2011 18:38:35 GMT 8
March 2011
admin
|
Post by allanglorious* on May 20, 2011 15:33:02 GMT 8
RAWDEAL SG RANKING FORMAT
RAW DEAL JUDGE SOFTWARE WILL BE USED TO CALCULATE POINTS.
Each players starts with 1500 points.
THE SWISS SYSTEM 6.1 - Wherever possible, the Swiss system will be used in sanctioned tournament play unless permission is given by Comic Images. 6.1.1 - Any number of the following variants to the Swiss system may be used: Single Elimination, Double Elimination, Straight Swiss, Standard Swiss. 6.1.1.A - Single Elimination expels from the tournament any Player who loses to an opponent for any reason. The Top # Cut for Standard Swiss uses this method. 6.1.1.B - Double Elimination is similar to 6.1.1.A with the exception that it requires two losses for a Player to be eliminated from the tournament. 6.1.1.C - Straight Swiss is played with enough rounds to have one undefeated player at the end. A Top # Cut is not used for this format. 6.1.1.D - Standard Swiss is the normal tournament format. A number of rounds followed by a Top # Cut. The Top # Cut is single elimination. 6.1.2 - The purpose of the Swiss System is to have one undefeated player at the end of rounds. This is not always possible, but the formula must still be followed: 8 Players or less - 3 Rounds. 9-16 Players - 4 Rounds. 17-32 Players - 5 Rounds. 33-64 Players - 6 Rounds. 65-128 Players - 7 Rounds. Additional Rounds may be needed if the Straight Swiss system is used. 6.1.3 - For the initial round 1 pairings, the Swiss system is not used, since all players have the same Match Points. Pairings must be done randomly. 6.1.4 - Odd numbers of participants will generate a random Bye. The player receiving the Bye will receive 3 Match Points for a Pinfall victory. Tiebreakers will not count this Match as being played (although the 3 Points still counts.) 6.1.5 - A player may only be given a random Bye if he: (a) Has not had a random Bye for this tournament, and (b) Has (or is tied for) the lowest Match Points amongst those players eligible to receive a random Bye. 6.1.6 - Players will occasionally be awarded Byes through some predetermined method (such as winning a gateway tournament etc.) Awarded Byes are granted by Comic Images for specific tournaments only. Awarded Byes follow the same rules as Random Byes, except that the same Player may have more than one in a Tournament, and more than one player may be affected.
6.2 - Scoring for tournament matches is as follows: 3 Match Points for a Pinfall Victory. 2 Match Points for a Countout Victory. 0 Points for a draw (including a draw based on time limit.) A Double Countout (both players end a turn with 0 cards in Arsenal) counts as a loss, and gives 0 Match Points for each Player. Match Disqualification counts as a Pin for the opponent (3 points) and Double Match Disqualification (both players Disqualified) is a Double Countout (0 points for both players)
6.3 - Swiss pairings are performed after all matches in the previous round are completed. 6.3.1 - Players who are on the same match points must be paired within the same group, or as closely as possible. 6.3.2 - It is possible for players to be paired against someone with more or less Match Points. 6.3.3 - Players may not be paired against each other if they have already played once during Swiss rounds. (EXCEPTION - If the nature of the tournament requires two players to play an extra Match in order to make the Top # Cut, these players may play regardless of tournament history. This is not counted as a tournament Match, but it must follow the same rules as a tournament Match.) 6.3.4 - Tournament officials may choose to avoid pairing players together if they are playing the same Superstar cards, as long as the Swiss pairings would otherwise not be affected. (EXAMPLE - The only Players with 10 Match Points after 5 rounds are playing Tazz. As long as they have not played each other yet, they must play each other in the next round.) 6.3.5 - Wrestlers who appear on Tag Team Superstar cards are considered different from Individual Superstar cards for the purpose of this rule. (EXAMPLE - Jeff Hardy is considered to be a different wrestler than Hardy Boyz.) 6.3.6 - Once the Swiss rounds have been completed, organizers must then calculate the final standings. Once completed, this information is considered Public Knowledge. 6.3.7 - If the tournament organizers wish to perform a Top # Cut for playoffs, they must determine the players eligible. This is to be done using the Diversity system (Section 9.) They must then make the original final standings public as well as the revised standings. 6.3.8 - The amount of Match Points currently awarded to each player is considered Public Knowledge. 6.3.9 - Each player is responsible for keeping track of his own Match Points in order to bring a possible discrepancy to the attention of the Tournament Organizer. Discrepancies for the last round played must be reported before the current round is finished. (EXAMPLE - A misreported Match in round 3 must be reported before the pairings for round 5 are completed.)
|
|
#ff0000
I'm Most Glorious.
1
0
1
Jul 6, 2014 0:14:57 GMT 8
10
allanglorious*
661
Mar 21, 2011 18:38:35 GMT 8
March 2011
admin
|
Post by allanglorious* on Jul 18, 2011 0:28:11 GMT 8
Current Most Tournament Wins :
BALLS - 3 Weed - 4 TianSheng - 2 Allan - 1 Daro - 1 Jason Lai - 2 Hoony - 1 XiuBin - 1 Wei Jie - 1
|
|
#ff0000
I'm Most Glorious.
1
0
1
Jul 6, 2014 0:14:57 GMT 8
10
allanglorious*
661
Mar 21, 2011 18:38:35 GMT 8
March 2011
admin
|
Post by allanglorious* on Aug 5, 2011 15:26:57 GMT 8
Note that Ranking did not include games played on 30th July as Alonso have not pass me the scoresheet. Will update once I have it, Thanks !
|
|
Installation |
Customization |
|
|
Welcome to the help dialog for the Custom Mini-Profile Creator plugin!
Click on any of the tabs above to go through the plugin configuration process!
You can access this menu at any time by clicking on the
icon in the bottom right bar (may not be applicable if you're on Forums.net), or you can disable the welcome window and/or the icon by going to
Plugins > Manage > Custom Mini-Profile Creator and changing the
Show Help option.
This step is essential as it gives the plugin everything it needs on the page to get as much profile information as possible.
To make the profile variables work you'll need to add a new line to the very end of
Themes > Layout Templates > Mini-Profile and paste the code below on it. The code should be placed completely outside of the mini-profile, so if you're using the default mini-profile template this will be after the very last closing
</div> tag.
This needs to be done on every theme you have the plugin enabled on as the template is theme-specific.
If your mini-profile template is already customized and you've hit the variable limit for your template you're free to remove any lines from the code below if they contain information that you don't plan on using. For example, if you have no plans to ever add a user's IP to their mini-profile for staff reference you can remove
<div class="mp-info ip">$[user.ip]</div> from the code and everything else will still work just fine.
Click to show example
Once you've added the HTML from the Layout Templates tab you're ready to move on to building your mini-profiles. If you want to get going and try some out now or you're not very adept at HTML, CSS, or Javascript, worry not! This plugin includes some examples for you to try out. You're free to skip to the Custom Profile Fields tab and read over this tab later when you're ready to build your own.
Here's a quick rundown of each of the components in Plugins > Manage > Custom Mini-Profile Creator:
Name
This is the name you'll be adding to your custom profile field dropdown once you've finished coding the mini-profile. Pretty self-explanatory. Make sure this name is unique from every other name you use for your mini-profiles or you'll end up overwriting the earlier ones in the list.
HTML
This is the HTML that will go inside your mini-profile. You can use just about any HTML tag here so long as it's appropriate for where the mini-profile is showing on the page. Please refrain from using <style> or <script> tags here. You have the next two sections for that! Also, remember that mini-profiles can show multiple times on the same page, so you shouldn't add ID attributes to any of your elements here. Two elements on the same page cannot have the same ID per HTML standards.
CSS
This is where you'll place what would normally go in your forum's style sheet or what would normally be between <style> tags. Try to code your mini-profile's HTML in a way that will allow you to target it specifically with your selectors. For example, you can surround all of the content in your HTML with a <div> element with a class and target that class and its child elements specifically with your CSS. That way you don't accidentally target every mini-profile on the page with CSS that was meant for the one you're building. One more thing: The forum theme's CSS still applies beforehand, so your mini-profile may look right in one theme but not in another. The best way to circumvent this is to define as many styles as you can to override the theme's CSS.
Javascript
Anything that normally goes between <script> tags will go here. This one's a bit tricky since you'll obviously want to target the custom mini-profile specifically. Luckily there's an easy way to do that. In your statements you can use the $(this) variable to target the mini-profile if you're coding using jQuery. Otherwise, if you only plan on using standard Javascript you can target $(this)[0] instead.
Once you've finished building your mini-profiles it's finally time to add them to the Edit Profile page for use! To enable selection of custom mini-profiles you'll first need to add two specific custom profile fields in
Members > Custom Profile Fields in your forum's admin area:
- Mini-Profile Theme
- Staff Mini-Profile Theme
Mini-Profile Theme is for mini-profiles that are designed for member use. You can set the Who Can Edit option for this field to
Staff With Power if you only want staff to be able to choose mini-profiles for users. Otherwise, if you want members to freely be able to choose their own mini-profiles you can choose
Members and Staff With Power.
Staff Mini-Profile Theme is for mini-profiles designed specifically for staff use. This field is completely optional.
Set the type for both of these fields as
Drop Down Selection. Click on the
(View/Edit) link to add mini-profile names to each of these fields.
If you've just installed this plugin you should have three different mini-profiles already installed by default:
Example 1,
Example 2, and
Example 3. You can add these to your dropdowns to test them out and see the plugin in action.
Click to show example
If you're having trouble getting this plugin to work despite following the instructions in the previous tabs you may want to check that each of your themes meets the prerequisites below in
Themes > Layout Templates > Mini-Profile.
First, ensure that opening tag of your mini-profile template includes the
$[miniprofile_class] variable in its class. On the default ProBoards theme it should look something like this:
<div class="$[miniprofile_class]">
Next, make sure that the default
{foreach} loop for custom fields is present inside your mini-profile. It doesn't need to be visible, so you're free to add it inside a hidden element if you don't plan on displaying it or if it would mess up the appearance of your own custom template.
{foreach $[user.mini_custom_field]}
<br /><span class="$[user.mini_custom_field.content_class]">$[user.mini_custom_field.name]: $[user.mini_custom_field.value]</span>
{/foreach}
Beyond that you can do whatever you like to the mini-profile template for the most part and it shouldn't negatively impact the plugin.
The following is a list of available variables for use in the HTML section of the mini-profile creator and their definitions. Adding any of these to a mini-profile will generate the content described in its definition in place of the variable so long as the information that variable outputs is visible to you.
To reference your forum's custom profile fields you can use
$[user.customfieldname], substituting "customfieldname" with your custom field's name. You'll need to type the name in all lowercase with no spaces and only use characters A-Z and 0-9.
For example,
Mini-Profile Theme becomes
$[user.miniprofiletheme]. This will output the value of the custom field. In the case of this example, it'll be the name of the mini-profile theme you've chosen in your profile.
IMPORTANT NOTE: These will only work if you followed the steps in the Installation tab of this window on each of your themes. Any themes that do not include the template code specified there will not have these variables replaced in the mini-profile.
$[user] |
User's display name link. |
$[user.age] |
User's age (if visible to you). |
$[user.avatar] |
User's current avatar. |
$[user.badges] |
User's list of badges. |
$[user.birthday] |
User's date of birth (if visible to you). |
$[user.color] |
Hex color of user's group. If user is not in a group this will return inherit. |
$[user.custom_title] |
User's custom title. |
$[user.email] |
User's email (if visible to you). |
$[user.gender.image] |
Image associated with the gender selected in the user's profile (if available). |
$[user.gender.text] |
Name of gender selected in the user's profile (if available). |
$[user.group.name] |
Name of user's current display group. |
$[user.group.stars] |
Star images associated with user's current display group. |
$[user.id] |
User's numerical ID. |
$[user.instant_messenger] |
User's list of instant messengers specified in their profile (if available). |
$[user.invisible] |
Returns 1 if a user is invisible. More useful for Javascript. |
$[user.ip] |
User's IP address (if visible to you). |
$[user.is_online] |
Returns Member is Online if user is currently online. |
$[user.is_staff] |
Returns 1 if a user is designated as staff. More useful for Javascript. |
$[user.last_online] |
Timestamp showing when user was last online. |
$[user.likes] |
Number of likes this user's posts have received. |
$[user.location] |
Location specified in user's profile. |
$[user.name] |
User's display name in plain text. |
$[user.personal_text] |
User's most recent status. |
$[user.posts] |
User's post count. |
$[user.rank.name] |
User's current posting rank. |
$[user.rank.stars] |
Star images associated with user's current posting rank. |
$[user.registered_on] |
Timestamp showing the date/time the user registered on the forum. |
$[user.registered_on_short] |
Condensed version of user's registration date. |
$[user.social_network] |
User's list of social networks specified in their profile (if available). |
$[user.username] |
Outputs the user's login username in plain text. |
$[user.warning.bar] |
User's warning bar (if it exists). |
$[user.warning.level] |
User's current warning level (if visible to you). |
$[user.website] |
Website specified in user's profile. |
You can utilize the
$(this) variable in the Javascript component to target the mini-profile
<div> element. For example, if you wanted to add a class to the mini-profile you can use:
$(this).addClass('class-name-here');
Profile variables can also be used in the Javascript component in this plugin. In Javascript the value
undefined is used to signify that a value doesn't exist for the variable you've specified. With this in mind you can use profile variables in Javascript conditional statements within the plugin similar to how they're used in the actual layout templates section of the admin area.
- if(variable) will only run if the variable you specify has a value.
- if(!variable) will only run if the variable you specify has no value.
Example 1 (variable has value):
if(user.group){
$(this).find('.group').show();
}
If the user has their group displayed in their profile the above Javascript would make the HTML below visible if you had it hidden with CSS.
<div class="group">$[user.group.name]<br />$[user.group.stars]</div>
Example 2 (variable has no value):
if(!user.gender){
$(this).find('.gender').hide();
}
If the user's gender isn't visible the above Javascript would hide the gender icon generated by the HTML with the "gender" class below.
<div class="gender">$[user.gender.image]</div>