Items And Loot Archive
Thread: Is using the /unstick bug to get the DJK missions a bannable offence?
Nevermind that would make sense.
I dont think its an exploit..
Wait a minute, are you both saying anytime someone can't complete a quest and they find a workaround that lets them continue somehow they are exploiting? Because that would mean you are going to have a whole bunch of people banned here pretty soon as I've seen people use workarounds since the begining of this game just to complete the most idiotic quests. Heck I've read posts by devs telling them how to get around problems with quests until it's fixed....somehow this is different because why.....people are sometimes looting great stuff? Like Isaid, devs might need to finally fix the ability of players being able to reset missions, or maybe remove the DArk Jedi from being the main NPC you have to kill. I think the second option is what needs to happen, it's stupid that a little mission in the middle of nowhere has you trying to kill what is possibly the toughest NPC in the game lol.
Problem doesn't lie in the fact people are doing the quest, it's that the quest has an NPC in it that can drop good loot. If the Krayt in that one quest would have dropped loot pre-CU, would you have considered it an exploit if people killed and looted pearls?
WookieOgre wrote:Wait a minute, are you both saying anytime someone can't complete a quest and they find a workaround that lets them continue somehow they are exploiting? Because that would mean you are going to have a whole bunch of people banned here pretty soon as I've seen people use workarounds since the begining of this game just to complete the most idiotic quests. Heck I've read posts by devs telling them how to get around problems with quests until it's fixed....somehow this is different because why.....people are sometimes looting great stuff? Like Isaid, devs might need to finally fix the ability of players being able to reset missions, or maybe remove the DArk Jedi from being the main NPC you have to kill. I think the second option is what needs to happen, it's stupid that a little mission in the middle of nowhere has you trying to kill what is possibly the toughest NPC in the game lol.
Problem doesn't lie in the fact people are doing the quest, it's that the quest has an NPC in it that can drop good loot. If the Krayt in that one quest would have dropped loot pre-CU, would you have considered it an exploit if people killed and looted pearls?
Don't forget people still have to kill these NPC's, it's not like they are going to roll over dead for you so you can loot them. And if you are worrying about the uber chain rooting, I'm sure the devs will fix root just because of things like this.
/agree If they did not want you to do the mission they would have just removed the NPC. I think its a bug. I have not tried the /unstick or even care to..lvl 3 toons just dont last very long.
IF this is the case and you are not supposed to be getting the mission then using the unstick command to circumvent the system would be an exploit.
If the quest requires you to do A & B before you can do C, and you use unstick to do C with out first doing A & B, or you use unstick to do C over and over again and the force field is there to prevent you from farming the mission over and over, then yes you are exploiting.
Message Edited by ObiQuixote on 06-14-2005 08:38 AM
ObiQuixote wrote:
I'm not saying they are exploiting, but that it may not be a bug that they can't get past a force field. There may be something else required to get the quest or it may be intentionally gating people for reasons only the devs know.
IF this is the case and you are not supposed to be getting the mission then using the unstick command to circumvent the system would be an exploit.
I agree if the devs intentionally put up a gate to prevent you from doing the quest, circumventing that should be an exploit. I suggest you go to the prison and look into the jail cell and tell me if you think it's anything except a bug......just like all the bugs in every quest on Wookie world, this is absolutely no different. Sometimes the devs make mistakes even with them being perfect as they usually are lol.
Once you look at the jail cell I think you will come to the conclusion that it's a glitch....As I said, if this was truely the way devs are tryig to prevent anyone from doing a stupid quest that doesn't give anything,there are easier ways to prevent someone from doing this quest plus they would mention it in the patch notes if it truely was that big of a deal. Remember, this was never an issue until suddenly the only thing that drops good loot is the highlevel mobs that one hit kill you. You can find these high end mobs on Dant anyways, it's really no big deal unless the players just think loot like this shouldn't exist.
"If the quest requires you to do A & B before you can do C, and you use unstick to do C with out first doing A & B, or you use unstick to do C over and over again and the force field is there to prevent you from farming the mission over and over, then yes you are exploiting."
Well then I hope this puts it to rest, you have to do A and the next step is B but there is no way to talk to B. A is telling you to goto B but there is still no way to talk to B. If someone jumped ahead in a quest by using the method you suggest I agree that is an exploit......lucky for everyone doing the missions that is absolutely not happening.
Message Edited by WookieOgre on 06-14-2005 10:48 AM
Let me ask you this. If a player that was engaged in combat or was not glowy used the /unstick command to get past the forcefield to the Village would you not consider that an exploit? I would think so.
It seems that they only difference between this scenario and using /unstick to get to the DJK npc is that you don't know why the forcefield is there. Circumventing an in obvious game mechanism to your advantage and rationalizing that you are using a work around for a bug does not mean it isn't an exploit. That you have to circumvent an in game system to gain a large advantage sure makes it sound like an exploit to me.
Message Edited by coronula on 06-14-2005 10:58 AM
coronula wrote:
Let me ask you this. If a player that was engaged in combat or was not glowy used the /unstick command to get past the forcefield to the Village would you not consider that an exploit? I would think so.
It seems that they only difference between this scenario and using /unstick to get to the DJK npc is that you don't know why the forcefield is there. Circumventing an in obvious game mechanism to your advantage and rationalizing that you are using a work around for a bug does not mean it isn't an exploit. That you have to circumvent an in game system to gain a large advantage sure makes it sound like an exploit to me.
Message Edited by coronula on 06-14-200510:58 AM
Some good discussion here guys
I'm minded to remember the Geo Cave in the weekbefore it was opened. There was a forcefield blocking entry to that too, but it wasn't long before players realised you could walk up to the gate, unplug your network cable, walk through, replug it, and wander round the cave, icing geonosians and kwis
This was obviously not meant to happen, and as far as I know it would have led to CSRs getting involved had they seen anyone doing it.
IMHO, the /unstick command is not part of the everyday"gameplay" aspect of the game, such as /attack or /infusion etc. Just as the /bug command is not part of gameplay; those two commands are there to help the player himself, not the player's on screen character.
I can only guess that there is a forcefield in place as perhaps the quest was determined too hard way back in a development cycle. Instead of deleting the entire quest, which could bring about continuity or coding errors, it would be far easier to simply create a physical block to the NPC quest giver, meaning that the quest was still in code, but it was impossible to start it. It's the most logical reason why there is a simple force field to stop characters from starting the quest, as opposed to removing it entirely.
Playing devil's advocate here; I am sure that the devs wouldn't sit around a table thinking "Ok, here's an idea. We set up the only quest in the game which yields a very high level mob, with great loot drops. Then we make it that the only way to complete the quest is to utilise a technical function of the game, not a gameplay function". Doesn't sound right does it? Imagine if the only way to complete Half Life was to make use of the console to lower the gravity enough to fly over an impassable wall. Again, doesn't sound likely at all.
Let's hope that there's someone from the SOE side who can clear this up soon.
Kev0r wrote:
Some good discussion here guys
I'm minded to remember the Geo Cave in the weekbefore it was opened. There was a forcefield blocking entry to that too, but it wasn't long before players realised you could walk up to the gate, unplug your network cable, walk through, replug it, and wander round the cave, icing geonosians and kwis
This was obviously not meant to happen, and as far as I know it would have led to CSRs getting involved had they seen anyone doing it.
IMHO, the /unstick command is not part of the everyday"gameplay" aspect of the game, such as /attack or /infusion etc. Just as the /bug command is not part of gameplay; those two commands are there to help the player himself, not the player's on screen character.
I can only guess that there is a forcefield in place as perhaps the quest was determined too hard way back in a development cycle. Instead of deleting the entire quest, which could bring about continuity or coding errors, it would be far easier to simply create a physical block to the NPC quest giver, meaning that the quest was still in code, but it was impossible to start it. It's the most logical reason why there is a simple force field to stop characters from starting the quest, as opposed to removing it entirely.
Playing devil's advocate here; I am sure that the devs wouldn't sit around a table thinking "Ok, here's an idea. We set up the only quest in the game which yields a very high level mob, with great loot drops. Then we make it that the only way to complete the quest is to utilise a technical function of the game, not a gameplay function". Doesn't sound right does it? Imagine if the only way to complete Half Life was to make use of the console to lower the gravity enough to fly over an impassable wall. Again, doesn't sound likely at all.
Let's hope that there's someone from the SOE side who can clear this up soon.
First I'll address your comparison to the Geo Cave. That was a big exploit as there was a red barrier specifically designed to make sure no one entered the cave. Devs posted it was intentionally done so they could finish balancing the dungeon and warned players from going in there. Reason why this does not apply to the current glitch is because there is no forcefield like that in this case. The guy you are supposed to talk to is a prisoner behind bars. The bars do not let you pass as I would think is supposed to happen. The problem is these bars are acting as a barrier that prevents you from talking to the prisoner. Simple glitch, probably overlooked as many things are specially since this is a very obscure quest that seems to serve absolutely no purpose other than more content. I'll say this one more time, everyone needs to go try that mission and then you can tell me if you think that looks intentional. To me it looks more like an error in the code that doesn't allow us to speak through the bars.
Again, you say the best reasonable arguement is that the devs intentionally made it so we can not talk to the NPC.........first please tell me how many bugs there have been with quests lately? There are so many I've lost count. A lot of the complaints I've heard is the NPC doesn't talk to you or won't let you continue the quest.....does that mean the devs intentionally made it this way or could it be.....a bug lol. Second, how is that reasonable? What would be the reason to make the quest stop at a certain point? It can't be because the NPC is too hard. It can't be because it's too easy. It can't be because it's the only thing dropping good loot since it's not. And above all it can't be because you get free loot......you still have to kill a level 263 level mob.
You are right, devs would not intentionally make it so you have to use /unstick to progress....but like all bugs in this game you find ways around the multiple bugs anyway you can. If I have to stand on my head, rub my belly while chanting songs to get a quest done, I'll do it. The devs do make mistakes, no one is perfect. I remember doing a Paddy trial log ago that requried me to talk and do missions for Gungans....too bad they wanted to kill me everytime I went near them.....did that mean the devs didn't want me to be a Jedi lol?
I've been around this game since the start, this just does not register (to me anyways) as an exploit. The only reason why this is even an issue is because of the good loot that may/maynot drop.....if killing a level 263 mob gave no loot there would n't even be discussions. That tells me it has nothing to do with /unstick but with the ability to fight a Jedi NPC for loot, which btw anyone can do if you just go to Dant lol.