Bio Engineer Archive
Thread: A Pretty Good Tank
Zadokk
Tue Jan 25, 2005 3:29 pm
#14
This is why I think they could provide any extra FS skill tree for BEs where they can opt for better sampling skills, experimentation points (make up for lack of skill tapes), assembly (see prev.) and maskscent ability (without the preq. scout skill tree). This would radically improve the effeciency of the BE skill point allocation issue (where some believe that SP investment is too great) and offer BEs to invest time into grinding some BE points (get out the old BSN crafter) and work towards getting the better skills and thus the right to have all these better properties 'innately'. Solves a lot of problems.
LloydPickering wrote:
I also would like it a little easier to sample from higher end creatures, I mean come on guys, a Master failing to get a sample 9/10 times on a Mutant Rancosr then killing it in 1 sample?
CTRL_ALT
Wed Jan 26, 2005 1:47 am
#15
Whoa! With this coming to all the other servers and the big krayt spawn boom...Master CH/Rifleman might actually pay off.
lammergeier
Wed Jan 26, 2005 5:10 am
#16
I just made a post-rollback attempt, and it turned out a little better (up to CL67). I'll have it on display on Rori (200m from the rebel OP, hard to miss the naboo medium there (Will o'the Wisp)) and I'll see what I can arrange for screenshots later.
EDIT:
take Merek Harvester, Blooming Jax, Mutant Rancor, and Ancient Bull Rancor.
MH/MH/BJ/BJ/MH = A (CL 34ish)
MR/MH/A/A/A = B (CL 39ish)
ABR/ABR/B/B/B = C (CL 65ish)
ABR/ABR/B/B/C = final combine
ArthurDent used Bull Rancor in place of Mutant Rancor, but I found MR's before Bulls, so I sampled accordingly. I maxxed physique experimentation on all templates, and brought intellect to 400+. all other experimentation points were discarded.
to make ONE of these took: four A-types, two B-types, and one C-type. that's 16 MH, 8 BJ, 2 MR, and 4 ABR. THIRTY field samples were needed to yield ONE end clone (no crit fails on templates or clones, but low clone-sample yield). because I'm prone to mishaps, I cloned A-types as Anglers, B's as Bantha, and C as Cu Pa... with the poor labelling on our DNA, this helped me sort out the generational DNA.
the final result was: CL67, 18574/14086/9401, AR2 51/49/5/89/89/80/5/v/v, 340-390 @ 0.38 @ 2.41, crip/diz.
the physique (specifically, fortitude) was 106% on assembly... the C-type was almost enough, but physique was too high to experiment (94% on assembly), and too low to stick AR2.
EDIT:
take Merek Harvester, Blooming Jax, Mutant Rancor, and Ancient Bull Rancor.
MH/MH/BJ/BJ/MH = A (CL 34ish)
MR/MH/A/A/A = B (CL 39ish)
ABR/ABR/B/B/B = C (CL 65ish)
ABR/ABR/B/B/C = final combine
ArthurDent used Bull Rancor in place of Mutant Rancor, but I found MR's before Bulls, so I sampled accordingly. I maxxed physique experimentation on all templates, and brought intellect to 400+. all other experimentation points were discarded.
to make ONE of these took: four A-types, two B-types, and one C-type. that's 16 MH, 8 BJ, 2 MR, and 4 ABR. THIRTY field samples were needed to yield ONE end clone (no crit fails on templates or clones, but low clone-sample yield). because I'm prone to mishaps, I cloned A-types as Anglers, B's as Bantha, and C as Cu Pa... with the poor labelling on our DNA, this helped me sort out the generational DNA.
the final result was: CL67, 18574/14086/9401, AR2 51/49/5/89/89/80/5/v/v, 340-390 @ 0.38 @ 2.41, crip/diz.
the physique (specifically, fortitude) was 106% on assembly... the C-type was almost enough, but physique was too high to experiment (94% on assembly), and too low to stick AR2.
Message Edited by lammergeier on 01-26-2005 08:29 AM
ArthurDentOnBria
Wed Jan 26, 2005 12:56 pm
#17
sweet! I'm glad that the result was reproducable and that you were able to improve over the original. I of course was real concerned about CL on the original attempt, so I played it pretty conservatively (i.e. the use of Bull Rancor). But it looks like we even have a little wiggle room still to go 
It's kind of funny that both of ours came out with cripple/dizzy as that is kind of a "happy fluke". That's actually not a bad combo of specials, lol, but it was not at all a consideration when engineering the thing.
Message Edited by ArthurDentOnBria on 01-26-2005 11:59 AM
Meplorium
Wed Jan 26, 2005 2:05 pm
#19
Not going live, there was a bug on TC a while back that allowed those samples to be taken. The bug has since been fixed. They used the DNA since TC was getting a roll back anyways, so it would have been lost in those tests.
lammergeier
Wed Jan 26, 2005 6:10 pm
#21
gave one of these to a MCH, in a narglatch skin (per request).
with +taming mod clothing (aggro skin), they were able to tame it.
they stored it. they tried to call it again.
"invalid pet" error.
kind of makes all this testing moot for usability.
with +taming mod clothing (aggro skin), they were able to tame it.
they stored it. they tried to call it again.
"invalid pet" error.
kind of makes all this testing moot for usability.
Joker9125
Wed Jan 26, 2005 11:29 pm
#23
Wait...........does this mean they have put a hardcap on the stats of callable pets?
Zadokk
Thu Jan 27, 2005 12:05 pm
#24
Joker9125 wrote:
Wait...........does this mean they have put a hardcap on the stats of callable pets?
it probably means that it didnt get passed the in game pet scan, which checks for exploit pets. i suppose the system thinks of it as an exploit pet.
Meplorium
Thu Jan 27, 2005 4:24 pm
#25
Zadokk wrote:
Joker9125 wrote:
Wait...........does this mean they have put a hardcap on the stats of callable pets?
it probably means that it didnt get passed the in game pet scan, which checks for exploit pets. i suppose the system thinks of it as an exploit pet.
Nah, you think? ![]()
So what was choosen? Bring the stats down or up the CL? I would guess a CL of 71 would be the adjustment. How those things usually work.
Zadokk
Fri Jan 28, 2005 3:05 am
#26
Meplorium wrote:
Zadokk wrote:
Joker9125 wrote:
Wait...........does this mean they have put a hardcap on the stats of callable pets?
it probably means that it didnt get passed the in game pet scan, which checks for exploit pets. i suppose the system thinks of it as an exploit pet.
Nah, you think?
think about it. it's a rare case that the devs programming actually worked, so of course i'm going to seem sceptical 