News Box
WELCOME TO MLNO!!! ... ENJOY YOUR TIME HERE! ... WHILE YOU ARE HERE, CHECK OUT OUR RPGS!
My LEGO Nexus Organization
May 01, 2026, 10:41:35 pm
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to My Lego Nexus Organization! A LEGO Universe, LEGO and My LEGO Network Fan Site! The LEGO Company does not sponsor, authorize, or endorse this site.-- New? Check out the welcome forum and get started! Got questions? PM Blade, or one of the other active members of the staff.
 
  Home   Forum   Help Arcade Gallery Rules Staff List Login Register Chat  

My path to Rank 10 and Badges ... Come Follow Along

Pages: [1] 2 3   Go Down
  Print  
Author Topic: My path to Rank 10 and Badges ... Come Follow Along  (Read 3119 times)
0 Members and 39 Guests are viewing this topic.
MysteryOrange
Apprentice
*

MLNO Reputation 0
Offline Offline

Gender: Male
Purpose: To create a better MLN environment for everyone.
Posts: 36


WWW
Badges: (View All)
Combination Topic Starter Poll Voter
« on: October 19, 2009, 04:05:02 pm »

Absolutely choose intimate friends over creating a big list.  When you're a higher rank, more people will want to be your friend, and you'll have less space on your friends list (you can only have 100 people total).  Also, intimate friends will be more likely to help you, instead of just wasting your time.  A really neat idea to document friends is to create a new document in Microsoft Excel (if you own it).  I'm doing this, and it will let you see the ranks of people you added as friends, when you deleted them, (if you did) and so on and so forth.  Hope that helped! 

P.S. Great idea for a post!
Report Spam   Logged

Cheers!
*Proud Member of "MLN Enhancers"*
Pages: [1] 2 3   Go Up
  Print  
 
Jump to:  

LEGO® is a trademark of the LEGO Group, which does not sponsor, authorize or endorse this site.
Bookmark this site! | Upgrade This Forum
SMF For Free - Create your own Forum

Powered by SMF | SMF © 2016, Simple Machines
Privacy Policy
Page created in 0.023 seconds with 12 queries.