Skip to content
View in the app

A better way to browse. Learn more.

Tip.It Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

icebox84

Members
  • Joined

  • Last visited

  1. 1/14/10 Edit: Only working half the time. Don't know why. I haven't change anything. Now its doing what the 2.0 ver did. It goes strait to a blank white page with a small java error link at the top left corner. I have to keep trying to load it until it finally goes through. I click on the link, then click on details and here is what I get: Java Plug-in 1.6.0_17 Using JRE version 1.6.0-oem-b104 Java HotSpot(TM) Client VM User home directory = C:\Users\Bobby ---------------------------------------------------- c: clear console window f: finalize objects on finalization queue g: garbage collect h: display this help message l: dump classloader list m: print memory usage o: trigger logging q: hide console r: reload policy configuration s: dump system and deployment properties t: dump thread list v: dump thread stack x: clear classloader cache 0-5: set trace level to <n> ---------------------------------------------------- java.lang.NullPointerException: null pData at sun.awt.windows.WToolkit.eventLoop(Native Method) at sun.awt.windows.WToolkit.run(Unknown Source) at java.lang.Thread.run(Unknown Source) java.lang.NullPointerException: null pData at sun.awt.windows.WToolkit.eventLoop(Native Method) at sun.awt.windows.WToolkit.run(Unknown Source) at java.lang.Thread.run(Unknown Source) java.lang.NullPointerException: null pData at sun.awt.windows.WToolkit.eventLoop(Native Method) at sun.awt.windows.WToolkit.run(Unknown Source) at java.lang.Thread.run(Unknown Source) java.lang.NullPointerException: null pData at sun.awt.windows.WToolkit.eventLoop(Native Method) at sun.awt.windows.WToolkit.run(Unknown Source) at java.lang.Thread.run(Unknown Source) exception: No JVM to relaunch applet. java.lang.Exception: No JVM to relaunch applet at sun.plugin2.main.client.PluginMain$StartAppletListener.appletSSVValidation(Unknown Source) at sun.plugin2.applet.Plugin2Manager.fireAppletSSVValidation(Unknown Source) at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source) at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Exception: java.lang.Exception: No JVM to relaunch applet exception: No JVM to relaunch applet. java.lang.Exception: No JVM to relaunch applet at sun.plugin2.main.client.PluginMain$StartAppletListener.appletSSVValidation(Unknown Source) at sun.plugin2.applet.Plugin2Manager.fireAppletSSVValidation(Unknown Source) at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source) at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Exception: java.lang.Exception: No JVM to relaunch applet I'm running Windows vista home, Firefox 3.5.7, Java ver 6 update 7. reply if you need any more info 1/11/10 Very nice program. I'm having to use the beta because I couldn't get the 2.0 to work. but thats fine. Can't seem to get the planer to work though. But thats also ok, because I think its like that same planner in rs already. But over all I love it. One suggestion though. I've posted this b4 on the runescape forums with no success. If you look at the first page of the Grand Exchange you will see a scroll bar listing the current ups and downs of items. It would be so great if a add on could be made that put that on top or bottom of rs screen.
  2. Hello Tipit. First I'd like to say the method I'm going to show you later in this guide I did not create. I was told this by someone else. I thought about it and it made perfect scene. But it also got me thinking a lot about the way things work on my long journey to 99 wcing. I don't have many things I'm good at but there is one skill I have and I'm very good at it. I'm kinda like Syler on Heroes. I can look at things and figure them out. I've always had this skill and its only gotten better as I learned to use it. Anyways my point is I'm not saying what you are about to read is all fact, but I'm pretty sure I'm right about most of it. Anybody is more than welcome to debate issues with me here or if you agree. Just post your comments. I'd like to start by clearing up a few common misconceptions about wcing in rs, the reason why they are false and why people think they are true. First: The biggest and worst common misconception is that cutting any tree all by yourself will somehow get you logs faster then if you were shearing that tree with 1 or more other players. THIS IS FALSE!! Reason people believe it is true: When making a game the developers try to stay with the natural realm of physics. This is to make the game more realistic and believable. But this can't always be done. Trying to stick with just wcing; when trees fall(chopped down) in real life, they don't take just a few minutes to grow back like in runescape. Runescape knows we need trees quicker than it takes a real tree to grow. Yet runescape does keep with the face that a tree when cut does eventually get cut all the way down. The problem with this, is it leads people into believing there is only a certain amount of logs in each tree. I understand why people think this. After all in real life you can only get so much wood from an individual tree. Why it is not true: We have to think from a programmers prospective. (BTW I'm in school for Programming) We already know that how many logs you do get is random. Its different every time. But what non-programmers don't know is in order to store an random amount of logs in each tree all over runescape, you would have to create a variable for each tree.Think of a variable as a box you can put information in. This box takes up memory. And all programmers know the less memory the better. Now we are talking about creating literally 10's of thousands of variables, not only for each and every tree in runescape but also for each world(or server). Reason we have to create these variables is because each time a new tree is created, we need a box to store how many logs that tree has. How can we still make the tree still give out a random number of logs without creating all these variables which waste memory and system resources. I can think of only 2 feasible ways to do this. The first, which I rule out immediately is a time base tree. The the object tree is created anew, it waits for a player to start chopping on it and the timer starts counting down. But what if the player leaves the tree for another. Does the time stop? It has too. None of us ever seen a tree fall all by it self. So, if it stops, does the timer restart when the player or another player starts chopping again. Noooo. If so then we could just go back and forth between trees and they would never fall, because we keep resetting the timer. So then, we could create a variable to hold the current time left. But then we get back to the first issue with wasting memory. That leaves one final option. A very simple method. Random number. I will try to explain this the best I can. In object oriented programming objects are made and used over and over again. So most likely there is only one actual tree in runescape. And this one tree is just used over and over again just with different values representing the different types of trees. a rough example of what the object tree looks like. I don't know java so i don't know what the actual code would look like. Example: CODE Tree; tree coordinates = ? lvl needed to cut = ? image = ? <---the image it uses to identify to use what tree it is get log if get number = 10,20 knock down tree if get number = 15, 25, 35 so on.... So when programming the mage trees north west of ledgends guild now we need to call the object tree say its named "Tree()" looks something like this: Tree(1234,5677; 75; magic_color; return number) 'Tree' calls the object into existence, the '1234,5677' is the coordinates of the tree(where to place it), '75' would be the lvl needed to cut it, 'magic_color' of course would be the image used for what kind of tree it is, and lastly the most important 'return number' Return number is the number the tree receives from a player when its being chopped. Where does this number come from? Probably the axe you are using , seeing how different axes give you a different chopping rate. To put this a plainly as I can and not to go on forever trying to explain every detail, try to think of chopping like a game of dice. You walk up to a tree and start cutting. Every chop you roll a 50 sided dice.(Remember I just guessing at these numbers. I could never know what the real values are without looking at the source code.) If the dice, following the example above, lands on a 10 or 20then the tree gives up a log. If you land on a 15,25, or 35 then get a log and knock down the tree. If you hit any other number nothing happens you keep on chopping. Yes there is even one in there for the bird nest but even more rarer. Btw, real quick, when you hear a crunching sound and u get a log right before a tree falls you are the one that rolled the unlucky number and knock the tree down. The lower your lvl the higher the chance of hitting that unlucky number. All this leads me to my main point. How can me shearing a tree with another player make me get logs slower when the tree is interacting with us individually. The only ways if affects you is is when have have more than one person on a single tree the chance of that tree getting knock down sooner is more. This is because you have not one dice rolling for that unlucky number but multiple dices at once. Sense you don't get logs any faster whether you are shearing a tree or not you might as well all shear the same tree. This is it!! How I get logs faster!! What happens if everyone shears the same tree? Well, in the long run you get more logs per hour which means more xp and cash per hour. Why is this you say? Well if we have 4 trees. 10 people cutting on 4 trees. All 10 people cut on tree number 1. After 20 secs it falls. Everyone moves to tree 2. It falls after 60 sec. Now on to tree 3 everyone goes. It falls after only 10 sec. Now last tree number 4. It last 45 sec. On no last trees gone, but wait , whats this enough time has passed for the number 1 tree to grow back. "Everyone to tree 1!" And so the process is repeated. Not that I'm saying you will never run out of trees, but with this method it happens a lot less. And. I mean A LOT less. Trust me most of the time at least 3 trees stay standing at all times. Finally, a last few common misconceptions about wcing. This one is only a rumor but from what I've seen it seems to be true, but could just as well not be. Others disagree, though. The rumor is that all trees except magic trees give a higher cut rate the higher the lvl you are. Meaning the higher your lvl the better you chances of hitting the lucky number more often that gets you a log. So, the rumor is that magic trees are the exception. As I lvled my way closer to 99 I too have noticed no change in my logs per hour consumption. Although, yew logs come at a considerably higher rate. So, from lvl 75 to lvl 99 you get virtually the same cut rate. I say virtually because I believe if there is an increase, it is so small it couldn't be more than 5 logs more per hour. Which leads me to the last Some seem to think that the cut rate is the same for a dragon hatchet verses a rune hatchet. This seems to be true, but it of course is not. With my tests I get virtually the same amount of logs per hour for each type. Strange, I know, but true. But this is False according to this: Source. Thank you mister_moocky. Everyone help spread the word!!!! Thank you for your time. :thumbsup: :thumbsup: :thumbsup: :thumbsup:

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.