Remove ads

Shepard Quest Mk V, Base of Operations (ME/MCU)

Ultra-Compact Core Design (mini ftl - raises light speed) + Optical computing => mHAHAHAHAHAHA FTL computing.
 
Last edited:
UberJJK said:
So I've gone through and added everything to the existing tech tree. Thing is it's a real mess now. So I'm going to work on coming up with an alternate design that works better.
Click to expand...
Click to shrink...

If it helps, I've got everything written out and roughly categorized at
https://docs.google.com/spreadsheets/d/1NDxsKpeOQgyHIUDmhBbwKNL-wi75q1N9eLf_7QR95bo/pubhtml

If you want edit access so you can change the format or something, just send me a PM. would be awesome if we could drive a decent visualization from the data instead of manually. I roughly based it off the format that D&D and Pathfinder use for presenting long lists of feats, since that's generally the best way I've seen to do this kinda thing.

you also have something wierd going on in the upper left of your tech tree - looks like it wrote out multiple text fields over the compact autocannon entry
 
Last edited:
So, I was wondering...why is the Arc Reactor dependent on the Mk. II Suit? Why don't we have a Generation 1, Generation 2, Generation 3 Arc Reactor branch?
 
Found an Error!

The Quarian immune system doesn't need to be after krepals syndrome, it only requires peak human and quarian assistance

And a suggestion!

Put Extremis off to the side, where you have the alien biology options, and have those go straight down instead.
 
UberJJK said:
So I've gone through and added everything to the existing tech tree. Thing is it's a real mess now. So I'm going to work on coming up with an alternate design that works better.
Click to expand...
Click to shrink...
yEd and 45 minutes of adding the tech names and prereqs - but not costs or status - gave me this:



This program has so many different autosort options.

Edit: Added color-coded status indicators.
Second edit: Desaturated the red for readability and added tech costs.
 
Last edited:
UberJJK said:
That looks fucking awesome!

The program you did that in is called yEd right? I'll make sure to download it tommrow because I've been looking for a program capable of doing that.
Click to expand...
Click to shrink...
Hit refresh for the version with color coding. The only thing you did manually that I don't know how to tell yEd to do is force different techs that cost the same into the same tier. In SBSGA, I represented tech costs by adding specific colored borders to each tech, but that got... distracting.
 
Last edited:
So...I just noticed the superdreadnought there. Since the treaty of farixen only covers dreadnoughts, d'you think we can get around it by building superdreadnoughts? :p
I know the answer is no. I mean if it's larger than a dreadnought, it's technically a larger dreadnought.
 
Last edited:
kylina said:
So...I just noticed the superdreadnought there. Since the treaty of farixen only covers dreadnoughts, d'you think we can get around it by building superdreadnoughts? :p
I know the answer is no. I mean if it's larger than a dreadnought, it's technically a larger dreadnought.
Click to expand...
Click to shrink...
Don't invisitext with questions... >.<
 
Huh. Would have thought Project Lazarus would at least be a 6400 tech, considering it lets you bring the dead back to life and all. Even if it does take two years and enough money to bankrupt a planet.
 
Leingod said:
Huh. Would have thought Project Lazarus would at least be a 6400 tech, considering it lets you bring the dead back to life and all. Even if it does take two years and enough money to bankrupt a planet.
Click to expand...
Click to shrink...
Most likely those 2 years plus money to bankrupt a planet were part of the R&D process for Cerberus.
It says a *lot* that Revy and her company could develop the same procedure over the course of half a year or so even now.
 
I'd like to note that Lazarus is basically an "extreme limit of trauma treatment". Once developed, the process basically eclipses and makes obsolete all other trauma treatments.
 
kylina said:
Sorry, not fully aware of do's and don'ts here. Is there a particular reason not to invisitext in questions?
Click to expand...
Click to shrink...
Sorry if I came off as a lawyer or somesuch. No rules against it, and it isn't even close to a big deal.

Nothing wrong with invisitext in questions, but Invisitext saying that you already know the answer just means the question can waste peoples time trying to answer it. Authors in their story threads are the only ones obsessively highlighted.

kylina said:
Regarding the ships, is there a reason we don't have carriers in the tech tree?
Click to expand...
Click to shrink...
Hopefully, it is part of dreadnaughts, as they're the same size, and size difference seems to have been part of the fluff for why fighter wasn't enough for building frigates.
 
UberJJK said:
Added "Advanced Mass Effect Theory". Should it have "Basic Mass Effect Theory (200)" above it? Because that's not listed on this. Or can we just assume Revy is already familiar with it given how integral it is to ME tech and that she's personally assembled at least a few for her three demonstration Legionary suits?
Click to expand...
Click to shrink...
Very nice work!

It is indeed assumed that Revy knows basic Mass Effect Theory, so no need to make that a separate tech. Regarding benefit, I quite like Yog's (I think) idea of letting her publish her findings and submit it as a PhD thesis, giving her a proper degree.

Also, one small mistake I spotted, Quarian Immune system is not dependent on Kepral's Syndrome, merely on Xenobiology.
 
So, probably a bit redundant given SwiftRosenthal's tree and the one Uber is surely editing...but I was bored.

http://www.gliffy.com/go/publish/image/6067440/L.png
http://www.gliffy.com/go/publish/image/6067440/m.png (...smaller image for people on phones)



This are a bit annoying on the left with the Suit/Reactor shenanigans. I was hoping I could do it without crossing any lines at all, but fucking Tractor Beams and the Mk. III Suit wouldn't play ball.

Alright then, DEW tree moved down a bit to eliminate overlap. Tried to have separate Suit and Reactor trees, and it worked but ruined the flow. So fuck it.

Aaaand, done.
 
Last edited:
Alanek2002 said:
could have looped the Tractor beam line over the basic DEW. :p
Click to expand...
Click to shrink...
Meh, didn't want to be the only one looped over like that. I guess I could just move the whole DEW branch a bit lower...


Also kinda want to do something about the whole suit/reactor slurry there. Maybe make two branches, like:

I----> Re-entry Shroud​
Mk. 1 Suit -> Mk. 1.5 Suit -> Mk. 2 Suit -> Mk. 3 Suit

Mk. 1 Reactor -> Mk. 2 Reactor -> Mk. 3 Reactor
I------------> Industrial Arc Reactor​

I'll see how that looks in a little bit.
 
All these graphs are awesome, but we don't actually need to keep the green ones in the trees

make make your jobs easier if you just consider the yellow and red ones.
 
Lagrange said:
All these graphs are awesome, but we don't actually need to keep the green ones in the trees

make make your jobs easier if you just consider the yellow and red ones.
Click to expand...
Click to shrink...
And thus the sound of a half dozen Facpalms was heard, For Lo; They realized they could put the Acquired knowledge in columns off to the side, and instead focus on mapping what was not yet learned.
 
You must login or register to reply here.
Remove ads
Back
Top