God Of Lego

But didn't sliske supposed to have used the stone to lure Strosaph? thats surely a huge torment. We were present in the room. So by logic we wouldn't even need to be in his mind. We are already very real infront of him. Its like getting a striptease but not being able to touch. But knowing Jagex they probably don't even know themselves. Probably just waiting for the better idea to do.

I don't think that proves anything. We have used the stone, Guthix has used the stone, That random fremminik from cutscenes in WGS used to stone, people in Kethsi used the stone - its hardly a full roster of who has and has not used that stone that appeared in the battle. But what if it were based on recent torments? We are currently there so that doesn't matter to much. We are already a torment to it. That's a possibility, but I'd hardly call it proof. I mean we don't fully known the history of the Stone, we know it changed hands several times during the godwars between Zamorak using it to ascend at the start and Saradomin using it to heal people mid-war and Guthix using it to end the fight. Equally I wouldn't exactly call Zamorak or Saradomin 'recent' torments their last use of the stone is between 2169 and 6169 years ago - since the 5th age was 169 years and the 4th age was ~2000 and the 3rd age was ~4000 A factor that would offer a counter is it took 3 dragonkin to kill Lucien and he hadn't even ascended, whilst 1 dragonkin was enough to pose a serious threat (serious enough that they all fled pretty quick) to the gods at Sliske's little party, which could infer they'd gained more strength which would in turn mean more stone usage between the events of rotm and then. from the FAQ Q: What's the significance of Lucien (False User) appearing in the final fight?Mod Raven: The Dragonkin are connected to the False Users via their curse, Lucien is one of the more recent False Users and is therefore deeply imprinted upon them. Zamorak and Saradomin are present for similar reasons. Sounds like it can be a possibility then.

I don't think that proves anything. We have used the stone, Guthix has used the stone, That random fremminik from cutscenes in WGS used to stone, people in Kethsi used the stone - its hardly a full roster of who has and has not used that stone that appeared in the battle. But what if it were based on recent torments? We are currently there so that doesn't matter to much. We are already a torment to it.

Sliske wasn't part of the false users proving he doesn't have the stone? maybe. Or that he has not used it.

Makes me wonder what the developers are actually doing or have done.

That Q and A just shows Jagex is full of poop to be honest. So unorganised.

Not everyone has played RuneScape.

120 is a stupid number anyway.

99 is already tormenting for some. Never mind 120.

Now thats a nice job to have!

Dancing for Charms

Well most of runescapes colour looks like its been pooped on

Sure, lemme just pull up the highscores and type in illilililil real fast... Oh I died. Nevermind, don't need to know anymore. Combat formula will never fix that. Who would stay in the wild while searching anyway. They could easiely add an highscore tab. Click play to search. I could guestimate most levels from anyone I ran into in the wildy. I knew instantly who was maxed and was going to wreck my face back when I was a level 90~ trying to train agility and I also knew instantly who was a non-threat. Now I see a level 200 and I just log instantly. Even if they're some 45hp 99 magic/99 defence account with 1 prayer. Because now I have no idea if my enemy likely has turmoil, what their melee stats are, what their HP level is, what quests they likely have done. Nothing. Zilch. No information. They can either be a huge threat or an annoying fly I can swat away myself. I don't know. About searching in the wildy: Lemme just ask them kindly to stay where they are while I leave the wilderness, search them up, decide if I want to fight them or not, and return to where they were. Ever since they introduced the spell and showed that they had the ability to show other players' levels in game I always thought we should be able to right click "inspect" players for their skills without having to use a magic spell to do so. The should just have an examine thats active in the wild.

Sure, lemme just pull up the highscores and type in illilililil real fast... Oh I died. Nevermind, don't need to know anymore. Combat formula will never fix that. Who would stay in the wild while searching anyway. They could easiely add an highscore tab. Click play to search.

Or people should just use the highscores.

For some reason my crew has not leveled up past level 5! I bought them like 6-7 days ago. It got to level 5 first voyage. Nothing after that.

200CB should not of been there anyway. Simple. If 75% say no, its common sense that they did wrong.

They don't see the problem with that logic? They do most of the work. Just to quickly deposit when they get bonus XP. Why don't they only train divination with bonus XP.

If the treasure is in a dedicated place. It would be camped. If its in an open public area where other npcs and objects are. It would be better.

I just hope it gives decent bonus XP. Just because of the fact I hate theiving and hunter. Mind numbing.

I think they should have a system where they can earn the previously not claimed items each years holiday event. For example if you have 2009-2013s, you could get 2008 in 2014s holiday event then because you have that. Next year you get 2007. It builds backwards until you claim them all. meaning if you started in 2009 it would take you 7-8 years to get all event items whilst keeping up with new ones.

I dont think they've ever been confident, more like stuborn and ignorant.

At least it gives us a high level something. Smithing is greatly needed there.

Whats best to spend my resources on first in the loop region?

What I hate about this is that they are focusing developer time on yelps. I don't want an awful quest dedicated to killing him. Just make a nice cutscene of him getting ripped inside out for when we log in.