Bounty Hunter Archive
Thread: Until the Producers decide otherwise, Kashyyyk stays how it is.
wrote:
Until the Producers decide otherwise, Kashyyyk stays how it is.
I thought the problem with droids on Kash was a technical one. Which is BS of course we’re just dealing with planet instance and position information. If planet == kash ask client for instance then return info to BH. If that was a technical problem we are in trouble. Hell, that could have been solved by sending tagged info client to client through the chat channel if the droid returned “Due to too many life signs….”
But this statement makes it obvious it's by design.
So what the hell, guess it's really just to give jedi a reason to buy the box. And since player informant networks popped up and screwed up the plan we get publish 20.
Message Edited by ObiQuixote on 07-18-2005 01:02 AM
I would simply be happy with them a) fixing the los buggs on the trails, or b) banning those people (BH's and Jedi) that use them.
ObiQuixote wrote:
wrote:
Until the Producers decide otherwise, Kashyyyk stays how it is.
I thought the problem with droids on Kash was a technical one. Which is BS of course we’re just dealing with planet instance and position information. If planet == kash ask client for instance then return info to BH. If that was a technical problem we are in trouble. Hell, that could have been solved by sending tagged info client to client through the chat channel if the droid returned “Due to too many life signs….”
But this statement makes it obvious it's by design.
So what the hell, guess it's really the way it is to give all jedi a reason to buy the box. And when player informant networks popped up that screwed up the plan and now we got publish 20.
Cpl_Fisher wrote:
I would simply be happy with them a) fixing the los buggs on the trails, or b) banning those people (BH's and Jedi) that use them.
ObiQuixote wrote:
wrote:
Until the Producers decide otherwise, Kashyyyk stays how it is.
I thought the problem with droids on Kash was a technical one. Which is BS of course we’re just dealing with planet instance and position information. If planet == kash ask client for instance then return info to BH. If that was a technical problem we are in trouble. Hell, that could have been solved by sending tagged info client to client through the chat channel if the droid returned “Due to too many life signs….”
But this statement makes it obvious it's by design.
So what the hell, guess it's really the way it is to give all jedi a reason to buy the box. And when player informant networks popped up that screwed up the plan and now we got publish 20.
Agreed.
wrote:
Until the PLAYERS decide otherwise, Kashyyyk stays how it is.
Fix'd to how it should be.
Ehh, come publish 20 I don't see why you would stay on the trails when there is much better (and visibility free) exp to be had elsewhere. I for one will be kicking Kash to the curb and hitting lok or dant. If you're careful I see no reason why paddies can't grind twice as fast as kash with zero vis and zero BH'ers...
Hopefully this will translate to less jedi hiding on kashyyyk, and hence less people abusing the LOS exploit.
I am on Kettemoor, you can read my reports.
Plse help to make my gaming experience enjoyable, I at least play by the rules.
Oh and I am cancelling my account for now, I will allow it to expire and renew manually only if I am shown that SOE is genuine in its desire to enforce the rules of the game and higher community standards.
I am on Kettemoor, you can read my reports.
Plse help to make my gaming experience enjoyable, I at least play by the rules.
Oh and I am cancelling my account for now, I will allow it to expire and renew manually only if I am shown that SOE is genuine in its desire to enforce the rules of the game and higher community standards.
you sir are an idiot.
ObiQuixote wrote:
wrote:
Until the Producers decide otherwise, Kashyyyk stays how it is.
I thought the problem with droids on Kash was a technical one. Which is BS of course we’re just dealing with planet instance and position information. If planet == kash ask client for instance then return info to BH. If that was a technical problem we are in trouble. Hell, that could have been solved by sending tagged info client to client through the chat channel if the droid returned “Due to too many life signs….”
But this statement makes it obvious it's by design.
So what the hell, guess it's really just to give jedi a reason to buy the box. And since player informant networks popped up and screwed up the plan we get publish 20.Message Edited by ObiQuixote on 07-18-2005 01:02 AM
It is a technical problem since waypoints do not carry dungeon names and instance numbers. The waypoint system was never designed for instances. To solve this problem the waypoint system needs a revamp. The problem is the waypoint system is tied very closely to a lot of other systems (/waypoint, global vendor search, missions / quests, house placement and user interface, to name a few). The problem probably isnt the addition of two more fields to a waypoint to represent dungeon and instance, but the effects this might have on the other systems and the testing involved.
SOE would need to dedicate a developer to the implementation / testing of this. Unfortunately, in software development usually the work time available is less than the work time needed to complete all changes, so a priority list is made - and face it or not, seeing professions as BE, tailor, CH, commando, scout and entertainers (just to name a few), this problem has and should have a very low priority. BH is not nearly as broken as other professions.
mclouj wrote:
Ehh, come publish 20 I don't see why you would stay on the trails when there is much better (and visibility free) exp to be had elsewhere.
aekeem wrote:
mclouj wrote:
Ehh, come publish 20 I don't see why you would stay on the trails when there is much better (and visibility free) exp to be had elsewhere.
because you can run a macro while afk and grind your jedi with pretty much zero chance of a bh running through every instance, tabbing through every possible target to find you. why were you down there in the first place?
The question is if a Jedi is group-grinding with friends to avoid visibility after pub 20, why would he stay in the trails over night to generate a flashing "hunt me now" sign before hunting with his group mates on a regular planet the next day?
TrebuhAragorn wrote:
only one solution for kashyyyk:
make it to a real quest-planet where only the quest-rewards are motivation enough.
reduce XP on kashyyyk by 50 - 100% !!!
then all other discussions will stop.
/agree
Remove ALL xp from Kash for everybody. Leave it as a quest planet, one that everbody can enjoy when they want to. Jedi that want to grind can do so anywhere else in relative peace with the loss of grp vis, and any jedi that does get vis deserves to be hunted.
Problem solved - over to the devs..............