Development Cycle Archive
Thread: Weekly Roundtable Discussion (Week Ending 3-29-04)
After the Jedi changes are implemented and no longer profression based can you look into revamping the apprentice point system. There should still be a reward for players training players but there should be an alternate way to become a Master.
Maybe quest based - Do profession specific based quests and earn the AP points needed. This gives us something to do other than sitting in starports spamming and selling and buying apprentice points.
will musicians be able to dual wield slitherhorns? heheh, jk ![]()
eh?
terrific!
DVader539 wrote:
LLJK_Griz wrote:If that is true, then why did the Tusken start off as kinetic and then mysteriously change to another useless energy rifle around publish 4? Why has it taken this many months of weaponsmith and rifleman correspondents complaining before we got ANY response on this?
Thunderheart wrote:
DVader539 wrote:
Here's a real, real, real simple fix for you.
Spraystick is supposed to be Acid damage
Tusken Rifle is supposed to be Kinetic damage
T21 is supposed to be Blast damageThe correspondents and I have looked at this many times. Sorry, but its not an easy change. Damage types have a relationship to damage and by changing the damage type, it also changes the damage modifiers (numbers) and throws them out of whack. This is something Im checking to see if we can address in the weapon balance part of the larger combat balance, but I don't know what the answer might be. And in any event, concentrating on these minor things before the weapon balance isn't productive. We'll want to look at things when the combat balance is on TC.First off, thank you TH for a response to this issue. Before you read anything else in my response, please understand I am directing no anger at you, since I know you are only fielding the question, and are not responsible for the error nor ignoring the error.
With that said, LLJK_Griz makes a very valid point. If it's not an easy change, then how did the Tusken Rifle change it's damage type? If it was unintentional, then I'd like to meet the unlucky guy who by-mistake did the complex job of reprogramming it. If it was intentional, then I'd like to meet the doofus who went to all that complex work to screw up a weapon. Or is this a case of "if you had a dozen programmers sitting at a dozen terminals typing randomly, in twelve days they would reprogram a complex variable of this game"?
of course that last one was a joke. I hope...
Finally, what bass-ackwards logic made the Dev team make a weapon's stats not variable-entry based? That being, a weapon's code is a string of numbers, each number representing a stat. Like 1=energy damage, 2=heat damage, 3=kinetic damage, etc. Then a seperate function takes certain numbers during a fight and puts them through an equation set to figure out damage and such. If the Dev team made it any more complex than that, then please hire my service of logical thinking. I'll sell you my services at a good price since I'd enjoy making this game better. (p.s. I'm serious.)
After discussing this with my fellow Riflepeople, the idea of the T21 being blast damage is debatable. But a very good point was made.
T21 ws only blast for a few days and IMHO it should stay energy cause a blast rifle would be overpowered for the stuff that is sposed to be what commandos are made for taking out.
However the fact that within a week the T21 was changed from Energy to Blast and back to Energy does show just how full of [balogna] old TH is with his responces to us idiots that play this game
Oh, then we got this little doozie last Friday...
Keldarin wrote:
I just went through the revision history of those weapons [spraystick, tusken rifle] and they have never had those damage [acid, kinetic] types.
Now, please... this is complete BS. If the Dev team has screwed up, please admit it. Don't treat us like morons and try half-arsed lies. My reply to this was...
First off, an article from bloodfin.org
ranged attacks generally do blast damage (unless the weapon is an acid rifle or lightning rifle - i expect some common sense here) ... however there are 2 guns which do kinetic damage - the tusken rifle and the striker pistol
And then a weaponsmith's guide from swgcraft.com
Q. What are the damage types for each weapon?
A.
Heat: EE3 Carbine, E11 Carbine, FWG5 Pistol
Cold: SG82 Rifle
Acid: DXR6 Carbine, DX2 Pistol
Stun: Tangle Pistol, Jawa Ion Rifle
Kinetic: Striker Pistol, Tusken Rifle
Energy: All others
And finally, the piece of evidence worth a thousand words from swgcener.com
A screenshot of a King Tusken Rifle with kinetic damage!
Proof that the Devs lie and the Tusken was kinetic!
TH!!!!
Please tell me this means we could possibly see dual 1H Lightsabers!? Like Anakin wielded in AOTC.
Any updates on Dev testing of the Skill Mod (armor and clothing attachments) issues?
- Multi Skill mods where only the highest value mod listed is attaching
- Negative Skill Numbers listed on a mod
- Blank Armor and Clothing Attachments
- No stacking of same skills into one clothing item or peice of armor
- And other issues related to skill mods...
Thanks...
There seems to be a problem with weapon, armor, and clothing repairs that appeared with the activation of Publish 7. Masters in each group are reporting an apparent radical change in repair success results. Even using high quality repair tools (over 95% functionality), there seem to be very few 'minor blemish' (great) repairs. Where most would experience 60% or better of their repair results as 'minor blemishes', now are obtaining 'reduced condition' (moderate) repairs over 90% of the time. I have done 40 repairs since Publish 7 went live. My results have been 1/38/1 (great/moderate/failure). This is a complete turn around from pre-Publish 7 when I was experiencing a success distribution of 26/13/1 over 40 repairs. Same repair tool used (99.83% functionality), and approximately the same range of weapon conditions.
Was this an unintentional change (bug) introduced by some other aspect of Publish? If not, why was this change introduced and not mentioned in the notes for the Publish?
Thank You,
hope nobody minds my persistence...
Thunderheart wrote:
LeBob wrote:
TH
are you guys making any progress on the 'NPC stuck in wall' bug?
With each publish, we're making strides with this. There is some more progress made with this publish. AI code is very tricky though.
LeBob wrote:
TH
are you guys making any progress on the 'NPC stuck in wall' bug?
I've been trying to gain Jabba faction since COA III went live by hunting Valarians particularly in the slums of Mos Eisley, but they are almost 100% always stuck in the walls and therefore unatackable... plus no others will spawn since the area is spawn-capped (new word? )
I asked numerous CSRs via in-game ticket if they could do anything like 'unstick' 'despawn' 'suicide' the NPCs in question, but they said they could not...
if you guys are unable to get the primary problem fixed soon could you at least enable CSRs to do something like this?
ALSO another temporary solution (at least in the location of Mos Eisley) would be to move the spawn location 100m outside the city.... where there are no walls!.... no walls means NPCs cannot get stuck in said-nonexistant-walls
thanks
is it possible to enable CSRs to do this?
can some of the more bugged spawns be moved 100m or so temporarily?
and actually now that I think about it... your original answer is not that great either since (I think)...
AI code does not influence where a MOB spawns.... am I wrong?
to be clear: there does not seem to be a problem of the MOBs sticking themselves but rather the spawn mechanics of the game engine spawn (verb) them into the collidable environment
thanks very much
thanks again
jedi is nearly un-playable due to the threat of being Clone-camped (Grieffing beyond the scope of anything i have ever even heard of) please, jedi vs. BH missions are a very good thing, they are good content. the solution is simple, if a jedi Dies for ANY reason, give the BH a "mission incomplete" and remove all the missions and re-set there visability just as if a BH had completed it. BH will say that this is un-fair to them as there mark may be eaten by a rancor before they get there... but realy, even wreckless jedi dont die more than 1-2 times a week, so the odds of them loosing a mission do to this are minimal.
the shuttles are fine as is, the only change that would make sence would be to have Coronet move to a 5 minut timer, or to insta-travel like theed. Please leave the space routs the way they are, and the shuttle wait on atleast the far-flung planets. it does feel alot more like starwars when some one asks you for a slice/buff/training, and you have to reply "sory budd, im on the other side of the galaxy"
Thunderheart, any news on:
- GCW HQ bases? The word is that turrets still fail to fire, bases get TEF against everything (including NPCs and players of their own faction), and that players can still enter Bases with turrets up. Also, somebody mentioned that the zero HP bug is back as well. Any official word on this? For many of the people that are playing since July of last year, GCW was the only true content left. Now it is borken more that it ever was before.
- Many Droid Engineers are very dissapointed with the Publish 7, some are even completelydropping their Profs, having lost the faith in any DE Revamp. Any plans on making them (and all other players and SW fans, for that matter) happy? Publish 8 doesn't look like the right answer at the moment, since no combat droids will be introduced. And nobody will want to havea CL10-like probot droid for a combat droid - that's not Star Warsy.
- Smuggler Revamp? Any idea which publish it is scheduled for? And any idea if Devs are planning on sharing their Smuggler vision with us?
- Character copy for Test Center? Any ETA?
Thanks. Not a rant, just looking for some answers, if you have them.
same issues week after week..but to recap
- VEHICLE PAINT doesnt last long enough
- LAMPS decay to quickly and when on a vendor or in a crate
- LOK has no spawns
- NECKLACES dont display
- MISSIONS wont let some of us take them..says we are below the level which is BS