There could be a multitude of issues, wrong object id's, some servers had like coordinate checks for the stairs, those could be off.
|
Only 3 of the 5 of my stairs at barrows work. I don't understand what the issue is...
Veracs and Torags stairs do not work once you've entered their crypt yet the other 3 do?
Whats going on?
Barrows.java:
Code:public static int[][] barrowData = { /** ID Coffin X Y Stair X Y */ {1673, 20720, 3556, 9716, 20668, 3574, 3297}, /**Dharoks*/ {1677, 20772, 3575, 9706, 20672, 3557, 3297}, /**Veracs*/ {1672, 20770, 3557, 9700, 20667, 3565, 3288}, /**Ahrims*/ {1676, 20721, 3568, 9685, 20671, 3554, 3282}, /**Torags*/ {1674, 20722, 3537, 9703, 20699, 3577, 3282}, /**Guthans*/ {1675, 20771, 3549, 9682, 20670, 3566, 3275} /**Karils*/ };ActionHandler.java:Code:public void useStairs() { if (c.inBarrows()) { switch (c.objectId) { case 20668: c.getPA().movePlayer(barrowData[0][5], barrowData[0][6], 0); break; case 20672: c.getPA().movePlayer(barrowData[1][5], barrowData[1][6], 0); break; case 20667: c.getPA().movePlayer(barrowData[2][5], barrowData[2][6], 0); break; case 20671: c.getPA().movePlayer(barrowData[3][5], barrowData[3][6], 0); break; case 20669: c.getPA().movePlayer(barrowData[4][5], barrowData[4][6], 0); break; case 20670: c.getPA().movePlayer(barrowData[5][5], barrowData[5][6], 0); break; } } }
Code:case 6702: case 6703: case 6704: case 6705: case 6706: case 6707: case 20672: case 20667: case 20668: case 20669: case 20670: case 20671: case 20699: c.getBarrows().useStairs(); break; case 10284: c.getBarrows().useChest(); break;
I also noticed that I can climb down the stairs but not up the stairs in the Slayer Tower even though there is code for it...
There could be a multitude of issues, wrong object id's, some servers had like coordinate checks for the stairs, those could be off.
Barrows.java:
Code:public static int[][] barrowData = { /** ID Coffin X Y Stair X Y */ {1673, 20720, 3556, 9716, 20668, 3574, 3297}, /**Dharoks*/ {1677, 20772, 3575, 9706, 20672, 3557, 3297}, /**Veracs*/ {1672, 20770, 3557, 9700, 20667, 3565, 3288}, /**Ahrims*/ {1676, 20721, 3568, 9685, 20671, 3554, 3282}, /**Torags*/ {1674, 20722, 3537, 9703, 20699, 3577, 3282}, /**Guthans*/ {1675, 20771, 3549, 9682, 20670, 3566, 3275} /**Karils*/ };ActionHandler.java:Code:public void useStairs() { if (c.inBarrows()) { switch (c.objectId) { case 20668: c.getPA().movePlayer(barrowData[0][5], barrowData[0][6], 0); break; case 20672: c.getPA().movePlayer(barrowData[1][5], barrowData[1][6], 0); break; case 20667: c.getPA().movePlayer(barrowData[2][5], barrowData[2][6], 0); break; case 20671: c.getPA().movePlayer(barrowData[3][5], barrowData[3][6], 0); break; case 20669: c.getPA().movePlayer(barrowData[4][5], barrowData[4][6], 0); break; case 20670: c.getPA().movePlayer(barrowData[5][5], barrowData[5][6], 0); break; } } }
Code:case 6702: case 6703: case 6704: case 6705: case 6706: case 6707: case 20672: case 20667: case 20668: case 20669: case 20670: case 20671: case 20699: c.getBarrows().useStairs(); break; case 10284: c.getBarrows().useChest(); break;
Other thing to check is object distance. Sometimes the stairs are rotated on an odd angle meaning the default value isn't large enough for the click to register. In your click object class or whatever handles object distance clicking just increase it if the id's are in there and if not add the 2 in.
Its not object distance, I'm assuming you're using the brutality source. The problem actually affects quite a few different objects including the furnace as well. In your actionhandler under search the object cases and you'll find something in the lines of "break;" just delete the unnessary shit and all your objects will be fixed.
My best piece of advice is to rid far away for that source, its horribly written and far from stable.
You need to actually debug the problem. This isn't going to be solved by posting all your barrows code in here.
Write some simple code that prints into the console when you click objects displaying all the information you might need to find an issue for example:
ID, x, y, type, distance etc
Then go click the object and compare the code with the data you've got from debugging
Take a look of object id's if there the same as in the codes..
The source already had debugging methods implemented:
Problem is, when you click the non working stairs in debug mode they do not tell you the information about the object. it displays "0"Code:if ((c.getRights().isDeveloper() || c.getRights().isOwner()) && Config.SERVER_DEBUG ) { c.sendMessage("<col=255>[SERVER DEBUG] " + " - FirstClickObject: X: " + c.absX + " Y: " + c.absY + " Height: " + c.heightLevel + " ObjectID: " + objectType); }
Displays proper information for the working objects though.
« Previous Thread | Next Thread » |
Thread Information |
Users Browsing this ThreadThere are currently 1 users browsing this thread. (0 members and 1 guests) |