What would you do if the source was released, and you were an epic C++ god?

well i doesnt really matter i suck with sarcasm in real life due to my aspergers.

well, we're pretty sure it's aspergers. I was evaluated in san fransisco and they said that I was on the autistic spectrum, and htat it was most likely aspergers.

http://en.wikipedia.org/wiki/Irony_mark#Irony_mark

/Derailment

lol that is funny. Never herd of that one.

It's Chris!

I would add ragdolls. LOTS OF RAGDOLLS.

I'd consolidate Trim, Rudder, and Chip into one chip, and add "bomb" chips- these chips would have similar attributes to arm chips, save that when they are triggered (either by damage, or by a trigger VAL reaching "option") they break (both off the model, and the chip itself shattering) and release an explosion. The explosion would do (option) damage and exert (option) force on chips within a radius proportional to (option).

Then I would cackle gleefully and make VTOL bombers.

no. just no.
i've hacked myself a 12.8m automatic gun. its overpowered. if that happened to bombs it would be a game-breaker.

anyway, i do have a 400+ chip "bomb", which uses 2M arms, and can disconnect players online because of its lag factor

Yeah, as I wrote that I began wondering if that's part of the reason the game doesn't have explosives. They'd be way too easy to spam and abuse...

Hmm... What do you mean "hacked" for your 12.8mil autocannon, you figured out a clever way for extreme rates of fire or you actually altered the game code? If it's the former, I'm intrigued and wish to steal your ideas learn this technique in order to fight the Japanese bulletspam cannon menace...

i used Cheat Engine(aka second method) for that. hint: the energy value is a float. it needs to be set to the energy value of the arm or a greater value, then frozen. i'll leave the adress scanning up for you though.

as for the bulletspam cannons, they just make a "chaingun", which moves arm chips so that they dont intersect when firing, fires, and switches to the next arm, allowing for higher firerates.

bulletspam cannons wont be enough though, especially against satelite vehicles.

I've seen satellite vehicles shot down by spamcannons though; the model shooting them down was a microtank with a spamcannon turret that had a near-vertical maximum traverse.

And while I'd guessed the spamcannons operated something like that, for the life of me I don't know how to code for something like that. Any tips? If I could master the art of the spamcannon, I'd be unstopppable...

Lua _G[] function. it basically reveals the variable within its argument(a string).

you can concatenate strings and numbers by using the ".." operator. this allows for less pain when wiring controls to all of the arms.

for instance, the code below sets variables POWER1, POWER2, POWER3, POWER4, POWER5, POWER6, POWER7, POWER8, POWER9, POWER10, POWER11, POWER12, POWER13, POWER14, POWER15, POWER16, POWER17, POWER18, POWER19, POWER20, POWER21, POWER22, POWER23, POWER24, POWER25, POWER26, POWER27, POWER28, POWER29, POWER30, POWER31, POWER32, POWER33, POWER34, POWER35, POWER36, POWER37, POWER38, POWER39, POWER40, POWER41, POWER42, POWER43, POWER44, POWER45, POWER46, POWER47, POWER48, POWER49, POWER50, POWER51, POWER52, POWER53, POWER54, POWER55, POWER56, POWER57, POWER58, POWER59, POWER60, POWER61, POWER62, POWER63, POWER64, POWER65, POWER66, POWER67, POWER68, POWER69, POWER70, POWER71, POWER72, POWER73, POWER74, POWER75, POWER76, POWER77, POWER78, POWER79, POWER80, POWER81, POWER82, POWER83, POWER84, POWER85, POWER86, POWER87, POWER88, POWER89, POWER90, POWER91, POWER92, POWER93, POWER94, POWER95, POWER96, POWER97, POWER98, POWER99, POWER100, POWER101, POWER102, POWER103, POWER104, POWER105, POWER106, POWER107, POWER108, POWER109, POWER110, POWER111, POWER112, POWER113, POWER114, POWER115, POWER116, POWER117, POWER118, POWER119, POWER120, POWER121, POWER122, POWER123, POWER124, POWER125, POWER126, POWER127, POWER128, POWER129, POWER130, POWER131, POWER132, POWER133, POWER134, POWER135, POWER136, POWER137, POWER138, POWER139, POWER140, POWER141, POWER142, POWER143, POWER144, POWER145, POWER146, POWER147, POWER148, POWER149, POWER150, POWER151, POWER152, POWER153, POWER154, POWER155, POWER156, POWER157, POWER158, POWER159, POWER160, POWER161, POWER162, POWER163, POWER164, POWER165, POWER166, POWER167, POWER168, POWER169, POWER170, POWER171, POWER172, POWER173, POWER174, POWER175, POWER176, POWER177, POWER178, POWER179, POWER180, POWER181, POWER182, POWER183, POWER184, POWER185, POWER186, POWER187, POWER188, POWER189, POWER190, POWER191, POWER192, POWER193, POWER194, POWER195, POWER196, POWER197, POWER198, POWER199, POWER200, POWER201, POWER202, POWER203, POWER204, POWER205, POWER206, POWER207, POWER208, POWER209, POWER210, POWER211, POWER212, POWER213, POWER214, POWER215, POWER216, POWER217, POWER218, POWER219, POWER220, POWER221, POWER222, POWER223, POWER224, POWER225, POWER226, POWER227, POWER228, POWER229, POWER230, POWER231, POWER232, POWER233, POWER234, POWER235, POWER236, POWER237, POWER238, POWER239, POWER240, POWER241, POWER242, POWER243, POWER244, POWER245, POWER246, POWER247, POWER248, POWER249, POWER250, POWER251, POWER252, POWER253, POWER254, POWER255, POWER256, POWER257, POWER258, POWER259, POWER260, POWER261, POWER262, POWER263, POWER264, POWER265, POWER266, POWER267, POWER268, POWER269, POWER270, POWER271, POWER272, POWER273, POWER274, POWER275, POWER276, POWER277, POWER278, POWER279, POWER280, POWER281, POWER282, POWER283, POWER284, POWER285, POWER286, POWER287, POWER288, POWER289, POWER290, POWER291, POWER292, POWER293, POWER294, POWER295, POWER296, POWER297, POWER298, POWER299, POWER300, POWER301, POWER302, POWER303, POWER304, POWER305, POWER306, POWER307, POWER308, POWER309, POWER310, POWER311, POWER312, POWER313, POWER314, POWER315, POWER316, POWER317, POWER318, POWER319, POWER320, POWER321, POWER322, POWER323, POWER324, POWER325, POWER326, POWER327, POWER328, POWER329, POWER330, POWER331, POWER332, POWER333, POWER334, POWER335, POWER336, POWER337, POWER338, POWER339, POWER340, POWER341, POWER342, POWER343, POWER344, POWER345, POWER346, POWER347, POWER348, POWER349, POWER350, POWER351, POWER352, POWER353, POWER354, POWER355, POWER356, POWER357, POWER358, POWER359, POWER360, POWER361, POWER362, POWER363, POWER364, POWER365, POWER366, POWER367, POWER368, POWER369, POWER370, POWER371, POWER372, POWER373, POWER374, POWER375, POWER376, POWER377, POWER378, POWER379, POWER380, POWER381, POWER382, POWER383, POWER384, POWER385, POWER386, POWER387, POWER388, POWER389, POWER390, POWER391, POWER392, POWER393, POWER394, POWER395, POWER396, POWER397, POWER398, POWER399, POWER400, POWER401, POWER402, POWER403, POWER404, POWER405, POWER406, POWER407, POWER408, POWER409, POWER410, POWER411, POWER412, POWER413, POWER414, POWER415, POWER416, POWER417, POWER418, POWER419, POWER420, POWER421, POWER422, POWER423, POWER424, POWER425, POWER426, POWER427, POWER428, POWER429, POWER430, POWER431, POWER432, POWER433, POWER434, POWER435, POWER436, POWER437, POWER438, POWER439, POWER440, POWER441, POWER442, POWER443, POWER444, POWER445, POWER446, POWER447, POWER448, POWER449, POWER450, POWER451, POWER452, POWER453, POWER454, POWER455, POWER456, POWER457, POWER458, POWER459, POWER460, POWER461, POWER462, POWER463, POWER464, POWER465, POWER466, POWER467, POWER468, POWER469, POWER470, POWER471, POWER472, POWER473, POWER474, POWER475, POWER476, POWER477, POWER478, POWER479, POWER480, POWER481, POWER482, POWER483, POWER484, POWER485, POWER486, POWER487, POWER488, POWER489, POWER490, POWER491, POWER492, POWER493, POWER494, POWER495, POWER496, POWER497, POWER498, POWER499, and POWER500
to 100000 with minimal effort. Inviso-text test: Yay for filling up the post space with useless text!

Code:

for x=1,500 do
_G["POWER"..x] = 100000
end

PS:an actual lua function was used to create that wall of text

So.... what you just wrote allows for queuing up a whole lot of arms to one firing key, or is it for overcoming the _E() recharge time? But what about the process of making the chips flip in and out of firing position without intersecting for the Japanese spamcannons?


You'll have to forgive me, I'm a quick study and I follow the logic of programming languages well, but I still don't really know much about Lua.

it just sets all variables to 100000, for no effect at all. what's interesting about _G[] is that it can work along with if statements and other structures.

Code:

function guncontrol(gun, numguns, prefix, suffix, step)
   --changes guns' angles by moving them at step degrees per frame
for n=1,numguns do
     if n == gun  then
   _G[prefix..n..suffix] = _G["G1_"..n..suffix] - step
   else
   _G[prefix..n..suffix] = _G[prefix..n..suffix] + step
     end
end
end

i think the variables' limits should do it.

the function just controls the guns' angles, without controlling its firing. another for operator which checks for the arm angles(and optionally the _E() of the arms, as long as you name each one) to fire the gun and get the loaded gun variable to change its value.