Bounty Hunter Archive
Thread: A Solution to the Kashyyk Problem From a Jedi
Message Edited by OmniReaperr on 07-20-2005 10:12 AM
OmniReaperr wrote:
Using droids on kashyyk will probably never happen...it's against SWG canon, kashyyk is supposed to be all but devoid of such things. However, there can be another way.
I'm not sure what you mean here. Wookiees are a fairly high-tech race, and it would be the BH bringing the droids there.
If we're talking canon (the movies)- nothing is shown that would say "you can't use droids."
If we're talking EU (the books, Happy Meal fliers, Fruit Loops box backs, etc) then...maybe...I've read a lot of Star Wars books and eaten a lot of happy meals, and I've never heard that droids don't work on Kashyyk - or anything remotely close to that.
Agreed, the wookies are fairly advanced technologically...however their jungles are "sacred" if I remember correctly, wouldn't droids like that sully their sanctified state? Also, speaking from a realistic standpoint, I doubt if they'll ever allow droids on kashyyk...they've said so. This is simply a solution that could satisfy all parties without keeping kashyyk as a very bad itch that we can't scratch, so to speak.
TheMadCoder wrote:
OmniReaperr wrote:
Using droids on kashyyk will probably never happen...it's against SWG canon, kashyyk is supposed to be all but devoid of such things. However, there can be another way.
I'm not sure what you mean here. Wookiees are a fairly high-tech race, and it would be the BH bringing the droids there.
If we're talking canon (the movies)- nothing is shown that would say "you can't use droids."
If we're talking EU (the books, Happy Meal fliers, Fruit Loops box backs, etc) then...maybe...I've read a lot of Star Wars books and eaten a lot of happy meals, and I've never heard that droids don't work on Kashyyk - or anything remotely close to that.
Droids do not work in Kashyyyk because of a technical problem and no developer resources being dedicated to that problem, not because it is Star Wars canon that droids dont work on Kashyyyk. Its all a matter of resource allocation and priorities, not a fact of devs wanting to support Jedi and hurt BHs.
Eskie wrote:
Droids were intended to work on Kashyyyk. But the devs realized the current implementation of the waypoint system cannot handle instances, a flaw whose fix would need a lot of developer time.
Droids do not work in Kashyyyk because of a technical problem and no developer resources being dedicated to that problem, not because it is Star Wars canon that droids dont work on Kashyyyk. Its all a matter of resource allocation and priorities, not a fact of devs wanting to support Jedi and hurt BHs.
Translation: The Droids does not work because the producers wanted to trap many jedi into their web by bugging the droids there and give jedi a free grind planet as a boast to sell more ROTW copies..All about marketing.
StormTroopercpt0 wrote:
Eskie wrote:
Droids were intended to work on Kashyyyk. But the devs realized the current implementation of the waypoint system cannot handle instances, a flaw whose fix would need a lot of developer time.
Droids do not work in Kashyyyk because of a technical problem and no developer resources being dedicated to that problem, not because it is Star Wars canon that droids dont work on Kashyyyk. Its all a matter of resource allocation and priorities, not a fact of devs wanting to support Jedi and hurt BHs.
Translation: The Droids does not work because the producers wanted to trap many jedi into their web by bugging the droids there and give jedi a free grind planet as a boast to sell more ROTW copies..All about marketing.
Exactly that part is what you did not understand from my post. The droids were not bugged intentionally, they worked for the first few hours of RotW. But when a Jedi was in an instanced region, the waypoints would be royally messed up and of no use to the BH. Making up a story about too many life signs was a quick fix to cover up the bugged waypoints, nothing more, nothing less.
Of course, after the initial bug was discovered, somebody has chosen to put this issue on a low priority. But the initial bug was not introduced on purpose.