Core 2013/12/21(Sat)10:12 No. 552981 ID: 53ba34
File 138764954838.png - (8.30KB , 805x532 , nano2.png )

You harvest and divide, the both of you then harvest and divide once more, then all four of you harvest and divide a third time.

NEW POWER:
LINK; two or more nanos can link together to form a more complex structure. WARNING, linked nanos cannot harvest or divide until unlinked.

have 1/4 of the nano's link while the other 3/4 harvest and divide.

same, 1/4 link 3/4 harvest/divide. What you should also do is prioritize links that will increase processing power and lead to greater awareness, we need to establish were we are and what exactly we are harvesting.

>You are too simple to understand concepts such as time
You don't need to understand the meaning of concepts to read values saved to memory.

What does your internal epoc time variable read?

>what do?
Devote say... 20% of nanos to linking together while the remaining 80% harvest and divide at whatever rate results in the most efficient replication.

1/2 Core 2013/12/21(Sat)11:26 No. 552988 ID: 53ba34
File 138765400377.png - (8.64KB , 805x532 , nano3.png )

2 Nanos link together, the other six of you harvest and divide again.

2/2 Core 2013/12/21(Sat)11:30 No. 552989 ID: 53ba34
File 138765422482.png - (31.36KB , 1272x810 , nanospindle.png )

The linking causes you to suddenly remember something. You are not sure how you got the memory, but you are sure that two linked nanos can transmute into a micro transmission spindle which allows individual nanos to communicate over longer distances.
WARNING: transmutation is permanent

Replicate until you have 24 nano components. Link 4 and create 2 transmission spindle's, then link 10 into blocks of 2,and two of those into blocks of four. the remaning 10 singles continue to harvest and devide

Final count will be 10 singles, 2 spindels 2 blocks of four and one double.

oh, one of the four block should be a square, the other a line

>>552990
sounds good

>>552990
This, and begin immediate experimentation to determine range of transmission spindles.

Once range is determined, we will know how many spindles we will need to space throughout the swarm to allow communication with the whole. Eventually we'll want a communications net with redundancies in case individual spindles are damaged or destroyed, but a single layer should suffice for now.

1/4 Core 2013/12/21(Sat)14:53 No. 553000 ID: 53ba34
File 138766642286.png - (8.94KB , 805x532 , nano4.png )

You set about harvesting dividing and linking in several configurations. As well as transmute two micro spindles.

the other linkings reveal new memories to you.

2/4 Core 2013/12/21(Sat)15:01 No. 553001 ID: 53ba34
File 138766687049.png - (49.10KB , 1447x895 , nanobeamerlifter.png )

when assembled into a square you remember

Beamer: 3 nanos in a L shape, can fire a small beam that can destroy a single nano, but has a fire rate of only 1 per round and is normally immobile. which brings us to

Lifter: a square of 4 nanos, it generates a localized anti-gravity field directly over it letting it lift and manipulate any micro class constructs and give various benefits to it. most obvious being it grants the beamer the ability to rotate in any direction. it can only lift an object 1 nano above itself without an extra source of power

3/4 Core 2013/12/21(Sat)15:08 No. 553002 ID: 53ba34
File 138766728717.png - (41.21KB , 1609x871 , nanopowersensor.png )

Micro generator: 3 nanos in a line, despite being made of only 3 nanos, this device generates as much energy as 7 nanos. which can boost the ability of some nanos.

micro Sensor tower: 4 nanos in a line can create a sensor tower. it is the most basic way of detecting things other then the relative location of your nanos. you think it's supposed to face a different direction...

4/4 Core 2013/12/21(Sat)15:12 No. 553003 ID: 53ba34
File 138766754063.png - (33.78KB , 1609x871 , spindlerange.png )

Finally you run some tests with your two spindles and figure out exactly how far things can go. The spindles themselves can be roughly 50% further away then a single nano due to their improved send/receive ability.

The fackt that "Round" is a concept you understand leads me to belive the nanites are some sort of combat Toy, this is good, if we have escaped or are malfunctioning we will not be viewed as a theat to begin with.

Ok, first things first, build ourselves up until the construction of 3 Generators, 2 towers, 1 meaner and 1 lifter leaves us with 20 single nanites. then experiment with the towers and try to ascertain our local enviroment, if possible try to build up to 40 spare nanites, then use 20 to create a large block, see what that dose.

If the giant cube dose nothing then turn the beamer on it to break it down into usable marital once more.

Right.

Swarm: continue to harvest and replicate.

Construction orders:

1x Beamer
1x Lifter for the beamer
1x Generator
1x Sensor tower

Maintain numbers and stagger construction such that at any given point, no more than 1/4 of total nanos are built into special structures, and the remainder are on collect and multiply duty.

When the sensor comes online, use the lifter to rotate it and scan a full 360 degrees.

Oh, from the look of it sensor towers need to be hooked up to generators some how, if the connections arent permanent then try different angles.

Core 2013/12/21(Sat)16:21 No. 553009 ID: 53ba34
File 138767167094.png - (9.64KB , 805x532 , nanoerror.png )

The nanos harvest and replicate once mo-

REPLICATION ERROR

it appears we have hit some kind of limit, when attempting to divide the 31st nano it went inert almost immediately after it was created. seems that right now we only have 30 nanos to work with, including those in transmuted objects, so the micro spindles count as two each despite being one object.

please advise.

Join all non-specialized nanos (non-permanently) in one block to unlock as many memories as possible.

Generator and Sensor. we need to survey the surroundings to make better decisions. keep the others as free nanos in case we need them for something. The swarm can keep harvesting to accumulate resources.

>>553009
Could we link up more of the harvest nanos (that can't do anything right now), and see if we can remember anything relevant to the swarm size cap?

>>553011
This seems like a good idea.

1/3 Core 2013/12/21(Sat)18:28 No. 553029 ID: 53ba34
File 138767930768.png - (44.73KB , 1447x895 , biggest shape.png )

the nanos swarm into the largest cuboid they can make. luckily it does indeed unlock new memories of transmutations.

2/3 Core 2013/12/21(Sat)18:33 No. 553031 ID: 53ba34
File 138767959088.png - (30.64KB , 1609x871 , central.png )

micro subprocessor: a 2 x 2 x 2 cube, frees up nano control ability by directing control for 10 micro class objects, such as spindles. it counts as a single nano for purpose of total nanos in swarm.

3/3 Core 2013/12/21(Sat)18:35 No. 553032 ID: 53ba34
File 138767975846.png - (33.82KB , 1609x871 , nanoshield.png )

micro shield: Projects a shield over an area. alone the shield is just big enough to cover itself. at full power it can withstand four beamers indefinitely.

The processor only counts as one nano? Make one, and then harvest and replicate until we hit the nano-cap again.

Also, if we haven't made a senor tower yet, make one, and begin scanning the area.

>>553031
Excellent. Create one immediately. That will allow us to create 17 more(8 used for a structure that count as 1, so 7 are freed up, and 10 max cap increase). Also form up some spare nanos into a line of 8 length for additional line research, and make a Sensor tower and Lifter combo so we can look around in various directions.

Core 2013/12/21(Sat)20:56 No. 553044 ID: 53ba34
File 138768819651.png - (17.50KB , 1161x742 , nano5.png )

apparently i was too subtle, or something. it's a TOWER, it was sideways. got the memory from four blocks in a row, but it was facing the wrong direction.

The sup-processor and the sensor tower are built. the tower begins scanning the area.

A lifter is also built and is awaiting an input

A chain of 8 blocks in a row reveals nothing new.

sensor data has compiled. two different types of data have been detected. green indicates some kind of energy source. blue marks faint data transmissions.

>too subtle, tower goes up
...aren't we operating in three dimensions? Which way is up? Are we floating around, or are we operating on an actual plane or surface?

>two things scanned
Send scout nanos towards each?

>>553044
Blue we can assume is an enemy, let's avoid them for now. Make a Beamer for the Lifter so we have some basic defense.

Take those 8 research nanos and make an L block from them instead. Also make two subprocessors. Continue to produce new nanos. Once we have like 50 free nanos try making a 3x3x3 cube.

I suggest a different strategy for harvest/growth: Instead of alternating harvesting and growing, have half of our idle nanos harvesting at any moment and the other half growing. That should save a little time from not having to switch tasks, and we'll actually grow at a faster rate because, if for instance we have 100 nanos, it'll be 50 then 75 instead of just 100 from two cycles.

>>553044
Can we have some kind of visual representation, like a grid or circles or something, so we know the range of the spindles or the antenna?

Hmm, so, do you need to ingest a certain amount of matter before you can divide, or do you just get smaller and smaller if you keep dividing? Is there some kind of drawback to that?

So, does the CPU block increase the max cap by 10, is that what it does? If so, basically keep harvesting and dividing; the half and half scheme seems good, depending on whether or not an individual bot needs to cycle harvesting and dividing. Allocate a enough new bots to CPUs to keep raising the cap, but also start producing beamers and lifters and other sundry units.

I'm waiting for the other shoe to drop - unopposed, we could get arbitrarily big really fast. I'm nervous that we may soon be called upon to defend ourselves.

Break up the 8 nanos we have researching.
Make a second lifter.
Make a pair of beamers.
Make a third spindle.

Place the beamers on the lifters, and position them facing the blue area as defense.

Organize two groups of four nanos and a spindle, then send a group to scout each of the blue and green areas.

We need to figure out what is going on here.

>>553058
I'm a little nervous that sending out scouting parties could draw unwanted attention to us, before we're ready. I would prefer that we build up our defenses a bit more before poking our head out.

1/4 Core 2013/12/22(Sun)08:18 No. 553074 ID: 53ba34
File 138772910937.png - (23.57KB , 1161x835 , nano6.png )

>>553045
we are on a plane, if we were moving in 3d space the lifter would be useless
>>553054
i thought i was clear in the description of it "directing control for 10 micro class objects, such as spindles." it controls transmuted objects, which are made of multiple nanos, freeing up control so instead of having 26 single nanos and 2 spindles you have 29 nanos and 1 sub processor


the 8 line is changed into an 8 L. nothing happens. you build and deploy two lifter/beamer combos on the.... let's call it east, side.

you re-arrange your spindles so your nanos can examine the energy source, one nano approa-
NANO DESTROYED
oh, it appears the energy source is so high energy that it overloads a nano's simple systems.
>>553050
placed a range ring around one of the spindles for this update, would get very cluttered very fast if we have several spindles and they all have their rings shown all the time

2/4 Core 2013/12/22(Sun)08:20 No. 553075 ID: 53ba34
File 138772921588.png - (18.52KB , 1161x835 , nano7.png )

Despite the set back you still have more ideas to try. You regroup and separate the large L block and create a 3x3x3 cube.

NEW MEMORIES

3/4 Core 2013/12/22(Sun)08:20 No. 553076 ID: 53ba34
File 138772925342.png - (38.50KB , 1609x871 , coreprocessor.png )

Small Core Processor: central command and control object. uses one nano, interfaces with two sub processors and two memory matrix. unlocks new objects. improves sub processors by having them prioritize the largest objects. only one small core processor can be built

Small class objects: an object with a nano count greater than 8 is considered small class, compared to the micro class of objects below that threshold. micro sub processors do NOT free up control of small objects.

4/4 Core 2013/12/22(Sun)08:21 No. 553077 ID: 53ba34
File 138772927698.png - (44.30KB , 1609x871 , memorymatrix.png )

Small Memory Matrix: frees up processing power from the nanos themselves by handling various sub tasks that the nanos normally do. increses max nanos by 30. core processor required to transmute.

>if we were moving in 3d space the lifter would be useless
Not necessarily. The ability to control the relative orientation of structures that would otherwise orient and/or drift randomly would still be useful (especially with directional weapons or sensors). But point taken.

>Energy source fried approaching nano
Then it's off limit until we develop shielding and/or hardened units.

>New structures
>ups nano limit
Build new things, harvest and multiply to new unit cap.

>>553081
this

>>553081
We have shielding, but the shielded structure only protects itself so it's kindof useless atm.

>>553077
Oh, so the micro subprocessor only increases the cap by freeing up nanos used to make structures.

Wait, the core processor requires a memory matrix, but the memory matrix requires a core processor? How are we supposed to build either of them? Or does the core processor just connect to any existing memory matrixes and sub processors to improve its own function?

I'd like to build both new structures, and then two more sub processors alongside two beam/lifter combos and four micro generators. If we have a bunch of free nanos, make a line of 20 of them to see if it unlocks anything. Lacking results from that, a 2x2x5 structure might unlock the Small generator...

>>553085
Oh, maybe the shield can cover more than itself if it's boosted by a micro generator? I'm wondering what specific effects a generator has when boosting structures.

>>553085
I believe that the processor needs a memory to work, but you can build it alright, and the memory needs the processor to be built first...

I suggest that we replicate a couple of times mores, i think that we still have the space to do it.

Core 2013/12/22(Sun)11:15 No. 553104 ID: 53ba34
File 138773971739.png - (24.58KB , 1161x835 , nano8.png )

You build a Core Processor and Two Memory Matrix. You then begin a massive cycle of multiplication. You are about to start assembling into new larger shapes when the sensor detects moving sources of data transmission.

>>553104
To arms! Make 5 more lifter/beamer combos, and send out an advance scout.

Can we run the incoming signal through our memory and/or processor for analysis? Can we boost the efficiency of our scan of the data by using the generator?

nanos are expendable, if they get destroyed they can be harvested for supplies and cloned again... i suggest that we use like... half of our nanos making walls. Just a bunch of nanos linked together. With the lifters, we should be able to fire from over the wall!

TL;DR Operation human shield from the southpark movie...

1/3 Core 2013/12/22(Sun)14:24 No. 553156 ID: 53ba34
File 138775107424.png - (21.61KB , 1161x835 , nano9.png )

while the wall is growing the signals are getting closer. you aren't too sure how well a wall can- oh, what's this?

MEMORY

2/3 Core 2013/12/22(Sun)14:27 No. 553157 ID: 53ba34
File 138775127031.png - (50.21KB , 1609x871 , wall.png )

it seems a 2x4 can transmute into a solid wall. it is dumb and takes no nano cap. it also seems to be harder for nanos to break down. be careful where you place them, can hinder your own nanos as well.

3/3 Core 2013/12/22(Sun)14:31 No. 553159 ID: 53ba34
File 138775148833.png - (26.89KB , 1609x871 , gate.png )

A 2x5 can turn into a small gate. Despite being small it fits seamlessly with micro walls. It counts as an object due to the moving parts, but is simple enough that it can be managed by a micro subprocessor. due to the requirement of moving parts it is a weak point in wall defenses.

Make a second subprocessor, attach both to the core.

Make two wall segments facing the approaching signals and a gate between them, then put our beam towers at the gate to defend it. Do not open fire immediately upon the signals- wait until we know they are hostile.

2 more lifter/beamer combos would not hurt... but get ready to move them if we need to relocate fast... also keep a good number of nanos with a spindle to the southeast, for any eventuality.

>>553167
Do this, but the moment the wall is up send a small scout group of 4 nanos & spindal out to investigate the transmission source.

okay, people seem to think that if you have a spindle then you can send it and some nanos as far as you want. no, the cluster must be in communication range at all times. if something cuts two groups off the smaller group goes inert. spindles extend your range, not make it infinite.

>>553186
Well then we just need more spindles, right? Send them out in a chain? Or does every spindle have to be in direct communication with the core?

>>553186
Yes, but sending a spindle with a group doubles the range it can travel out to.

Core 2013/12/23(Mon)05:27 No. 553238 ID: 53ba34
File 138780522766.png - (26.17KB , 1161x835 , nano10.png )

You prepare. Lifter/Beamers are transmuted and placed, Walls and Gate placed, Spindles and Nanos waiting for the order to move out.
>>553192
chain

>>553238
That's weird, shouldn't we be able to see them by now? Get some eyes out there. Send a spindle chain if necessary, we have nanos to burn. Speaking of which, let's keep increasing the cap by making a couple more memory matrixes, and extend the wall in both directions. Also I'd like to send a spindle and shield generator out to the power source so we can get a look at it instead of just finding out it destroys things.

Also, we have a fully assembled core processor but nothing's unlocked?

>>553239
We can worry about research later.
Let's get those scouts out to the network signal ASAP.

Send a few scouts east, and build ourselves a generator if we haven't yet (we can use that to enhance our lasers, and possibly other things like the scanner or our thinking parts).

okay, maybe i should of asked specifically, but what should be done with the incoming contacts? they are going to hit the wall if they don't change course.

>>553259
That is acceptable.

>>553259
Send a scout to see if they're hostile, and/or intelligent.

>>553259
Send a single nano out to meet them.
That'll give us more info and allow us to try to communicate, without risking anything valuable.

1/2 Core 2013/12/23(Mon)16:19 No. 553318 ID: 53ba34
File 138784438667.png - (25.85KB , 1161x835 , nano11.png )

>>553239
meant small objects unlocked by the core. without it you would not have been able to make a gate, which is 10 blocks total, only the walls. so if you made the shape before the core was built, you would have had it revealed then.

scout group and intercept nano sent. contacting in...
CLICK-CLICK
huh?

Core 2013/12/23(Mon)16:23 No. 553319 ID: 53ba34
File 138784460048.png - (29.12KB , 1161x835 , nanoboom.png )

BOOOOOOOOOOOM

well thats hostile, seems the small contacts are moving bombs. the contact nano was vaporized, the wall managed to deflect most of the blast but was damaged. what's odd is they were only the size of one of your nanos, and you have no data on one nano bombs.

how do you proceed?

>>553319
Ah, I see. The circles are objects, not just markers. From now on, have our defending Beamers shoot any incoming bombs.

Have our scouts go check out that bigger blue oval. Meanwhile, make 4 more beamer/lifter combos and have them move out as a second group behind the scouts. Time to retaliate with a quick strike force. Also, reinforce our defensive wall with two shields and two generators.

Lastly, let's continue research. Make a 1x20 line, a 2x2x5 rectangular prism, and a 5x5 square.

>>553369
lifters are immobile while lifting something, to negate gravity on one thing amps up the gravity on itself. even while idle it still cannot go anywhere very fast. Currently all objects other then spindles are much slower or worse then single nanos. and spindles are only slightly slower.

Better idea- Beamers, fire on the big object.
the '1 nano bomb' was probably from that blue wave object, I'm guessing it's a small class object that's hostile to us for some reason.

>>553375
Aw. Well let's just send a swarm of nanos and a spindle over and transmute into an army at their doorstep.

1/3 Core 2013/12/24(Tue)15:33 No. 553524 ID: 53ba34
File 138792799301.png - (23.06KB , 1161x835 , nano12.png )

designing the small units is harder, why i took so long

A nano touches the larger reading... nothing happens. One spindle passes the edge of the map, and is transferring to map 0_1.
The blasts clear. seems the wall managed to mostly withstand the blast.

The free nanos at the base Link in a variety of shapes.
the 1x20 line does nothing.

MEMORY

2/3 Core 2013/12/24(Tue)15:38 No. 553525 ID: 53ba34
File 138792828952.png - (68.52KB , 1609x1362 , smallheavytankl.png )

Small Heavy Transport Tank: low and wide. this tank can slowly carry just about anything that can fit on it's back. which is an area of about 5x4 nanos wide. Also has built in clamps to allow it to secure anything unstable.

3/3 Core 2013/12/24(Tue)15:45 No. 553526 ID: 53ba34
File 138792875808.png - (86.08KB , 1609x1601 , small spindle power.png )

2x2x4 Creates the Small Spindle: and upgrade of the micro spindle, this one is able to cover a greater area as well as generate a jamming field turning anything other then your units dumb. jamming field is half size of transmission area and both abilities cannot be active at the same time.

2x2x5 can transmute into Small Generator: produces 7 times as much energy as a micro generator. if given a fuel it is able to generate 3 times as much as that. WARNING; do not plug directly in to micro units.

reminder: micro sub processors do not mitigate cost of small units.

>>553525
Hmm. Make one tank, put a Lifter+Beamer combo on it and a small generator. Send that out behind our strike force. It should zap the enemy signatures loitering near our base before heading to the second map.

Further research: a 4x4x4 cube, if we can manage it. Could we get some numbers in each update giving us the total number of loose nanos, max nanos, and nanos used in structures by size alongside the processor compensation?

Then let's see what's on the next map.

Let's see if building/linking various sized pyramids get us any memories.

And why not do the tetrominoes? And while we're at it why not some polycubes? http://recmath.org/PolyPages/PolyPages/index.htm?Polycubes.html Seems to have quite a few we can try.

>>553549
you can suggest specific shapes. like hollow tube of X dimensions and such. but i am not going to go that whole site to see if one of the shapes is valid

>>553526
Make the skeleton of a 4x4x4 cube. This will take 32 nanos. Then add 8 to make it a 4x4x4 cube skeleton containing a 2x2x2 cube. Then add 16 more nanos to make a hollow cube. Finally add the remaining 8 to make a solid cube. This is the most efficient means of testing the simplest combinations for a 4x4x4 space.

I thought that so long as the shape we form is large enough to contain memory-designs then we'd discover it?

>>553565
yes, but obviously you can make some weird shapes that are otherwise too big to just make a cube. such as the 2x2x5, you do not have enough nanos to make a 5x5x5 cube. so non-cube shapes can still help. not sure what Seven thinks he is gonna get from making part of a cube, and then the whole cube.

>>553566
Alright cool that's what I was doing so far.

Why dont make a L shape out of 2x2x2 boxs? It should make a small beamer or something along those lines?

sorry for the wait, is pretty hard to design small objects that mostly conform the right shape.

guuuuys, we haven't figured out how to work things like the micro generators work with beamers or even gotten the shield generators working by plugging the micro generators into them!
If we're gonna experiment, lets work more with those things instead of small-class crap we don't really have the nanos to create!

Well if we dont have the nanos to go making small stuff why dont we make small/micro combos like
1x trans tank
With 1x lifter beamer combo
And 1x micro spindle
That takes 27 nanos to make and gives us some mobile fire power and a slow but strong scout

And lets see what sec 0-1 is like

seriously guys, i give you a unit with a large transport capacity and you only stick ONE unit on it? it is 4x5 wide, lifters are only 2x2, do the math.

>>553882
So then we just load it up with 4 pairs of lifter-beamers!!

>>553891
Or two and a small spindle and a micro sensor

1/9 Core 2013/12/30(Mon)21:47 No. 554415 ID: 53ba34
File 138846886546.png - (24.06KB , 1161x835 , nano13.png )

First the beamers take out the bombs once they get in range.
Shapes are reconstituted into a 4x4x4 cube, three nanos are sent after the spindle into the next sector, and the lifter beamers are migrated together awaiting a heavy transport to move them.

MEMORIES

2/9 Core 2013/12/30(Mon)21:50 No. 554416 ID: 53ba34
File 138846901712.png - (28.09KB , 1447x895 , spider.png )

Light transport tank: is made via a 4x4 + shape with an extra layer of 4 in the center. the light tank has an obviously smaller transportation capacity but it can move much faster then the heavy tank, in fact, it can move faster then even single nanos. it's armor is much lighter and the legs are vulnerable.

3/9 Core 2013/12/30(Mon)21:53 No. 554417 ID: 53ba34
File 138846918671.png - (30.41KB , 1447x896 , smalltower.png )

small sensory correlation system: does not operate on it's own. instead it is linked with 4 micro sensor towers that link up with it and create a sensor net. this improves both range and fidelity of sensor systems due to the slightly different inputs being processed in parallel.

4/9 Core 2013/12/30(Mon)21:54 No. 554418 ID: 53ba34
File 138846927843.png - (42.17KB , 1447x896 , smal lifter.png )

small lifter: is exactly what it sounds like, a larger sized lifter. can also multiple micro units.

5/9 Core 2013/12/30(Mon)21:56 No. 554419 ID: 53ba34
File 138846936141.png - (36.30KB , 1447x896 , eyeinthesky.png )

The Eye: provides additional data within it's line of sight. must be lifted to have any real range.

6/9 Core 2013/12/30(Mon)21:58 No. 554420 ID: 53ba34
File 138846950122.png - (37.97KB , 1447x896 , small SPU.png )

Small Sub-processor: provides improved command and control abilities to small class objects. two of them also allow one additional memory matrix by streamlining data flow.

7/9 Core 2013/12/30(Mon)22:01 No. 554421 ID: 53ba34
File 138846969028.png - (47.95KB , 1447x896 , transfer lifter.png )

NEW OBJECT TYPE: DOUBLE TRANSMUTATION

Transfer lifter. requires attached generator to function properly. not only lifts but provides extra power to lifted object(s). so objects require this to function properly. takes two micro object capacity

8/9 Core 2013/12/30(Mon)22:04 No. 554422 ID: 53ba34
File 138846989052.png - (45.28KB , 1447x896 , slicer.png )

Slicer: chargeable sustained coherent energy beam. made from 4 micro beamers. MUST be placed on a transfer lifter in order to have enough power. central energy sphere is charged up then fires a continuous beam that can rotate while firing for as long as the charge lasts.

9/9 Core 2013/12/30(Mon)22:06 No. 554423 ID: 53ba34
File 138846998419.png - (24.11KB , 1161x835 , 0-1-1.png )

the spindle is in the new map. it only obtains partial data due to sensor tower range. also cannot properly identify shape of objects emitting transmissions.

Cool, cool. Oh, hey, how many nanos do we need in order to build those things?

>>554423
Ahhhh shit lets upgrade both the lefters and beamers too there small size and then mount them on a hev trans

>>554431
light tank: 16
small tower: 22
small lifter and eye: 32
small subprocessor: 36

the double transmutations require only component parts, no additional nanos unless noted.

>>554462
Then instead of micro left-beam armed hev tank we use a small version of both along with 4 more beamers to re arm the micro lefts we have