Spring - User contributions [en]

GamesDownloads

2022-01-09T18:58:38Z

Zwzsg:

{{#css:
table.glossy {
width: 200px;
margin: 9px; padding:3px;
border: 1px solid rgba(0,0,0,0.5);
border-radius: 10px 10px 10px 10px;
box-shadow: 0 2px 6px rgba(0,0,0,0.5), inset 0 1px rgba(255,255,255,0.3), inset 0 10px rgba(255,255,255,0.2), inset 0 10px 20px rgba(255,255,255,0.25), inset 0 -15px 30px rgba(0,0,0,0.3);
text-align: center;
}

/*#installers img {
border: 1px solid rgba(0,0,0,0.5);
box-shadow: 0px -1px 3px rgba(0,0,0,0.8), 0px 1px 3px rgba(255,255,255,0.5);
}*/

/*table.glossy:hover {
background: rgba(160,160,220,0.4);
}*/
}}
[[Download]] < {{FULLPAGENAME}}

== Spring Lobby ==

For the Spring engine and a variety of games to play on it! Online battlerooms and singleplayer. Also, there is a lobby to chat in.

<div style="padding-left:7px">
{{Template:GamesDownload|name=SpringLobby|image=Springlobby_64.png|url=https://springlobby.springrts.com/}}
The easiest way to play: download SpringLobby, join the Spring server and enter an online battleroom.

MacOS players: see https://springrts.com/phpbb/viewtopic.php?f=65&t=32970 for the SpringLobby download link. Engine must be downloaded seperately (103.0 is current), in the same forum.


</div>

== Games available via [https://www.steampowered.com Valve Steam] for Windows ==
<div id="steam" style="padding-left:7px">
{{Template:GamesDownload|name=Zero-K|image=eclipse.jpg|url=https://store.steampowered.com/app/334920/ZeroK/}}
{{Template:GamesDownload|name=Evolution RTS|image=Evoimg.jpg|url=https://store.steampowered.com/app/291150/Evolution_RTS/}}
</div>

== Games available via [https://www.itch.io itch.io] for Linux ==

<div id="itch" style="padding-left:7px">
{{Template:GamesDownload|name=Zero-K|image=eclipse.jpg|url=https://zerok.itch.io/zero-k}}
{{Template:GamesDownload|name=Evolution RTS|image=Evoimg.jpg|url=https://forboding-angel.itch.io/evolution-rts}}
</div>

== Individual game installers ==
A handful of Spring games also provide their own installers (and/or other infrastructure). These usually contain everything you need to play that game, but they might not allow you to play other games too.
<div id="installers" style="padding-left:7px">

{{Template:GamesDownload|name=Zero-K|image=eclipse.jpg|url=https://zero-k.info/Wiki/Download}}
<span class="warning">(!)</span> This lobby is limited to playing Zero-K. (Windows & Linux)

{{Template:GamesDownload|name=NOTA|image=notAgame02.jpg|url=http://nota.machys.net/downloads}}
<span class="warning">(!)</span> This lobby is limited to playing NOTA. (Windows & Linux & Mac OS X)

{{Template:GamesDownload|name=Spring 1944|image=S44_tigers.jpg|notAs44lobby|url=https://trello.com/c/XllGyMqI/}}
<span class="warning">(!)</span> This lobby is limited to playing Spring 1944, NOTA and Kernel Panic. (Windows & Linux)

{{Template:GamesDownload|name=Kernel Panic|image=Kernel_Panic_3.4.jpg|url=https://www.moddb.com/games/kernel-panic}} <span class="warning">(!)</span> This lobby is limited to playing Kernel Panic. (Windows)
</div>

For more Spring games, check out the [[Games]] page. Please note that some of them will require you to have the engine installed in order to work, as well as some maps, as they don't come with their own installer.

[[Category:Spring]]

Kernel Panic

2021-07-13T23:20:58Z

Zwzsg: Add Mod DB link (to installer)

<center>[http://timblokdijk.nl/spring/Kernel%20Panic/logo/kernel0_hd.png https://springrts.com/mediawiki/images/f/fc/Kernel_Panic_Alpha_Title_Half.png]</center>

==Overview:==

''For the latest news and/or assistance, try the [http://springrts.com/phpbb/viewforum.php?f=43'''KP forum'''] or go to #kp when you log onto the lobby.''

'''Kernel Panic''' is a game about computers. Systems, Hackers and Networks wage war in a matrix of DOOM! The only constraints are time and space; unlike other real time strategy games, no resource economy exists in KP.

All units are free in this game, every factory built will be spamming units at all times. You can build more factories, but only on pre-defined areas (geothermal vents). All that remains is pure strategy and tactics.

KP makes for a frantically fast-paced, action-oriented game, with a very unique graphical style.

----

==Download links:==

Current Version of Kernel Panic is 4.9

* <u>Newcomers:</u>
** If you run '''Windows''' (2000,XP,Vista,7,8,10):
*** Here you can get a complete installer:
**** http://zwzsg.ddns.net/kp/installers/Kernel_Panic_4.9_Including_Spring_105.0_Installer39.exe
**** Mod DB mirror: https://www.moddb.com/games/kernel-panic/downloads/kernel-panic-49-installer-39
*** Use it to install both Spring and Kernel Panic in one go.
*** Then use the shortcuts created in your Start Menu or Desktop.
** If you run '''Linux''':
*** Get a Linux static build of the Spring engine from https://springrts.com/wiki/Download
*** Get and unzip that file: http://zwzsg.ddns.net/kp/zips/Kernel_Panic_4.9.zip
*** Unzip both in the same folder, so that Kernel_Panic_4.9_Launcher_Linux is next to spring executable
*** Run Kernel_Panic_4.9_Launcher_Linux
*** Alternatively, running spring directly would bring a greenish menu once ingame
*** For multiplayer or advanced options, run SpringLobby

* <u>Experienced Users:</u>
** If you have already the Spring engine (or prefer to install it yourself): Here you can get a zip with the mod file, the maps, and a tiny executable for single player frontend. Unzip into your Spring root folder: http://zwzsg.ddns.net/kp/zips/Kernel_Panic_4.9.zip
** If you are certain you have all the maps and just need a quick link to the mod file itself: http://zwzsg.ddns.net/kp/mods/Kernel_Panic_4.9.sd7

----

==Media:==

===Youtube Videos:===

[http://youtube.com/watch?v=doF7owZ0blk&fmt=18 http://i.ytimg.com/vi/doF7owZ0blk/default.jpg]
[http://youtube.com/watch?v=Ug1c19yaZac http://i.ytimg.com/vi/Ug1c19yaZac/default.jpg] [http://youtube.com/watch?v=GAZQhRlt5bU http://i.ytimg.com/vi/GAZQhRlt5bU/default.jpg]
[http://www.youtube.com/watch?v=3q48ys5hFtI&fmt=18 http://i.ytimg.com/vi/3q48ys5hFtI/default.jpg]

----
===Still shots:===

[http://tof.canardpc.com/view/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg http://tof.canardpc.com/preview/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg] [http://tof.canardpc.com/view/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg http://tof.canardpc.com/preview/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg] [http://tof.canardpc.com/view/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg http://tof.canardpc.com/preview/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg]

[http://tof.canardpc.com/view/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg http://tof.canardpc.com/preview/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg] [http://tof.canardpc.com/view/e5184baf-6c95-4c90-8469-b00a4f092054.jpg http://tof.canardpc.com/preview/e5184baf-6c95-4c90-8469-b00a4f092054.jpg] [http://tof.canardpc.com/view/cbe6dae0-a696-450a-bf22-236043d76511.jpg http://tof.canardpc.com/preview/cbe6dae0-a696-450a-bf22-236043d76511.jpg]

----

==License:==
Extracted from the <code>Kernel_Panic_readme.txt</code> file:

<pre>
========--------------------------------------------
License:
--------
- The content of the /mods/Kernel*.sd7 is Public Domain, save:
/LuaUI/Widgets/kp_buildbar.lua
/LuaRules/Gadgets/autohold.lua
/LuaRules/Gadgets/Burrow.lua
/LuaRules/Gadgets/game_spawn.lua
which are GPL, taken from http://www.caspring.org or http://springrts.com
- The maps Marble Madness and Direct Memory Access are Public Domain
- The maps Major Madness and Speed Balls 16 Way status are unknown
- The maps Central Hub, Corrupted Core, Dual Core, Quad Core were CC BY-NC-SA and are now CC-BY-SA
https://springrts.com/phpbb/viewtopic.php?f=43&t=21331&p=401680#p397471
https://springrts.com/phpbb/viewtopic.php?f=43&t=27499&start=6
- The Spring engine is GPL, available from http://spring.clan-sy.com
</pre>

----

== Game Modes:==
By default the aim is to destroy the homebase and all the minifacs of all opposing teams.
<br /><br />
Other "mod options" available are:
* '''King Of The Hill :''' Keeps control of the map center for a given time to win.
* '''O.N.S. :''' Adds shields to buildings, preventing homebase rush.
* '''Save Our Mem :''' Unit leave "leaks" that must be reclaimed.
* '''Color Wars :''' Whoever controls the most territory when timer elapse wins.
* '''Heroes of Mainframe :''' You only control a very buffed up but single unit. Best used with "Pre-placed Minifacs".
* '''Rebalancing formula :''' Let you change the stat of any units of weapons without the hassle of making a mutator.
<br />
For details, read [http://zwzsg.ddns.net/kp/Kernel_Panic_readme.txt <code>Kernel_Panic_readme.txt</code>] or click [?] next to each mod option in your lobby.
----

==Units and Buildings:==

===System units:===

<table><td>https://springrts.com/mediawiki/images/5/54/96x96Kernel.png</td><td>'''The Kernel:''' You start with one of these. It can build all mobile units in the game. Has rapid auto-heal and lots of health.</td></table>

<table><td>https://springrts.com/mediawiki/images/b/b2/96x96Socket.png</td><td>'''The Socket:''' The socket is a factory which can only be built on a geothermal vent. It can solely build bits, and slower than the kernel can. It autoheals, and has a decent amount of health.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/8c/96x96Terminal.png</td><td>'''The Terminal:''' This is a new structure that gets placed on geovents. It can dispatch a nuclear bomber once every 90 seconds that will deal about 16000 damage to a large target area, i.e. it destroys everything except factories. It does much less damage to the kernel and hole. The bomber can strike any position on the map, there is no defense.</td></table>

<table><td>https://springrts.com/mediawiki/images/1/1e/96x96Assembler.png</td><td>'''The Assembler:''' The assembler is a construction unit. It can build sockets, but it cannot assist-build. Slow, little health. Equipped with a radar to detect mines and other cloacked units.</td></table>

<table><td>https://springrts.com/mediawiki/images/0/0a/96x96Bit.png</td><td>'''The Bit:''' Your basic attacking unit. Cheap, fast, small, not very much health. Is armed with a SPARCling laser. Can be built by a kernel or a socket.</td></table>

<table><td>https://springrts.com/mediawiki/images/e/e3/96x96Byte.png</td><td>'''The Byte:''' A large, strong, and slow attacking unit. Can holds it's own against many bits, as it has lots of health and a powerful gun. More armored when closed. Can plow through bad blocks. The byte has an alternate firing mode, the mine launcher, which throws 5 mines at the cost of much health.</td></table>

<table><td>https://springrts.com/mediawiki/images/5/51/96x96Pointer.png</td><td>'''The Pointer:''' An artillery unit. Its normal shot is not so useful against moving units, but can kill kernels and sockets pretty quickly. Is slow and has little health, so it needs protection. The pointer has an alternate firing mode, the NX Flag, which set a wide area ablaze for a minute, causing constant damage to all units, or buildings within it's range.</td></table>

----

===Hacker units:===
<table><td>https://springrts.com/mediawiki/images/7/7f/96x96NewHoleLow.png</td><td>'''Security Hole:''' The Hacker kernel equivalent.</td></table>

<table><td>https://springrts.com/mediawiki/images/7/70/96x96Window.png</td><td>'''Window:''' The Hacker socket equivalent.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/fb/96x96Obelisk.png</td><td>'''Obelisk:''' This building is a stationary artillery weapon, it can fire an infection shot every 40 seconds (the obelisk has a pink fire on top when it's ready to shoot) that will cover a large area in poison. The poison does a bit of damage (about 1000) and turns any enemy that dies inside the cloud into a Virus. The weapon's range is fairly limited. Best used against stationnary herds of Bits/Bugs.</td></table>

<table><td>https://springrts.com/mediawiki/images/c/c5/96x96NewTrojan.png</td><td>'''Trojan:''' This unit is your constructor as well as radar platform (needed for detecting mines and cloaked units), just like the assembler. It builds all the same stuff as the assembler, except it has the window instead of the socket and the obelisk instead of the terminal.</td></table>

<table><td>https://springrts.com/mediawiki/images/9/94/96x96Virus.png</td><td>'''Virus:''' A crappy little swarm unit. It cannot be built but is produced when killing enemy units with certain weapons. Namely, the Virus, the Worm, and the Obelisk.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/ff/96x96NewBug.png</td><td>'''Bug:''' The Hacker spam unit. The Bug is weaker than the Bit but can sense movement outside of its LOS. It has a stronger weapon and more range but cannot shoot at things behind it or through friendly units and won't take much damage before dying. The mine ability of the old bug has been removed. Instead it can now morph into the Exploit with the deploy button, or the bombard button.</td></table>

<table><td>https://springrts.com/mediawiki/images/c/c4/96x96Exploit.png</td><td>'''Exploit:''' This is the new name for the bug cannon. It's a building the Bug morphs into with the deploy or bombard command. The Exploit is a stationary artillery emplacement that does more damage the further the target is away. Even more frail than the Bug, so don't let any foe come near.</td></table>

<table><td>https://springrts.com/mediawiki/images/4/40/96x96NewWorm.png</td><td>'''Worm:''' The worm is a sneaky assassin, travelling cloacked, then surfacing only to kill many bits at once with its large area of effect weapon, which turn any slain units into virus. The worm large splash damage will damage your own units. However, it does practicaly no damage against other worms or virus. When cloacked, the worm does not automatically attack, you have to give attack orders manually. If you'd rather have your worms auto-attack even when cloacked, set autohold to off. The autohold setting of new worms is inherited from the Security Hole.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/f4/96x96DoS.png</td><td>'''Denial of Service:''' Not an artillery, but close: fire a beam that stun units. For bigger targets it'll take longer to stun them so perform a DDoS (use multiple) to stun them fast. Once the DoS stops firing the target will quickly unfreeze. It moves faster than the pointer but causes a particle trail that can be seen from far away.</td></table>

----

===Network units:===
The network faction is built around mobility, its small factories (Ports) don't produce units openly but instead increment a virtual counter (the Buffer). Packets in the Buffer can be materialized at any teleporter unit (currently that means the Port and the Connection), it's also possible to dematerialize the Packets back into the Buffer by making them enter a teleport.

<table><td>https://springrts.com/mediawiki/images/7/76/96x96Carrier.png</td><td>'''Carrier:''' The base building, like a Kernel or Security Hole.</td></table>

<table><td>https://springrts.com/mediawiki/images/4/46/96x96Port.png</td><td>'''Port:''' The production building. It puts Packets into the Buffer, to materialize them select the Dispatch command. Dispatch will send 12 Packets if available, you can hold ALT when giving the order to make the Port dispatch until the Buffer is empty.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/83/96x96Firewall.png</td><td>'''Firewall:''' This building can cover units (affects friendly units in a certain radius around the target location) in a protective shield for 20 seconds. The shield halves all damage the unit receives and throws the other half back at the attacker.</td></table>

<table><td>https://springrts.com/mediawiki/images/6/6c/96x96Gateway.png</td><td>'''Gateway:''' The constructor. It is lightly armed to help against enemy raids.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/8b/96x96Packet.png</td><td>'''Packet:''' The basic light spam unit, it's weaker in combat than both competitors but much faster.</td></table>

<table><td>https://springrts.com/mediawiki/images/2/26/96x96Connection.png</td><td>'''Connection:''' Mostly a mobile teleporter (i.e. can dispatch Packets and let them enter like a Port). The Connection has decent armor and an arc beam that can do a lot of damage to single targets and has good range. It can defeat most large units one on one but engaging Bytes will probably result in pointer fire which the Connection cannot withstand and the arc beam is not optimal for engaging swarms.</td></table>

<table><td>https://springrts.com/mediawiki/images/0/01/96x96Flow.png</td><td>'''Flow:''' An air unit. The Flow moves fairly slowly but can of course cross any terrain. It's equipped to attack light targets (spam units and fire support) but it's highly vulnerable to return fire. If you want to use them in open combat give them a meatshield and hope the enemy doesn't field long range units, Pointers, DoSes and Connections make short work of Flows if they hit.</td></table>

----

===All side Units:===

<table><td>https://springrts.com/mediawiki/images/9/98/96x96BadBlock.png</td><td>'''The Bad Block:''' A tiny wall, built by Assembler/Trojan/Gateway. Blocks small units movement. Do not block shots however. Easily removed by the Debug or simply crushing them with a Byte or Connection.</td></table>

<table><td>https://springrts.com/mediawiki/images/a/a4/96x96Mine.png</td><td>'''The Logic Bomb:''' A mine that can be built by the Assembler/Trojan/Gateway. And also launched by Bytes. It takes out Bits & Bugs in a single blow, has a decent damage radius, and doesn't chain explode. Use with care, as the blast hurts your own units too. Limited to 32.</td></table>

<table><td>https://springrts.com/mediawiki/images/3/35/96x96MineBlaster.png</td><td>'''The Debug:''' An easy way to clear an area of all mines and walls, this is a one shot weapon built by the Assembler/Trojan/Gateway.</td></table>

----

==Playing Guide for System:==


Playing Kernel Panic is fairly simple and quickly learned, but can be hard to master and can be very complex. It is recommended that beginners start with play the System faction, as they can be considered the least "gimmicky" of the factions.


One rather effective general strategy for a duel on small maps is to send three to five bits to destroy your enemy's early game units, and, to a lesser degree, for scouting purposes. This is most effective if they started with construction units, as this will likely cripple their plans for an early expansion, and gives you a slight head start. After the initial attack, if your scouting shows that your enemy started with offensive units, build a byte for defense, and place it between your Kernel and the hill. After that, build an assembler and use it to build a socket on one the three closest building locations, which should automatically start producing bits. After this, you should order your assembler to build more sockets on free spots close to it. It is crucial that all sockets' rally points are below them, as bits turning inside a socket will stall production until it is able to exit the factory. It is sometimes wise to repeat the prior process with one or two other assemblers. After this is done, construct about ten bits from your factor, and set your kernel to alternate between building bytes and pointers.


What units you build at your kernel, and what you use them for, is an important factor in winning. As buildings can't be resumed, sending in groups of bits to kill construction units creating buildings can be very effective at stopping expansion attempts. Building too many pointers, will result in them being destroyed by connections, bits and especially worms, due to their stealth. Also, bytes are easily destroyer by and pointers, and exploits. A good general purpose ratio seems to be to queue one byte and one pointer, but this will need adapting as the game develops, and depending on the enemy's play style.

Scouting is important too, as many enemies will leave their factories undefended, and knowing their build, and general unit use can help you in adapting the units you use to better fight them. Note that the Network can instantly spawn packets at any of their ports, or connections with their buffer system, meaning that all their factories should be considered defended. Single bits can be used to scout to find the enemy's current expansion attempts.

When attacking a Byte or Connection with bits, it is important to overwhelm it with large numbers of bits. For bytes, try to exploit a byte's blind spot directly under it, by moving bits into that area. If your byte is under attack, moving it backwards to keep the attacking units in it's shooting arc can help repel the attack. It is not recommended to engage a worm with bits, as it's attack will convert your bits to viruses on the worm's owner's side.


On Marble Madness, there are two main ways paths to victory. The simplest one is to control the hill and use pointers stationed on the hill to destroy the enemy's factories, and kernel. Gaining control of the hilltop will likely not be without resistance, because it requires a decent amount of time for units to reach the top of the hill, meaning most units involved will be spam units from your factories on it, and the fact that it will likely be highly contended. However, if you control it, you have a large advantage over the enemy as you can shell your opponents home base with ease. The other way is around the hill, which can be very effective if you control terrain you can use pointers to great effect. In both strategies, using pointers is the crucial factor. While they are hard to use correctly, they are game-winners as they destroy home bases and enemy units with ease.

----

==Credits:==
- Original concept by Boirunner<br>
- About all the work done by KDR_11k<br>
- Sounds by Noruas<br>
- Maintenance by zwzsg<br>
- Maps by Boirunner, Runecrafter, zwzsg, and TradeMark<br>
- Some Lua interface upgrade based of jK and trepan code<br>

----
Back to [[Games]]
[[Category:Games]]

Kernel Panic

2021-06-25T00:38:32Z

Zwzsg: KP 4.8 -> KP 4.9 + fixed links

<center>[http://timblokdijk.nl/spring/Kernel%20Panic/logo/kernel0_hd.png https://springrts.com/mediawiki/images/f/fc/Kernel_Panic_Alpha_Title_Half.png]</center>

==Overview:==

''For the latest news and/or assistance, try the [http://springrts.com/phpbb/viewforum.php?f=43'''KP forum'''] or go to #kp when you log onto the lobby.''

'''Kernel Panic''' is a game about computers. Systems, Hackers and Networks wage war in a matrix of DOOM! The only constraints are time and space; unlike other real time strategy games, no resource economy exists in KP.

All units are free in this game, every factory built will be spamming units at all times. You can build more factories, but only on pre-defined areas (geothermal vents). All that remains is pure strategy and tactics.

KP makes for a frantically fast-paced, action-oriented game, with a very unique graphical style.

----

==Download links:==

Current Version of Kernel Panic is 4.9

* <u>Newcomers:</u>
** If you run '''Windows''' (2000,XP,Vista,7,8,10):
*** Here you can get a complete installer:
*** http://zwzsg.ddns.net/kp/installers/Kernel_Panic_4.9_Including_Spring_105.0_Installer39.exe
*** Use it to install both Spring and Kernel Panic in one go.
*** Then use the shortcuts created in your Start Menu or Desktop.
** If you run '''Linux''':
*** Get a Linux static build of the Spring engine from https://springrts.com/wiki/Download
*** Get and unzip that file: http://zwzsg.ddns.net/kp/zips/Kernel_Panic_4.9.zip
*** Unzip both in the same folder, so that Kernel_Panic_4.9_Launcher_Linux is next to spring executable
*** Run Kernel_Panic_4.9_Launcher_Linux
*** Alternatively, running spring directly would bring a greenish menu once ingame
*** For multiplayer or advanced options, run SpringLobby

* <u>Experienced Users:</u>
** If you have already the Spring engine (or prefer to install it yourself): Here you can get a zip with the mod file, the maps, and a tiny executable for single player frontend. Unzip into your Spring root folder: http://zwzsg.ddns.net/kp/zips/Kernel_Panic_4.9.zip
** If you are certain you have all the maps and just need a quick link to the mod file itself: http://zwzsg.ddns.net/kp/mods/Kernel_Panic_4.9.sd7

----

==Media:==

===Youtube Videos:===

[http://youtube.com/watch?v=doF7owZ0blk&fmt=18 http://i.ytimg.com/vi/doF7owZ0blk/default.jpg]
[http://youtube.com/watch?v=Ug1c19yaZac http://i.ytimg.com/vi/Ug1c19yaZac/default.jpg] [http://youtube.com/watch?v=GAZQhRlt5bU http://i.ytimg.com/vi/GAZQhRlt5bU/default.jpg]
[http://www.youtube.com/watch?v=3q48ys5hFtI&fmt=18 http://i.ytimg.com/vi/3q48ys5hFtI/default.jpg]

----
===Still shots:===

[http://tof.canardpc.com/view/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg http://tof.canardpc.com/preview/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg] [http://tof.canardpc.com/view/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg http://tof.canardpc.com/preview/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg] [http://tof.canardpc.com/view/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg http://tof.canardpc.com/preview/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg]

[http://tof.canardpc.com/view/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg http://tof.canardpc.com/preview/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg] [http://tof.canardpc.com/view/e5184baf-6c95-4c90-8469-b00a4f092054.jpg http://tof.canardpc.com/preview/e5184baf-6c95-4c90-8469-b00a4f092054.jpg] [http://tof.canardpc.com/view/cbe6dae0-a696-450a-bf22-236043d76511.jpg http://tof.canardpc.com/preview/cbe6dae0-a696-450a-bf22-236043d76511.jpg]

----

==License:==
Extracted from the <code>Kernel_Panic_readme.txt</code> file:

<pre>
========--------------------------------------------
License:
--------
- The content of the /mods/Kernel*.sd7 is Public Domain, save:
/LuaUI/Widgets/kp_buildbar.lua
/LuaRules/Gadgets/autohold.lua
/LuaRules/Gadgets/Burrow.lua
/LuaRules/Gadgets/game_spawn.lua
which are GPL, taken from http://www.caspring.org or http://springrts.com
- The maps Marble Madness and Direct Memory Access are Public Domain
- The maps Major Madness and Speed Balls 16 Way status are unknown
- The maps Central Hub, Corrupted Core, Dual Core, Quad Core were CC BY-NC-SA and are now CC-BY-SA
https://springrts.com/phpbb/viewtopic.php?f=43&t=21331&p=401680#p397471
https://springrts.com/phpbb/viewtopic.php?f=43&t=27499&start=6
- The Spring engine is GPL, available from http://spring.clan-sy.com
</pre>

----

== Game Modes:==
By default the aim is to destroy the homebase and all the minifacs of all opposing teams.
<br /><br />
Other "mod options" available are:
* '''King Of The Hill :''' Keeps control of the map center for a given time to win.
* '''O.N.S. :''' Adds shields to buildings, preventing homebase rush.
* '''Save Our Mem :''' Unit leave "leaks" that must be reclaimed.
* '''Color Wars :''' Whoever controls the most territory when timer elapse wins.
* '''Heroes of Mainframe :''' You only control a very buffed up but single unit. Best used with "Pre-placed Minifacs".
* '''Rebalancing formula :''' Let you change the stat of any units of weapons without the hassle of making a mutator.
<br />
For details, read [http://zwzsg.ddns.net/kp/Kernel_Panic_readme.txt <code>Kernel_Panic_readme.txt</code>] or click [?] next to each mod option in your lobby.
----

==Units and Buildings:==

===System units:===

<table><td>https://springrts.com/mediawiki/images/5/54/96x96Kernel.png</td><td>'''The Kernel:''' You start with one of these. It can build all mobile units in the game. Has rapid auto-heal and lots of health.</td></table>

<table><td>https://springrts.com/mediawiki/images/b/b2/96x96Socket.png</td><td>'''The Socket:''' The socket is a factory which can only be built on a geothermal vent. It can solely build bits, and slower than the kernel can. It autoheals, and has a decent amount of health.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/8c/96x96Terminal.png</td><td>'''The Terminal:''' This is a new structure that gets placed on geovents. It can dispatch a nuclear bomber once every 90 seconds that will deal about 16000 damage to a large target area, i.e. it destroys everything except factories. It does much less damage to the kernel and hole. The bomber can strike any position on the map, there is no defense.</td></table>

<table><td>https://springrts.com/mediawiki/images/1/1e/96x96Assembler.png</td><td>'''The Assembler:''' The assembler is a construction unit. It can build sockets, but it cannot assist-build. Slow, little health. Equipped with a radar to detect mines and other cloacked units.</td></table>

<table><td>https://springrts.com/mediawiki/images/0/0a/96x96Bit.png</td><td>'''The Bit:''' Your basic attacking unit. Cheap, fast, small, not very much health. Is armed with a SPARCling laser. Can be built by a kernel or a socket.</td></table>

<table><td>https://springrts.com/mediawiki/images/e/e3/96x96Byte.png</td><td>'''The Byte:''' A large, strong, and slow attacking unit. Can holds it's own against many bits, as it has lots of health and a powerful gun. More armored when closed. Can plow through bad blocks. The byte has an alternate firing mode, the mine launcher, which throws 5 mines at the cost of much health.</td></table>

<table><td>https://springrts.com/mediawiki/images/5/51/96x96Pointer.png</td><td>'''The Pointer:''' An artillery unit. Its normal shot is not so useful against moving units, but can kill kernels and sockets pretty quickly. Is slow and has little health, so it needs protection. The pointer has an alternate firing mode, the NX Flag, which set a wide area ablaze for a minute, causing constant damage to all units, or buildings within it's range.</td></table>

----

===Hacker units:===
<table><td>https://springrts.com/mediawiki/images/7/7f/96x96NewHoleLow.png</td><td>'''Security Hole:''' The Hacker kernel equivalent.</td></table>

<table><td>https://springrts.com/mediawiki/images/7/70/96x96Window.png</td><td>'''Window:''' The Hacker socket equivalent.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/fb/96x96Obelisk.png</td><td>'''Obelisk:''' This building is a stationary artillery weapon, it can fire an infection shot every 40 seconds (the obelisk has a pink fire on top when it's ready to shoot) that will cover a large area in poison. The poison does a bit of damage (about 1000) and turns any enemy that dies inside the cloud into a Virus. The weapon's range is fairly limited. Best used against stationnary herds of Bits/Bugs.</td></table>

<table><td>https://springrts.com/mediawiki/images/c/c5/96x96NewTrojan.png</td><td>'''Trojan:''' This unit is your constructor as well as radar platform (needed for detecting mines and cloaked units), just like the assembler. It builds all the same stuff as the assembler, except it has the window instead of the socket and the obelisk instead of the terminal.</td></table>

<table><td>https://springrts.com/mediawiki/images/9/94/96x96Virus.png</td><td>'''Virus:''' A crappy little swarm unit. It cannot be built but is produced when killing enemy units with certain weapons. Namely, the Virus, the Worm, and the Obelisk.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/ff/96x96NewBug.png</td><td>'''Bug:''' The Hacker spam unit. The Bug is weaker than the Bit but can sense movement outside of its LOS. It has a stronger weapon and more range but cannot shoot at things behind it or through friendly units and won't take much damage before dying. The mine ability of the old bug has been removed. Instead it can now morph into the Exploit with the deploy button, or the bombard button.</td></table>

<table><td>https://springrts.com/mediawiki/images/c/c4/96x96Exploit.png</td><td>'''Exploit:''' This is the new name for the bug cannon. It's a building the Bug morphs into with the deploy or bombard command. The Exploit is a stationary artillery emplacement that does more damage the further the target is away. Even more frail than the Bug, so don't let any foe come near.</td></table>

<table><td>https://springrts.com/mediawiki/images/4/40/96x96NewWorm.png</td><td>'''Worm:''' The worm is a sneaky assassin, travelling cloacked, then surfacing only to kill many bits at once with its large area of effect weapon, which turn any slain units into virus. The worm large splash damage will damage your own units. However, it does practicaly no damage against other worms or virus. When cloacked, the worm does not automatically attack, you have to give attack orders manually. If you'd rather have your worms auto-attack even when cloacked, set autohold to off. The autohold setting of new worms is inherited from the Security Hole.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/f4/96x96DoS.png</td><td>'''Denial of Service:''' Not an artillery, but close: fire a beam that stun units. For bigger targets it'll take longer to stun them so perform a DDoS (use multiple) to stun them fast. Once the DoS stops firing the target will quickly unfreeze. It moves faster than the pointer but causes a particle trail that can be seen from far away.</td></table>

----

===Network units:===
The network faction is built around mobility, its small factories (Ports) don't produce units openly but instead increment a virtual counter (the Buffer). Packets in the Buffer can be materialized at any teleporter unit (currently that means the Port and the Connection), it's also possible to dematerialize the Packets back into the Buffer by making them enter a teleport.

<table><td>https://springrts.com/mediawiki/images/7/76/96x96Carrier.png</td><td>'''Carrier:''' The base building, like a Kernel or Security Hole.</td></table>

<table><td>https://springrts.com/mediawiki/images/4/46/96x96Port.png</td><td>'''Port:''' The production building. It puts Packets into the Buffer, to materialize them select the Dispatch command. Dispatch will send 12 Packets if available, you can hold ALT when giving the order to make the Port dispatch until the Buffer is empty.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/83/96x96Firewall.png</td><td>'''Firewall:''' This building can cover units (affects friendly units in a certain radius around the target location) in a protective shield for 20 seconds. The shield halves all damage the unit receives and throws the other half back at the attacker.</td></table>

<table><td>https://springrts.com/mediawiki/images/6/6c/96x96Gateway.png</td><td>'''Gateway:''' The constructor. It is lightly armed to help against enemy raids.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/8b/96x96Packet.png</td><td>'''Packet:''' The basic light spam unit, it's weaker in combat than both competitors but much faster.</td></table>

<table><td>https://springrts.com/mediawiki/images/2/26/96x96Connection.png</td><td>'''Connection:''' Mostly a mobile teleporter (i.e. can dispatch Packets and let them enter like a Port). The Connection has decent armor and an arc beam that can do a lot of damage to single targets and has good range. It can defeat most large units one on one but engaging Bytes will probably result in pointer fire which the Connection cannot withstand and the arc beam is not optimal for engaging swarms.</td></table>

<table><td>https://springrts.com/mediawiki/images/0/01/96x96Flow.png</td><td>'''Flow:''' An air unit. The Flow moves fairly slowly but can of course cross any terrain. It's equipped to attack light targets (spam units and fire support) but it's highly vulnerable to return fire. If you want to use them in open combat give them a meatshield and hope the enemy doesn't field long range units, Pointers, DoSes and Connections make short work of Flows if they hit.</td></table>

----

===All side Units:===

<table><td>https://springrts.com/mediawiki/images/9/98/96x96BadBlock.png</td><td>'''The Bad Block:''' A tiny wall, built by Assembler/Trojan/Gateway. Blocks small units movement. Do not block shots however. Easily removed by the Debug or simply crushing them with a Byte or Connection.</td></table>

<table><td>https://springrts.com/mediawiki/images/a/a4/96x96Mine.png</td><td>'''The Logic Bomb:''' A mine that can be built by the Assembler/Trojan/Gateway. And also launched by Bytes. It takes out Bits & Bugs in a single blow, has a decent damage radius, and doesn't chain explode. Use with care, as the blast hurts your own units too. Limited to 32.</td></table>

<table><td>https://springrts.com/mediawiki/images/3/35/96x96MineBlaster.png</td><td>'''The Debug:''' An easy way to clear an area of all mines and walls, this is a one shot weapon built by the Assembler/Trojan/Gateway.</td></table>

----

==Playing Guide for System:==


Playing Kernel Panic is fairly simple and quickly learned, but can be hard to master and can be very complex. It is recommended that beginners start with play the System faction, as they can be considered the least "gimmicky" of the factions.


One rather effective general strategy for a duel on small maps is to send three to five bits to destroy your enemy's early game units, and, to a lesser degree, for scouting purposes. This is most effective if they started with construction units, as this will likely cripple their plans for an early expansion, and gives you a slight head start. After the initial attack, if your scouting shows that your enemy started with offensive units, build a byte for defense, and place it between your Kernel and the hill. After that, build an assembler and use it to build a socket on one the three closest building locations, which should automatically start producing bits. After this, you should order your assembler to build more sockets on free spots close to it. It is crucial that all sockets' rally points are below them, as bits turning inside a socket will stall production until it is able to exit the factory. It is sometimes wise to repeat the prior process with one or two other assemblers. After this is done, construct about ten bits from your factor, and set your kernel to alternate between building bytes and pointers.


What units you build at your kernel, and what you use them for, is an important factor in winning. As buildings can't be resumed, sending in groups of bits to kill construction units creating buildings can be very effective at stopping expansion attempts. Building too many pointers, will result in them being destroyed by connections, bits and especially worms, due to their stealth. Also, bytes are easily destroyer by and pointers, and exploits. A good general purpose ratio seems to be to queue one byte and one pointer, but this will need adapting as the game develops, and depending on the enemy's play style.

Scouting is important too, as many enemies will leave their factories undefended, and knowing their build, and general unit use can help you in adapting the units you use to better fight them. Note that the Network can instantly spawn packets at any of their ports, or connections with their buffer system, meaning that all their factories should be considered defended. Single bits can be used to scout to find the enemy's current expansion attempts.

When attacking a Byte or Connection with bits, it is important to overwhelm it with large numbers of bits. For bytes, try to exploit a byte's blind spot directly under it, by moving bits into that area. If your byte is under attack, moving it backwards to keep the attacking units in it's shooting arc can help repel the attack. It is not recommended to engage a worm with bits, as it's attack will convert your bits to viruses on the worm's owner's side.


On Marble Madness, there are two main ways paths to victory. The simplest one is to control the hill and use pointers stationed on the hill to destroy the enemy's factories, and kernel. Gaining control of the hilltop will likely not be without resistance, because it requires a decent amount of time for units to reach the top of the hill, meaning most units involved will be spam units from your factories on it, and the fact that it will likely be highly contended. However, if you control it, you have a large advantage over the enemy as you can shell your opponents home base with ease. The other way is around the hill, which can be very effective if you control terrain you can use pointers to great effect. In both strategies, using pointers is the crucial factor. While they are hard to use correctly, they are game-winners as they destroy home bases and enemy units with ease.

----

==Credits:==
- Original concept by Boirunner<br>
- About all the work done by KDR_11k<br>
- Sounds by Noruas<br>
- Maintenance by zwzsg<br>
- Maps by Boirunner, Runecrafter, zwzsg, and TradeMark<br>
- Some Lua interface upgrade based of jK and trepan code<br>

----
Back to [[Games]]
[[Category:Games]]

File:Kernel Panic 4.9 poster.png

2021-06-25T00:03:32Z

Zwzsg: Promotional Picture for Kernel Panic 4.9

== Summary ==
Promotional Picture for Kernel Panic 4.9

Kernel Panic

2019-04-28T03:18:41Z

Zwzsg: 4.7 -> 4.8

<center>[http://timblokdijk.nl/spring/Kernel%20Panic/logo/kernel0_hd.png https://springrts.com/mediawiki/images/f/fc/Kernel_Panic_Alpha_Title_Half.png]</center>

==Overview:==

''For the latest news and/or assistance, try the [http://springrts.com/phpbb/viewforum.php?f=43'''KP forum'''] or go to #kp when you log onto the lobby.''

'''Kernel Panic''' is a game about computers. Systems, Hackers and Networks wage war in a matrix of DOOM! The only constraints are time and space; unlike other real time strategy games, no resource economy exists in KP.

All units are free in this game, every factory built will be spamming units at all times. You can build more factories, but only on pre-defined areas (geothermal vents). All that remains is pure strategy and tactics.

KP makes for a frantically fast-paced, action-oriented game, with a very unique graphical style.

----

==Download links:==

Current Version of Kernel Panic is 4.8

* <u>Newcomers:</u>
** If you run '''Windows''' (2000,XP,Vista,7,8,10):
*** Here you can get a complete installer:
*** http://springfiles.com/spring/game-installers/kernel-panic-installer
*** Use it to install both Spring and Kernel Panic in one go.
*** Then use the shortcuts created in your Start Menu or Desktop.
** If you run '''Linux''':
*** Get a Linux static build of the Spring engine from https://springrts.com/wiki/Download
*** Get and unzip that file: http://springfiles.com/spring/game-installers/kernel-panic-zip
*** Unzip both in the same folder, so that Kernel_Panic_4.8_Launcher_Linux is next to spring executable
*** Run Kernel_Panic_4.8_Launcher_Linux
*** Alternatively, running spring directly would bring a greenish menu once ingame
*** For multiplayer or advanced options, run SpringLobby

* <u>Experienced Users:</u>
** If you have already the Spring engine (or prefer to install it yourself): Here you can get a zip with the mod file, the maps, and a tiny executable for single player frontend. Unzip into your Spring root folder: http://springfiles.com/spring/game-installers/kernel-panic-zip
** If you are certain you have all the maps and just need a quick link to the mod file itself: http://springfiles.com/spring/games/kernel-panic-mod

----

==Media:==

===Youtube Videos:===

[http://youtube.com/watch?v=doF7owZ0blk&fmt=18 http://i.ytimg.com/vi/doF7owZ0blk/default.jpg]
[http://youtube.com/watch?v=Ug1c19yaZac http://i.ytimg.com/vi/Ug1c19yaZac/default.jpg] [http://youtube.com/watch?v=GAZQhRlt5bU http://i.ytimg.com/vi/GAZQhRlt5bU/default.jpg]
[http://www.youtube.com/watch?v=3q48ys5hFtI&fmt=18 http://i.ytimg.com/vi/3q48ys5hFtI/default.jpg]

----
===Still shots:===

[http://tof.canardpc.com/view/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg http://tof.canardpc.com/preview/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg] [http://tof.canardpc.com/view/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg http://tof.canardpc.com/preview/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg] [http://tof.canardpc.com/view/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg http://tof.canardpc.com/preview/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg]

[http://tof.canardpc.com/view/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg http://tof.canardpc.com/preview/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg] [http://tof.canardpc.com/view/e5184baf-6c95-4c90-8469-b00a4f092054.jpg http://tof.canardpc.com/preview/e5184baf-6c95-4c90-8469-b00a4f092054.jpg] [http://tof.canardpc.com/view/cbe6dae0-a696-450a-bf22-236043d76511.jpg http://tof.canardpc.com/preview/cbe6dae0-a696-450a-bf22-236043d76511.jpg]

----

==License:==
Extracted from the [http://pastebin.ca/2834721 <code>Kernel_Panic_readme.txt</code>] file:

<pre>
========--------------------------------------------
License:
--------
- The content of the /games/Kernel*.sd7 is Public Domain, save:
/LuaUI/Widgets/kp_buildbar.lua
/LuaRules/Gadgets/autohold.lua
/LuaRules/Gadgets/Burrow.lua
/LuaRules/Gadgets/game_spawn.lua
which are GPL, taken from http://www.caspring.org or http://springrts.com
- The maps Marble Madness and Direct Memory Access are Public Domain
- The maps Major Madness and Speed Balls 16 Way are status unknown
- The maps Central Hub, Corrupted Core, Dual Core, Quad Core are CC BY-SA
- The Spring engine is GPL, available from https://springrts.com
</pre>



----

== Game Modes:==
By default the aim is to destroy the homebase and all the minifacs of all opposing teams.
<br /><br />
Other "mod options" available are:
* '''King Of The Hill :''' Keeps control of the map center for a given time to win.
* '''O.N.S. :''' Adds shields to buildings, preventing homebase rush.
* '''Save Our Mem :''' Unit leave "leaks" that must be reclaimed.
* '''Color Wars :''' Whoever controls the most territory when timer elapse wins.
* '''Heroes of Mainframe :''' You only control a very buffed up but single unit. Best used with "Pre-placed Minifacs".
* '''Rebalancing formula :''' Let you change the stat of any units of weapons without the hassle of making a mutator.
<br />
For details, read [http://pastebin.ca/2834721 <code>Kernel_Panic_readme.txt</code>] or click [?] next to each mod option in your lobby.
----

==Units and Buildings:==

===System units:===

<table><td>https://springrts.com/mediawiki/images/5/54/96x96Kernel.png</td><td>'''The Kernel:''' You start with one of these. It can build all mobile units in the game. Has rapid auto-heal and lots of health.</td></table>

<table><td>https://springrts.com/mediawiki/images/b/b2/96x96Socket.png</td><td>'''The Socket:''' The socket is a factory which can only be built on a geothermal vent. It can solely build bits, and slower than the kernel can. It autoheals, and has a decent amount of health.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/8c/96x96Terminal.png</td><td>'''The Terminal:''' This is a new structure that gets placed on geovents. It can dispatch a nuclear bomber once every 90 seconds that will deal about 16000 damage to a large target area, i.e. it destroys everything except factories. It does much less damage to the kernel and hole. The bomber can strike any position on the map, there is no defense.</td></table>

<table><td>https://springrts.com/mediawiki/images/1/1e/96x96Assembler.png</td><td>'''The Assembler:''' The assembler is a construction unit. It can build sockets, but it cannot assist-build. Slow, little health. Equipped with a radar to detect mines and other cloacked units.</td></table>

<table><td>https://springrts.com/mediawiki/images/0/0a/96x96Bit.png</td><td>'''The Bit:''' Your basic attacking unit. Cheap, fast, small, not very much health. Is armed with a SPARCling laser. Can be built by a kernel or a socket.</td></table>

<table><td>https://springrts.com/mediawiki/images/e/e3/96x96Byte.png</td><td>'''The Byte:''' A large, strong, and slow attacking unit. Can holds it's own against many bits, as it has lots of health and a powerful gun. More armored when closed. Can plow through bad blocks. The byte has an alternate firing mode, the mine launcher, which throws 5 mines at the cost of much health.</td></table>

<table><td>https://springrts.com/mediawiki/images/5/51/96x96Pointer.png</td><td>'''The Pointer:''' An artillery unit. Its normal shot is not so useful against moving units, but can kill kernels and sockets pretty quickly. Is slow and has little health, so it needs protection. The pointer has an alternate firing mode, the NX Flag, which set a wide area ablaze for a minute, causing constant damage to all units, or buildings within it's range.</td></table>

----

===Hacker units:===
<table><td>https://springrts.com/mediawiki/images/7/7f/96x96NewHoleLow.png</td><td>'''Security Hole:''' The Hacker kernel equivalent.</td></table>

<table><td>https://springrts.com/mediawiki/images/7/70/96x96Window.png</td><td>'''Window:''' The Hacker socket equivalent.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/fb/96x96Obelisk.png</td><td>'''Obelisk:''' This building is a stationary artillery weapon, it can fire an infection shot every 40 seconds (the obelisk has a pink fire on top when it's ready to shoot) that will cover a large area in poison. The poison does a bit of damage (about 1000) and turns any enemy that dies inside the cloud into a Virus. The weapon's range is fairly limited. Best used against stationnary herds of Bits/Bugs.</td></table>

<table><td>https://springrts.com/mediawiki/images/c/c5/96x96NewTrojan.png</td><td>'''Trojan:''' This unit is your constructor as well as radar platform (needed for detecting mines and cloaked units), just like the assembler. It builds all the same stuff as the assembler, except it has the window instead of the socket and the obelisk instead of the terminal.</td></table>

<table><td>https://springrts.com/mediawiki/images/9/94/96x96Virus.png</td><td>'''Virus:''' A crappy little swarm unit. It cannot be built but is produced when killing enemy units with certain weapons. Namely, the Virus, the Worm, and the Obelisk.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/ff/96x96NewBug.png</td><td>'''Bug:''' The Hacker spam unit. The Bug is weaker than the Bit but can sense movement outside of its LOS. It has a stronger weapon and more range but cannot shoot at things behind it or through friendly units and won't take much damage before dying. The mine ability of the old bug has been removed. Instead it can now morph into the Exploit with the deploy button, or the bombard button.</td></table>

<table><td>https://springrts.com/mediawiki/images/c/c4/96x96Exploit.png</td><td>'''Exploit:''' This is the new name for the bug cannon. It's a building the Bug morphs into with the deploy or bombard command. The Exploit is a stationary artillery emplacement that does more damage the further the target is away. Even more frail than the Bug, so don't let any foe come near.</td></table>

<table><td>https://springrts.com/mediawiki/images/4/40/96x96NewWorm.png</td><td>'''Worm:''' The worm is a sneaky assassin, travelling cloacked, then surfacing only to kill many bits at once with its large area of effect weapon, which turn any slain units into virus. The worm large splash damage will damage your own units. However, it does practicaly no damage against other worms or virus. When cloacked, the worm does not automatically attack, you have to give attack orders manually. If you'd rather have your worms auto-attack even when cloacked, set autohold to off. The autohold setting of new worms is inherited from the Security Hole.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/f4/96x96DoS.png</td><td>'''Denial of Service:''' Not an artillery, but close: fire a beam that stun units. For bigger targets it'll take longer to stun them so perform a DDoS (use multiple) to stun them fast. Once the DoS stops firing the target will quickly unfreeze. It moves faster than the pointer but causes a particle trail that can be seen from far away.</td></table>

----

===Network units:===
The network faction is built around mobility, its small factories (Ports) don't produce units openly but instead increment a virtual counter (the Buffer). Packets in the Buffer can be materialized at any teleporter unit (currently that means the Port and the Connection), it's also possible to dematerialize the Packets back into the Buffer by making them enter a teleport.

<table><td>https://springrts.com/mediawiki/images/7/76/96x96Carrier.png</td><td>'''Carrier:''' The base building, like a Kernel or Security Hole.</td></table>

<table><td>https://springrts.com/mediawiki/images/4/46/96x96Port.png</td><td>'''Port:''' The production building. It puts Packets into the Buffer, to materialize them select the Dispatch command. Dispatch will send 12 Packets if available, you can hold ALT when giving the order to make the Port dispatch until the Buffer is empty.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/83/96x96Firewall.png</td><td>'''Firewall:''' This building can cover units (affects friendly units in a certain radius around the target location) in a protective shield for 20 seconds. The shield halves all damage the unit receives and throws the other half back at the attacker.</td></table>

<table><td>https://springrts.com/mediawiki/images/6/6c/96x96Gateway.png</td><td>'''Gateway:''' The constructor. It is lightly armed to help against enemy raids.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/8b/96x96Packet.png</td><td>'''Packet:''' The basic light spam unit, it's weaker in combat than both competitors but much faster.</td></table>

<table><td>https://springrts.com/mediawiki/images/2/26/96x96Connection.png</td><td>'''Connection:''' Mostly a mobile teleporter (i.e. can dispatch Packets and let them enter like a Port). The Connection has decent armor and an arc beam that can do a lot of damage to single targets and has good range. It can defeat most large units one on one but engaging Bytes will probably result in pointer fire which the Connection cannot withstand and the arc beam is not optimal for engaging swarms.</td></table>

<table><td>https://springrts.com/mediawiki/images/0/01/96x96Flow.png</td><td>'''Flow:''' An air unit. The Flow moves fairly slowly but can of course cross any terrain. It's equipped to attack light targets (spam units and fire support) but it's highly vulnerable to return fire. If you want to use them in open combat give them a meatshield and hope the enemy doesn't field long range units, Pointers, DoSes and Connections make short work of Flows if they hit.</td></table>

----

===All side Units:===

<table><td>https://springrts.com/mediawiki/images/9/98/96x96BadBlock.png</td><td>'''The Bad Block:''' A tiny wall, built by Assembler/Trojan/Gateway. Blocks small units movement. Do not block shots however. Easily removed by the Debug or simply crushing them with a Byte or Connection.</td></table>

<table><td>https://springrts.com/mediawiki/images/a/a4/96x96Mine.png</td><td>'''The Logic Bomb:''' A mine that can be built by the Assembler/Trojan/Gateway. And also launched by Bytes. It takes out Bits & Bugs in a single blow, has a decent damage radius, and doesn't chain explode. Use with care, as the blast hurts your own units too. Limited to 32.</td></table>

<table><td>https://springrts.com/mediawiki/images/3/35/96x96MineBlaster.png</td><td>'''The Debug:''' An easy way to clear an area of all mines and walls, this is a one shot weapon built by the Assembler/Trojan/Gateway.</td></table>

----

==Playing Guide for System:==


Playing Kernel Panic is fairly simple and quickly learned, but can be hard to master and can be very complex. It is recommended that beginners start with play the System faction, as they can be considered the least "gimmicky" of the factions.


One rather effective general strategy for a duel on small maps is to send three to five bits to destroy your enemy's early game units, and, to a lesser degree, for scouting purposes. This is most effective if they started with construction units, as this will likely cripple their plans for an early expansion, and gives you a slight head start. After the initial attack, if your scouting shows that your enemy started with offensive units, build a byte for defense, and place it between your Kernel and the hill. After that, build an assembler and use it to build a socket on one the three closest building locations, which should automatically start producing bits. After this, you should order your assembler to build more sockets on free spots close to it. It is crucial that all sockets' rally points are below them, as bits turning inside a socket will stall production until it is able to exit the factory. It is sometimes wise to repeat the prior process with one or two other assemblers. After this is done, construct about ten bits from your factor, and set your kernel to alternate between building bytes and pointers.


What units you build at your kernel, and what you use them for, is an important factor in winning. As buildings can't be resumed, sending in groups of bits to kill construction units creating buildings can be very effective at stopping expansion attempts. Building too many pointers, will result in them being destroyed by connections, bits and especially worms, due to their stealth. Also, bytes are easily destroyer by and pointers, and exploits. A good general purpose ratio seems to be to queue one byte and one pointer, but this will need adapting as the game develops, and depending on the enemy's play style.

Scouting is important too, as many enemies will leave their factories undefended, and knowing their build, and general unit use can help you in adapting the units you use to better fight them. Note that the Network can instantly spawn packets at any of their ports, or connections with their buffer system, meaning that all their factories should be considered defended. Single bits can be used to scout to find the enemy's current expansion attempts.

When attacking a Byte or Connection with bits, it is important to overwhelm it with large numbers of bits. For bytes, try to exploit a byte's blind spot directly under it, by moving bits into that area. If your byte is under attack, moving it backwards to keep the attacking units in it's shooting arc can help repel the attack. It is not recommended to engage a worm with bits, as it's attack will convert your bits to viruses on the worm's owner's side.


On Marble Madness, there are two main ways paths to victory. The simplest one is to control the hill and use pointers stationed on the hill to destroy the enemy's factories, and kernel. Gaining control of the hilltop will likely not be without resistance, because it requires a decent amount of time for units to reach the top of the hill, meaning most units involved will be spam units from your factories on it, and the fact that it will likely be highly contended. However, if you control it, you have a large advantage over the enemy as you can shell your opponents home base with ease. The other way is around the hill, which can be very effective if you control terrain you can use pointers to great effect. In both strategies, using pointers is the crucial factor. While they are hard to use correctly, they are game-winners as they destroy home bases and enemy units with ease.

----

==Credits:==
- Original concept by Boirunner<br>
- About all the work done by KDR_11k<br>
- Sounds by Noruas<br>
- Maintenance by zwzsg<br>
- Maps by Boirunner, Runecrafter, zwzsg, and TradeMark<br>
- Some Lua interface upgrade based of jK and trepan code<br>

----
Back to [[Games]]
[[Category:Games]]

Kernel Panic

2019-04-28T02:57:22Z

Zwzsg: Game Mode & Unit guide section visible again

<center>[http://timblokdijk.nl/spring/Kernel%20Panic/logo/kernel0_hd.png https://springrts.com/mediawiki/images/f/fc/Kernel_Panic_Alpha_Title_Half.png]</center>

==Overview:==

''For the latest news and/or assistance, try the [http://springrts.com/phpbb/viewforum.php?f=43'''KP forum'''] or go to #kp when you log onto the lobby.''

'''Kernel Panic''' is a game about computers. Systems, Hackers and Networks wage war in a matrix of DOOM! The only constraints are time and space; unlike other real time strategy games, no resource economy exists in KP.

All units are free in this game, every factory built will be spamming units at all times. You can build more factories, but only on pre-defined areas (geothermal vents). All that remains is pure strategy and tactics.

KP makes for a frantically fast-paced, action-oriented game, with a very unique graphical style.

----

==Download links:==

Current Version of Kernel Panic is 4.7

* <u>Newcomers:</u>
** If you run '''Windows''' (2000,XP,Vista,7,8,10):
*** Here you can get a complete installer:
*** http://springfiles.com/spring/game-installers/kernel-panic-installer
*** Use it to install both Spring and Kernel Panic in one go.
*** Then use the shortcuts created in your Start Menu or Desktop.
** If you run '''Linux''':
*** Get a Linux static build of the Spring engine from https://springrts.com/wiki/Download
*** Get and unzip that file: http://springfiles.com/spring/game-installers/kernel-panic-zip
*** Unzip both in the same folder, so that Kernel_Panic_4.7_Launcher_Linux is next to spring executable
*** Run Kernel_Panic_4.7_Launcher_Linux
*** Alternatively, running spring directly would bring a greenish menu once ingame
*** For multiplayer or advanced options, run SpringLobby

* <u>Experienced Users:</u>
** If you have already the Spring engine (or prefer to install it yourself): Here you can get a zip with the mod file, the maps, and a tiny executable for single player frontend. Unzip into your Spring root folder: http://springfiles.com/spring/game-installers/kernel-panic-zip
** If you are certain you have all the maps and just need a quick link to the mod file itself: http://springfiles.com/spring/games/kernel-panic-mod

----

==Media:==

===Youtube Videos:===

[http://youtube.com/watch?v=doF7owZ0blk&fmt=18 http://i.ytimg.com/vi/doF7owZ0blk/default.jpg]
[http://youtube.com/watch?v=Ug1c19yaZac http://i.ytimg.com/vi/Ug1c19yaZac/default.jpg] [http://youtube.com/watch?v=GAZQhRlt5bU http://i.ytimg.com/vi/GAZQhRlt5bU/default.jpg]
[http://www.youtube.com/watch?v=3q48ys5hFtI&fmt=18 http://i.ytimg.com/vi/3q48ys5hFtI/default.jpg]

----
===Still shots:===

[http://tof.canardpc.com/view/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg http://tof.canardpc.com/preview/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg] [http://tof.canardpc.com/view/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg http://tof.canardpc.com/preview/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg] [http://tof.canardpc.com/view/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg http://tof.canardpc.com/preview/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg]

[http://tof.canardpc.com/view/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg http://tof.canardpc.com/preview/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg] [http://tof.canardpc.com/view/e5184baf-6c95-4c90-8469-b00a4f092054.jpg http://tof.canardpc.com/preview/e5184baf-6c95-4c90-8469-b00a4f092054.jpg] [http://tof.canardpc.com/view/cbe6dae0-a696-450a-bf22-236043d76511.jpg http://tof.canardpc.com/preview/cbe6dae0-a696-450a-bf22-236043d76511.jpg]

----

==License:==
Extracted from the [http://pastebin.ca/2834721 <code>Kernel_Panic_readme.txt</code>] file:

<pre>
========--------------------------------------------
License:
--------
- The content of the /games/Kernel*.sd7 is Public Domain, save:
/LuaUI/Widgets/kp_buildbar.lua
/LuaRules/Gadgets/autohold.lua
/LuaRules/Gadgets/Burrow.lua
/LuaRules/Gadgets/game_spawn.lua
which are GPL, taken from http://www.caspring.org or http://springrts.com
- The maps Marble Madness and Direct Memory Access are Public Domain
- The maps Major Madness and Speed Balls 16 Way are status unknown
- The maps Central Hub, Corrupted Core, Dual Core, Quad Core are CC BY-SA
- The Spring engine is GPL, available from https://springrts.com
</pre>



----

== Game Modes:==
By default the aim is to destroy the homebase and all the minifacs of all opposing teams.
<br /><br />
Other "mod options" available are:
* '''King Of The Hill :''' Keeps control of the map center for a given time to win.
* '''O.N.S. :''' Adds shields to buildings, preventing homebase rush.
* '''Save Our Mem :''' Unit leave "leaks" that must be reclaimed.
* '''Color Wars :''' Whoever controls the most territory when timer elapse wins.
* '''Heroes of Mainframe :''' You only control a very buffed up but single unit. Best used with "Pre-placed Minifacs".
* '''Rebalancing formula :''' Let you change the stat of any units of weapons without the hassle of making a mutator.
<br />
For details, read [http://pastebin.ca/2834721 <code>Kernel_Panic_readme.txt</code>] or click [?] next to each mod option in your lobby.
----

==Units and Buildings:==

===System units:===

<table><td>https://springrts.com/mediawiki/images/5/54/96x96Kernel.png</td><td>'''The Kernel:''' You start with one of these. It can build all mobile units in the game. Has rapid auto-heal and lots of health.</td></table>

<table><td>https://springrts.com/mediawiki/images/b/b2/96x96Socket.png</td><td>'''The Socket:''' The socket is a factory which can only be built on a geothermal vent. It can solely build bits, and slower than the kernel can. It autoheals, and has a decent amount of health.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/8c/96x96Terminal.png</td><td>'''The Terminal:''' This is a new structure that gets placed on geovents. It can dispatch a nuclear bomber once every 90 seconds that will deal about 16000 damage to a large target area, i.e. it destroys everything except factories. It does much less damage to the kernel and hole. The bomber can strike any position on the map, there is no defense.</td></table>

<table><td>https://springrts.com/mediawiki/images/1/1e/96x96Assembler.png</td><td>'''The Assembler:''' The assembler is a construction unit. It can build sockets, but it cannot assist-build. Slow, little health. Equipped with a radar to detect mines and other cloacked units.</td></table>

<table><td>https://springrts.com/mediawiki/images/0/0a/96x96Bit.png</td><td>'''The Bit:''' Your basic attacking unit. Cheap, fast, small, not very much health. Is armed with a SPARCling laser. Can be built by a kernel or a socket.</td></table>

<table><td>https://springrts.com/mediawiki/images/e/e3/96x96Byte.png</td><td>'''The Byte:''' A large, strong, and slow attacking unit. Can holds it's own against many bits, as it has lots of health and a powerful gun. More armored when closed. Can plow through bad blocks. The byte has an alternate firing mode, the mine launcher, which throws 5 mines at the cost of much health.</td></table>

<table><td>https://springrts.com/mediawiki/images/5/51/96x96Pointer.png</td><td>'''The Pointer:''' An artillery unit. Its normal shot is not so useful against moving units, but can kill kernels and sockets pretty quickly. Is slow and has little health, so it needs protection. The pointer has an alternate firing mode, the NX Flag, which set a wide area ablaze for a minute, causing constant damage to all units, or buildings within it's range.</td></table>

----

===Hacker units:===
<table><td>https://springrts.com/mediawiki/images/7/7f/96x96NewHoleLow.png</td><td>'''Security Hole:''' The Hacker kernel equivalent.</td></table>

<table><td>https://springrts.com/mediawiki/images/7/70/96x96Window.png</td><td>'''Window:''' The Hacker socket equivalent.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/fb/96x96Obelisk.png</td><td>'''Obelisk:''' This building is a stationary artillery weapon, it can fire an infection shot every 40 seconds (the obelisk has a pink fire on top when it's ready to shoot) that will cover a large area in poison. The poison does a bit of damage (about 1000) and turns any enemy that dies inside the cloud into a Virus. The weapon's range is fairly limited. Best used against stationnary herds of Bits/Bugs.</td></table>

<table><td>https://springrts.com/mediawiki/images/c/c5/96x96NewTrojan.png</td><td>'''Trojan:''' This unit is your constructor as well as radar platform (needed for detecting mines and cloaked units), just like the assembler. It builds all the same stuff as the assembler, except it has the window instead of the socket and the obelisk instead of the terminal.</td></table>

<table><td>https://springrts.com/mediawiki/images/9/94/96x96Virus.png</td><td>'''Virus:''' A crappy little swarm unit. It cannot be built but is produced when killing enemy units with certain weapons. Namely, the Virus, the Worm, and the Obelisk.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/ff/96x96NewBug.png</td><td>'''Bug:''' The Hacker spam unit. The Bug is weaker than the Bit but can sense movement outside of its LOS. It has a stronger weapon and more range but cannot shoot at things behind it or through friendly units and won't take much damage before dying. The mine ability of the old bug has been removed. Instead it can now morph into the Exploit with the deploy button, or the bombard button.</td></table>

<table><td>https://springrts.com/mediawiki/images/c/c4/96x96Exploit.png</td><td>'''Exploit:''' This is the new name for the bug cannon. It's a building the Bug morphs into with the deploy or bombard command. The Exploit is a stationary artillery emplacement that does more damage the further the target is away. Even more frail than the Bug, so don't let any foe come near.</td></table>

<table><td>https://springrts.com/mediawiki/images/4/40/96x96NewWorm.png</td><td>'''Worm:''' The worm is a sneaky assassin, travelling cloacked, then surfacing only to kill many bits at once with its large area of effect weapon, which turn any slain units into virus. The worm large splash damage will damage your own units. However, it does practicaly no damage against other worms or virus. When cloacked, the worm does not automatically attack, you have to give attack orders manually. If you'd rather have your worms auto-attack even when cloacked, set autohold to off. The autohold setting of new worms is inherited from the Security Hole.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/f4/96x96DoS.png</td><td>'''Denial of Service:''' Not an artillery, but close: fire a beam that stun units. For bigger targets it'll take longer to stun them so perform a DDoS (use multiple) to stun them fast. Once the DoS stops firing the target will quickly unfreeze. It moves faster than the pointer but causes a particle trail that can be seen from far away.</td></table>

----

===Network units:===
The network faction is built around mobility, its small factories (Ports) don't produce units openly but instead increment a virtual counter (the Buffer). Packets in the Buffer can be materialized at any teleporter unit (currently that means the Port and the Connection), it's also possible to dematerialize the Packets back into the Buffer by making them enter a teleport.

<table><td>https://springrts.com/mediawiki/images/7/76/96x96Carrier.png</td><td>'''Carrier:''' The base building, like a Kernel or Security Hole.</td></table>

<table><td>https://springrts.com/mediawiki/images/4/46/96x96Port.png</td><td>'''Port:''' The production building. It puts Packets into the Buffer, to materialize them select the Dispatch command. Dispatch will send 12 Packets if available, you can hold ALT when giving the order to make the Port dispatch until the Buffer is empty.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/83/96x96Firewall.png</td><td>'''Firewall:''' This building can cover units (affects friendly units in a certain radius around the target location) in a protective shield for 20 seconds. The shield halves all damage the unit receives and throws the other half back at the attacker.</td></table>

<table><td>https://springrts.com/mediawiki/images/6/6c/96x96Gateway.png</td><td>'''Gateway:''' The constructor. It is lightly armed to help against enemy raids.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/8b/96x96Packet.png</td><td>'''Packet:''' The basic light spam unit, it's weaker in combat than both competitors but much faster.</td></table>

<table><td>https://springrts.com/mediawiki/images/2/26/96x96Connection.png</td><td>'''Connection:''' Mostly a mobile teleporter (i.e. can dispatch Packets and let them enter like a Port). The Connection has decent armor and an arc beam that can do a lot of damage to single targets and has good range. It can defeat most large units one on one but engaging Bytes will probably result in pointer fire which the Connection cannot withstand and the arc beam is not optimal for engaging swarms.</td></table>

<table><td>https://springrts.com/mediawiki/images/0/01/96x96Flow.png</td><td>'''Flow:''' An air unit. The Flow moves fairly slowly but can of course cross any terrain. It's equipped to attack light targets (spam units and fire support) but it's highly vulnerable to return fire. If you want to use them in open combat give them a meatshield and hope the enemy doesn't field long range units, Pointers, DoSes and Connections make short work of Flows if they hit.</td></table>

----

===All side Units:===

<table><td>https://springrts.com/mediawiki/images/9/98/96x96BadBlock.png</td><td>'''The Bad Block:''' A tiny wall, built by Assembler/Trojan/Gateway. Blocks small units movement. Do not block shots however. Easily removed by the Debug or simply crushing them with a Byte or Connection.</td></table>

<table><td>https://springrts.com/mediawiki/images/a/a4/96x96Mine.png</td><td>'''The Logic Bomb:''' A mine that can be built by the Assembler/Trojan/Gateway. And also launched by Bytes. It takes out Bits & Bugs in a single blow, has a decent damage radius, and doesn't chain explode. Use with care, as the blast hurts your own units too. Limited to 32.</td></table>

<table><td>https://springrts.com/mediawiki/images/3/35/96x96MineBlaster.png</td><td>'''The Debug:''' An easy way to clear an area of all mines and walls, this is a one shot weapon built by the Assembler/Trojan/Gateway.</td></table>

----

==Playing Guide for System:==


Playing Kernel Panic is fairly simple and quickly learned, but can be hard to master and can be very complex. It is recommended that beginners start with play the System faction, as they can be considered the least "gimmicky" of the factions.


One rather effective general strategy for a duel on small maps is to send three to five bits to destroy your enemy's early game units, and, to a lesser degree, for scouting purposes. This is most effective if they started with construction units, as this will likely cripple their plans for an early expansion, and gives you a slight head start. After the initial attack, if your scouting shows that your enemy started with offensive units, build a byte for defense, and place it between your Kernel and the hill. After that, build an assembler and use it to build a socket on one the three closest building locations, which should automatically start producing bits. After this, you should order your assembler to build more sockets on free spots close to it. It is crucial that all sockets' rally points are below them, as bits turning inside a socket will stall production until it is able to exit the factory. It is sometimes wise to repeat the prior process with one or two other assemblers. After this is done, construct about ten bits from your factor, and set your kernel to alternate between building bytes and pointers.


What units you build at your kernel, and what you use them for, is an important factor in winning. As buildings can't be resumed, sending in groups of bits to kill construction units creating buildings can be very effective at stopping expansion attempts. Building too many pointers, will result in them being destroyed by connections, bits and especially worms, due to their stealth. Also, bytes are easily destroyer by and pointers, and exploits. A good general purpose ratio seems to be to queue one byte and one pointer, but this will need adapting as the game develops, and depending on the enemy's play style.

Scouting is important too, as many enemies will leave their factories undefended, and knowing their build, and general unit use can help you in adapting the units you use to better fight them. Note that the Network can instantly spawn packets at any of their ports, or connections with their buffer system, meaning that all their factories should be considered defended. Single bits can be used to scout to find the enemy's current expansion attempts.

When attacking a Byte or Connection with bits, it is important to overwhelm it with large numbers of bits. For bytes, try to exploit a byte's blind spot directly under it, by moving bits into that area. If your byte is under attack, moving it backwards to keep the attacking units in it's shooting arc can help repel the attack. It is not recommended to engage a worm with bits, as it's attack will convert your bits to viruses on the worm's owner's side.


On Marble Madness, there are two main ways paths to victory. The simplest one is to control the hill and use pointers stationed on the hill to destroy the enemy's factories, and kernel. Gaining control of the hilltop will likely not be without resistance, because it requires a decent amount of time for units to reach the top of the hill, meaning most units involved will be spam units from your factories on it, and the fact that it will likely be highly contended. However, if you control it, you have a large advantage over the enemy as you can shell your opponents home base with ease. The other way is around the hill, which can be very effective if you control terrain you can use pointers to great effect. In both strategies, using pointers is the crucial factor. While they are hard to use correctly, they are game-winners as they destroy home bases and enemy units with ease.

----

==Credits:==
- Original concept by Boirunner<br>
- About all the work done by KDR_11k<br>
- Sounds by Noruas<br>
- Maintenance by zwzsg<br>
- Maps by Boirunner, Runecrafter, zwzsg, and TradeMark<br>
- Some Lua interface upgrade based of jK and trepan code<br>

----
Back to [[Games]]
[[Category:Games]]

File:Kernel Panic 4.8 poster.png

2019-04-27T19:19:34Z

Zwzsg: Promotional Picture for Kernel Panic 4.8

Promotional Picture for Kernel Panic 4.8

File:Kernel Panic 4.7 poster.png

2019-04-27T19:19:25Z

Zwzsg: Promotional Picture for Kernel Panic 4.7

Promotional Picture for Kernel Panic 4.7

File:Kernel Panic 4.6 poster.png

2019-04-27T19:19:09Z

Zwzsg: Promotional Picture for Kernel Panic 4.6

Promotional Picture for Kernel Panic 4.6

File:Kernel Panic 4.5 poster.png

2019-04-27T19:18:32Z

Zwzsg: Promotional Picture for Kernel Panic 4.5

Promotional Picture for Kernel Panic 4.5

File:Kernel Panic 4.4 poster.png

2019-04-27T19:18:10Z

Zwzsg: Promotional Picture for Kernel Panic 4.4

Promotional Picture for Kernel Panic 4.4

File:Kernel Panic 4.3 poster.png

2019-04-27T19:17:39Z

Zwzsg: Promotional Picture for Kernel Panic 4.3

Promotional Picture for Kernel Panic 4.3

File:Kernel Panic 4.2 poster.png

2019-04-27T19:16:59Z

Zwzsg: Promotional Picture for Kernel Panic 4.2

Promotional Picture for Kernel Panic 4.2

File:Kernel Panic 4.1 poster.png

2019-04-27T19:15:57Z

Zwzsg: Promotional Picture for Kernel Panic 4.1

Promotional Picture for Kernel Panic 4.1

Kernel Panic

2017-06-22T22:20:38Z

Zwzsg: Tell to use static build for linux + Lua is not an acronym

<center>[http://timblokdijk.nl/spring/Kernel%20Panic/logo/kernel0_hd.png https://springrts.com/mediawiki/images/f/fc/Kernel_Panic_Alpha_Title_Half.png]</center>

==Overview:==

''For the latest news and/or assistance, try the [http://springrts.com/phpbb/viewforum.php?f=43'''KP forum'''] or go to #kp when you log onto the lobby.''

'''Kernel Panic''' is a game about computers. Systems, Hackers and Networks wage war in a matrix of DOOM! The only constraints are time and space; unlike other real time strategy games, no resource economy exists in KP.

All units are free in this game, every factory built will be spamming units at all times. You can build more factories, but only on pre-defined areas (geothermal vents). All that remains is pure strategy and tactics.

KP makes for a frantically fast-paced, action-oriented game, with a very unique graphical style.

----

==Download links:==

Current Version of Kernel Panic is 4.7

* <u>Newcomers:</u>
** If you run '''Windows''' (2000,XP,Vista,7,8,10):
*** Here you can get a complete installer:
*** http://springfiles.com/spring/game-installers/kernel-panic-installer
*** Use it to install both Spring and Kernel Panic in one go.
*** Then use the shortcuts created in your Start Menu or Desktop.
** If you run '''Linux''':
*** Get a Linux static build of the Spring engine from https://springrts.com/wiki/Download
*** Get and unzip that file: http://springfiles.com/spring/game-installers/kernel-panic-zip
*** Unzip both in the same folder, so that Kernel_Panic_4.7_Launcher_Linux is next to spring executable
*** Run Kernel_Panic_4.7_Launcher_Linux
*** Alternatively, running spring directly would bring a greenish menu once ingame
*** For multiplayer or advanced options, run SpringLobby

* <u>Experienced Users:</u>
** If you have already the Spring engine (or prefer to install it yourself): Here you can get a zip with the mod file, the maps, and a tiny executable for single player frontend. Unzip into your Spring root folder: http://springfiles.com/spring/game-installers/kernel-panic-zip
** If you are certain you have all the maps and just need a quick link to the mod file itself: http://springfiles.com/spring/games/kernel-panic-mod

----

==Media:==

===Youtube Videos:===

[http://youtube.com/watch?v=doF7owZ0blk&fmt=18 http://i.ytimg.com/vi/doF7owZ0blk/default.jpg]
[http://youtube.com/watch?v=Ug1c19yaZac http://i.ytimg.com/vi/Ug1c19yaZac/default.jpg] [http://youtube.com/watch?v=GAZQhRlt5bU http://i.ytimg.com/vi/GAZQhRlt5bU/default.jpg]
[http://www.youtube.com/watch?v=3q48ys5hFtI&fmt=18 http://i.ytimg.com/vi/3q48ys5hFtI/default.jpg]

----
===Still shots:===

[http://tof.canardpc.com/view/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg http://tof.canardpc.com/preview/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg] [http://tof.canardpc.com/view/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg http://tof.canardpc.com/preview/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg] [http://tof.canardpc.com/view/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg http://tof.canardpc.com/preview/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg]

[http://tof.canardpc.com/view/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg http://tof.canardpc.com/preview/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg] [http://tof.canardpc.com/view/e5184baf-6c95-4c90-8469-b00a4f092054.jpg http://tof.canardpc.com/preview/e5184baf-6c95-4c90-8469-b00a4f092054.jpg] [http://tof.canardpc.com/view/cbe6dae0-a696-450a-bf22-236043d76511.jpg http://tof.canardpc.com/preview/cbe6dae0-a696-450a-bf22-236043d76511.jpg]

----

==License:==
Extracted from the [http://pastebin.ca/2834721 <code>Kernel_Panic_readme.txt</code>] file:

<pre>
========--------------------------------------------
License:
--------
- The content of the /games/Kernel*.sd7 is Public Domain, save:
/LuaUI/Widgets/kp_buildbar.lua
/LuaRules/Gadgets/autohold.lua
/LuaRules/Gadgets/Burrow.lua
/LuaRules/Gadgets/game_spawn.lua
which are GPL, taken from http://www.caspring.org or http://springrts.com
- The maps Marble Madness and Direct Memory Access are Public Domain
- The maps Major Madness and Speed Balls 16 Way status are unknown
- The maps Central Hub, Corrupted Core, Dual Core, Quad Core were initially CC BY-NC-SA.
Then the author removed the CC cause ( http://cpc.cx/4u3 )
- The Spring engine is GPL, available from http://spring.clan-sy.com
</pre>

----

== Game Modes:==
By default the aim is to destroy the homebase and all the minifacs of all opposing teams.
<br /><br />
Other "mod options" available are:
* '''King Of The Hill :''' Keeps control of the map center for a given time to win.
* '''O.N.S. :''' Adds shields to buildings, preventing homebase rush.
* '''Save Our Mem :''' Unit leave "leaks" that must be reclaimed.
* '''Color Wars :''' Whoever controls the most territory when timer elapse wins.
* '''Heroes of Mainframe :''' You only control a very buffed up but single unit. Best used with "Pre-placed Minifacs".
* '''Rebalancing formula :''' Let you change the stat of any units of weapons without the hassle of making a mutator.
<br />
For details, read [http://pastebin.ca/2834721 <code>Kernel_Panic_readme.txt</code>] or click [?] next to each mod option in your lobby.
----

==Units and Buildings:==

===System units:===

<table><td>https://springrts.com/mediawiki/images/5/54/96x96Kernel.png</td><td>'''The Kernel:''' You start with one of these. It can build all mobile units in the game. Has rapid auto-heal and lots of health.</td></table>

<table><td>https://springrts.com/mediawiki/images/b/b2/96x96Socket.png</td><td>'''The Socket:''' The socket is a factory which can only be built on a geothermal vent. It can solely build bits, and slower than the kernel can. It autoheals, and has a decent amount of health.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/8c/96x96Terminal.png</td><td>'''The Terminal:'''(only available in Division Zero) This is a new structure that gets placed on geovents. It can dispatch a nuclear bomber once every 90 seconds that will deal about 16000 damage to a large target area, i.e. it destroys everything except factories. It does much less damage to the kernel and hole. The bomber can strike any position on the map, there is no defense.</td></table>

<table><td>https://springrts.com/mediawiki/images/1/1e/96x96Assembler.png</td><td>'''The Assembler:''' The assembler is a construction unit. It can build sockets, but it cannot assist-build. Slow, little health. Equipped with a radar to detect mines and other cloacked units.</td></table>

<table><td>https://springrts.com/mediawiki/images/0/0a/96x96Bit.png</td><td>'''The Bit:''' Your basic attacking unit. Cheap, fast, small, not very much health. Is armed with a SPARCling laser. Can be built by a kernel or a socket.</td></table>

<table><td>https://springrts.com/mediawiki/images/e/e3/96x96Byte.png</td><td>'''The Byte:''' A large, strong, and slow attacking unit. Can holds it's own against many bits, as it has lots of health and a powerful gun. More armored when closed. Can plow through bad blocks. The byte has an alternate firing mode, the mine launcher, which throws 5 mines at the cost of much health.</td></table>

<table><td>https://springrts.com/mediawiki/images/5/51/96x96Pointer.png</td><td>'''The Pointer:''' An artillery unit. Its normal shot is not so useful against moving units, but can kill kernels and sockets pretty quickly. Is slow and has little health, so it needs protection. The pointer has an alternate firing mode, the NX Flag, which set a wide area ablaze for a minute, causing constant damage to all units, or buildings within it's range.</td></table>

----

===Hacker units:===
<table><td>https://springrts.com/mediawiki/images/7/7f/96x96NewHoleLow.png</td><td>'''Security Hole:''' The Hacker kernel equivalent.</td></table>

<table><td>https://springrts.com/mediawiki/images/7/70/96x96Window.png</td><td>'''Window:''' The Hacker socket equivalent.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/fb/96x96Obelisk.png</td><td>'''Obelisk:''' This building is a stationary artillery weapon, it can fire an infection shot every 40 seconds (the obelisk has a pink fire on top when it's ready to shoot) that will cover a large area in poison. The poison does a bit of damage (about 1000) and turns any enemy that dies inside the cloud into a Virus. The weapon's range is fairly limited. Best used against stationnary herds of Bits/Bugs.</td></table>

<table><td>https://springrts.com/mediawiki/images/c/c5/96x96NewTrojan.png</td><td>'''Trojan:''' This unit is your constructor as well as radar platform (needed for detecting mines and cloaked units), just like the assembler. It builds all the same stuff as the assembler, except it has the window instead of the socket and the obelisk instead of the terminal.</td></table>

<table><td>https://springrts.com/mediawiki/images/9/94/96x96Virus.png</td><td>'''Virus:''' A crappy little swarm unit. It cannot be built but is produced when killing enemy units with certain weapons. Namely, the Virus, the Worm, and the Obelisk.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/ff/96x96NewBug.png</td><td>'''Bug:''' The Hacker spam unit. The Bug is weaker than the Bit but can sense movement outside of its LOS. It has a stronger weapon and more range but cannot shoot at things behind it or through friendly units and won't take much damage before dying. The mine ability of the old bug has been removed. Instead it can now morph into the Exploit with the deploy button, or the bombard button.</td></table>

<table><td>https://springrts.com/mediawiki/images/c/c4/96x96Exploit.png</td><td>'''Exploit:''' This is the new name for the bug cannon. It's a building the Bug morphs into with the deploy or bombard command. The Exploit is a stationary artillery emplacement that does more damage the further the target is away. Even more frail than the Bug, so don't let any foe come near.</td></table>

<table><td>https://springrts.com/mediawiki/images/4/40/96x96NewWorm.png</td><td>'''Worm:''' The worm is a sneaky assassin, travelling cloacked, then surfacing only to kill many bits at once with its large area of effect weapon, which turn any slain units into virus. The worm large splash damage will damage your own units. However, it does practicaly no damage against other worms or virus. When cloacked, the worm does not automatically attack, you have to give attack orders manually. If you'd rather have your worms auto-attack even when cloacked, set autohold to off. The autohold setting of new worms is inherited from the Security Hole.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/f4/96x96DoS.png</td><td>'''Denial of Service:''' Not an artillery, but close: fire a beam that stun units. For bigger targets it'll take longer to stun them so perform a DDoS (use multiple) to stun them fast. Once the DoS stops firing the target will quickly unfreeze. It moves faster than the pointer but causes a particle trail that can be seen from far away.</td></table>

----

===Network units:===
The network faction is built around mobility, its small factories (Ports) don't produce units openly but instead increment a virtual counter (the Buffer). Packets in the Buffer can be materialized at any teleporter unit (currently that means the Port and the Connection), it's also possible to dematerialize the Packets back into the Buffer by making them enter a teleport.

<table><td>https://springrts.com/mediawiki/images/7/76/96x96Carrier.png</td><td>'''Carrier:''' The base building, like a Kernel or Security Hole.</td></table>

<table><td>https://springrts.com/mediawiki/images/4/46/96x96Port.png</td><td>'''Port:''' The production building. It puts Packets into the Buffer, to materialize them select the Dispatch command. Dispatch will send 12 Packets if available, you can hold ALT when giving the order to make the Port dispatch until the Buffer is empty.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/83/96x96Firewall.png</td><td>'''Firewall:''' This building can cover units (affects friendly units in a certain radius around the target location) in a protective shield for 20 seconds. The shield halves all damage the unit receives and throws the other half back at the attacker.</td></table>

<table><td>https://springrts.com/mediawiki/images/6/6c/96x96Gateway.png</td><td>'''Gateway:''' The constructor. It is lightly armed to help against enemy raids.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/8b/96x96Packet.png</td><td>'''Packet:''' The basic light spam unit, it's weaker in combat than both competitors but much faster.</td></table>

<table><td>https://springrts.com/mediawiki/images/2/26/96x96Connection.png</td><td>'''Connection:''' Mostly a mobile teleporter (i.e. can dispatch Packets and let them enter like a Port). The Connection has decent armor and an arc beam that can do a lot of damage to single targets and has good range. It can defeat most large units one on one but engaging Bytes will probably result in pointer fire which the Connection cannot withstand and the arc beam is not optimal for engaging swarms.</td></table>

<table><td>https://springrts.com/mediawiki/images/0/01/96x96Flow.png</td><td>'''Flow:''' An air unit. The Flow moves fairly slowly but can of course cross any terrain. It's equipped to attack light targets (spam units and fire support) but it's highly vulnerable to return fire. If you want to use them in open combat give them a meatshield and hope the enemy doesn't field long range units, Pointers, DoSes and Connections make short work of Flows if they hit.</td></table>

----

===All side Units:===

<table><td>https://springrts.com/mediawiki/images/9/98/96x96BadBlock.png</td><td>'''The Bad Block:''' A tiny wall, built by Assembler/Trojan/Gateway. Blocks small units movement. Do not block shots however. Easily removed by the Debug or simply crushing them with a Byte or Connection.</td></table>

<table><td>https://springrts.com/mediawiki/images/a/a4/96x96Mine.png</td><td>'''The Logic Bomb:''' A mine that can be built by the Assembler/Trojan/Gateway. And also launched by Bytes since Div0 2.2. It takes out Bits & Bugs in a single blow, has a decent damage radius, and doesn't chain explode. Use with care, as the blast hurts your own units too. Limited to 32.</td></table>

<table><td>https://springrts.com/mediawiki/images/3/35/96x96MineBlaster.png</td><td>'''The Debug:''' An easy way to clear an area of all mines and walls, this is a one shot weapon built by the Assembler/Trojan/Gateway.</td></table>

----

==Playing Guide for System:==


Playing Kernel Panic is fairly simple and quickly learned, but can be hard to master and can be very complex. It is recommended that beginners start with play the System faction, as they can be considered the least "gimmicky" of the factions.


One rather effective general strategy for a duel on small maps is to send three to five bits to destroy your enemy's early game units, and, to a lesser degree, for scouting purposes. This is most effective if they started with construction units, as this will likely cripple their plans for an early expansion, and gives you a slight head start. After the initial attack, if your scouting shows that your enemy started with offensive units, build a byte for defense, and place it between your Kernel and the hill. After that, build an assembler and use it to build a socket on one the three closest building locations, which should automatically start producing bits. After this, you should order your assembler to build more sockets on free spots close to it. It is crucial that all sockets' rally points are below them, as bits turning inside a socket will stall production until it is able to exit the factory. It is sometimes wise to repeat the prior process with one or two other assemblers. After this is done, construct about ten bits from your factor, and set your kernel to alternate between building bytes and pointers.


What units you build at your kernel, and what you use them for, is an important factor in winning. As buildings can't be resumed, sending in groups of bits to kill construction units creating buildings can be very effective at stopping expansion attempts. Building too many pointers, will result in them being destroyed by connections, bits and especially worms, due to their stealth. Also, bytes are easily destroyer by and pointers, and exploits. A good general purpose ratio seems to be to queue one byte and one pointer, but this will need adapting as the game develops, and depending on the enemy's play style.

Scouting is important too, as many enemies will leave their factories undefended, and knowing their build, and general unit use can help you in adapting the units you use to better fight them. Note that the Network can instantly spawn packets at any of their ports, or connections with their buffer system, meaning that all their factories should be considered defended. Single bits can be used to scout to find the enemy's current expansion attempts.

When attacking a Byte or Connection with bits, it is important to overwhelm it with large numbers of bits. For bytes, try to exploit a byte's blind spot directly under it, by moving bits into that area. If your byte is under attack, moving it backwards to keep the attacking units in it's shooting arc can help repel the attack. It is not recommended to engage a worm with bits, as it's attack will convert your bits to viruses on the worm's owner's side.


On Marble Madness, there are two main ways paths to victory. The simplest one is to control the hill and use pointers stationed on the hill to destroy the enemy's factories, and kernel. Gaining control of the hilltop will likely not be without resistance, because it requires a decent amount of time for units to reach the top of the hill, meaning most units involved will be spam units from your factories on it, and the fact that it will likely be highly contended. However, if you control it, you have a large advantage over the enemy as you can shell your opponents home base with ease. The other way is around the hill, which can be very effective if you control terrain you can use pointers to great effect. In both strategies, using pointers is the crucial factor. While they are hard to use correctly, they are game-winners as they destroy home bases and enemy units with ease.

----

==Credits:==
- Original concept by Boirunner<br>
- About all the work done by KDR_11k<br>
- Sounds by Noruas<br>
- Maintenance by zwzsg<br>
- Maps by Boirunner, Runecrafter, zwzsg, and TradeMark<br>
- Some Lua interface upgrade based of jK and trepan code<br>

----
Back to [[Games]]
[[Category:Games]]

Kernel Panic

2017-06-21T01:16:52Z

Zwzsg: 4.6 -> 4.7

<center>[http://timblokdijk.nl/spring/Kernel%20Panic/logo/kernel0_hd.png https://springrts.com/mediawiki/images/f/fc/Kernel_Panic_Alpha_Title_Half.png]</center>

==Overview:==

''For the latest news and/or assistance, try the [http://springrts.com/phpbb/viewforum.php?f=43'''KP forum'''] or go to #kp when you log onto the lobby.''

'''Kernel Panic''' is a game about computers. Systems, Hackers and Networks wage war in a matrix of DOOM! The only constraints are time and space; unlike other real time strategy games, no resource economy exists in KP.

All units are free in this game, every factory built will be spamming units at all times. You can build more factories, but only on pre-defined areas (geothermal vents). All that remains is pure strategy and tactics.

KP makes for a frantically fast-paced, action-oriented game, with a very unique graphical style.

----

==Download links:==

Current Version of Kernel Panic is 4.7

* <u>Newcomers:</u>
** If you run '''Windows''' (2000,XP,Vista,7,8,10):
*** Here you can get a complete installer:
*** http://springfiles.com/spring/game-installers/kernel-panic-installer
*** Use it to install both Spring and Kernel Panic in one go.
*** Then use the shortcuts created in your Start Menu or Desktop.
** If you run '''Linux''':
*** Read the [[SetupGuide]] how to install the Spring engine on Linux systems
*** Get and unzip that file: http://springfiles.com/spring/game-installers/kernel-panic-zip
*** Put the content of /games/ into ~/.spring/games
*** Put the content of /maps/ into ~/.spring/maps
*** Put Kernel_Panic_4.7_Launcher_Linux next to spring executable
*** Run it.
*** Alternatively, running spring directly would bring a greenish menu once ingame
*** For multiplayer or advanced options, run SpringLobby

* <u>Experienced Users:</u>
** If you have already the Spring engine (or prefer to install it yourself): Here you can get a zip with the mod file, the maps, and a tiny executable for single player frontend. Unzip into your Spring root folder: http://springfiles.com/spring/game-installers/kernel-panic-zip
** If you are certain you have all the maps and just need a quick link to the mod file itself: http://springfiles.com/spring/games/kernel-panic-mod

----

==Media:==

===Youtube Videos:===

[http://youtube.com/watch?v=doF7owZ0blk&fmt=18 http://i.ytimg.com/vi/doF7owZ0blk/default.jpg]
[http://youtube.com/watch?v=Ug1c19yaZac http://i.ytimg.com/vi/Ug1c19yaZac/default.jpg] [http://youtube.com/watch?v=GAZQhRlt5bU http://i.ytimg.com/vi/GAZQhRlt5bU/default.jpg]
[http://www.youtube.com/watch?v=3q48ys5hFtI&fmt=18 http://i.ytimg.com/vi/3q48ys5hFtI/default.jpg]

----
===Still shots:===

[http://tof.canardpc.com/view/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg http://tof.canardpc.com/preview/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg] [http://tof.canardpc.com/view/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg http://tof.canardpc.com/preview/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg] [http://tof.canardpc.com/view/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg http://tof.canardpc.com/preview/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg]

[http://tof.canardpc.com/view/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg http://tof.canardpc.com/preview/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg] [http://tof.canardpc.com/view/e5184baf-6c95-4c90-8469-b00a4f092054.jpg http://tof.canardpc.com/preview/e5184baf-6c95-4c90-8469-b00a4f092054.jpg] [http://tof.canardpc.com/view/cbe6dae0-a696-450a-bf22-236043d76511.jpg http://tof.canardpc.com/preview/cbe6dae0-a696-450a-bf22-236043d76511.jpg]

----

==License:==
Extracted from the [http://pastebin.ca/2834721 <code>Kernel_Panic_readme.txt</code>] file:

<pre>
========--------------------------------------------
License:
--------
- The content of the /games/Kernel*.sd7 is Public Domain, save:
/LuaUI/Widgets/kp_buildbar.lua
/LuaRules/Gadgets/autohold.lua
/LuaRules/Gadgets/Burrow.lua
/LuaRules/Gadgets/game_spawn.lua
which are GPL, taken from http://www.caspring.org or http://springrts.com
- The maps Marble Madness and Direct Memory Access are Public Domain
- The maps Major Madness and Speed Balls 16 Way status are unknown
- The maps Central Hub, Corrupted Core, Dual Core, Quad Core were initially CC BY-NC-SA.
Then the author removed the CC cause ( http://cpc.cx/4u3 )
- The Spring engine is GPL, available from http://spring.clan-sy.com
</pre>

----

== Game Modes:==
By default the aim is to destroy the homebase and all the minifacs of all opposing teams.
<br /><br />
Other "mod options" available are:
* '''King Of The Hill :''' Keeps control of the map center for a given time to win.
* '''O.N.S. :''' Adds shields to buildings, preventing homebase rush.
* '''Save Our Mem :''' Unit leave "leaks" that must be reclaimed.
* '''Color Wars :''' Whoever controls the most territory when timer elapse wins.
* '''Heroes of Mainframe :''' You only control a very buffed up but single unit. Best used with "Pre-placed Minifacs".
* '''Rebalancing formula :''' Let you change the stat of any units of weapons without the hassle of making a mutator.
<br />
For details, read [http://pastebin.ca/2834721 <code>Kernel_Panic_readme.txt</code>] or click [?] next to each mod option in your lobby.
----

==Units and Buildings:==

===System units:===

<table><td>https://springrts.com/mediawiki/images/5/54/96x96Kernel.png</td><td>'''The Kernel:''' You start with one of these. It can build all mobile units in the game. Has rapid auto-heal and lots of health.</td></table>

<table><td>https://springrts.com/mediawiki/images/b/b2/96x96Socket.png</td><td>'''The Socket:''' The socket is a factory which can only be built on a geothermal vent. It can solely build bits, and slower than the kernel can. It autoheals, and has a decent amount of health.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/8c/96x96Terminal.png</td><td>'''The Terminal:'''(only available in Division Zero) This is a new structure that gets placed on geovents. It can dispatch a nuclear bomber once every 90 seconds that will deal about 16000 damage to a large target area, i.e. it destroys everything except factories. It does much less damage to the kernel and hole. The bomber can strike any position on the map, there is no defense.</td></table>

<table><td>https://springrts.com/mediawiki/images/1/1e/96x96Assembler.png</td><td>'''The Assembler:''' The assembler is a construction unit. It can build sockets, but it cannot assist-build. Slow, little health. Equipped with a radar to detect mines and other cloacked units.</td></table>

<table><td>https://springrts.com/mediawiki/images/0/0a/96x96Bit.png</td><td>'''The Bit:''' Your basic attacking unit. Cheap, fast, small, not very much health. Is armed with a SPARCling laser. Can be built by a kernel or a socket.</td></table>

<table><td>https://springrts.com/mediawiki/images/e/e3/96x96Byte.png</td><td>'''The Byte:''' A large, strong, and slow attacking unit. Can holds it's own against many bits, as it has lots of health and a powerful gun. More armored when closed. Can plow through bad blocks. The byte has an alternate firing mode, the mine launcher, which throws 5 mines at the cost of much health.</td></table>

<table><td>https://springrts.com/mediawiki/images/5/51/96x96Pointer.png</td><td>'''The Pointer:''' An artillery unit. Its normal shot is not so useful against moving units, but can kill kernels and sockets pretty quickly. Is slow and has little health, so it needs protection. The pointer has an alternate firing mode, the NX Flag, which set a wide area ablaze for a minute, causing constant damage to all units, or buildings within it's range.</td></table>

----

===Hacker units:===
<table><td>https://springrts.com/mediawiki/images/7/7f/96x96NewHoleLow.png</td><td>'''Security Hole:''' The Hacker kernel equivalent.</td></table>

<table><td>https://springrts.com/mediawiki/images/7/70/96x96Window.png</td><td>'''Window:''' The Hacker socket equivalent.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/fb/96x96Obelisk.png</td><td>'''Obelisk:''' This building is a stationary artillery weapon, it can fire an infection shot every 40 seconds (the obelisk has a pink fire on top when it's ready to shoot) that will cover a large area in poison. The poison does a bit of damage (about 1000) and turns any enemy that dies inside the cloud into a Virus. The weapon's range is fairly limited. Best used against stationnary herds of Bits/Bugs.</td></table>

<table><td>https://springrts.com/mediawiki/images/c/c5/96x96NewTrojan.png</td><td>'''Trojan:''' This unit is your constructor as well as radar platform (needed for detecting mines and cloaked units), just like the assembler. It builds all the same stuff as the assembler, except it has the window instead of the socket and the obelisk instead of the terminal.</td></table>

<table><td>https://springrts.com/mediawiki/images/9/94/96x96Virus.png</td><td>'''Virus:''' A crappy little swarm unit. It cannot be built but is produced when killing enemy units with certain weapons. Namely, the Virus, the Worm, and the Obelisk.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/ff/96x96NewBug.png</td><td>'''Bug:''' The Hacker spam unit. The Bug is weaker than the Bit but can sense movement outside of its LOS. It has a stronger weapon and more range but cannot shoot at things behind it or through friendly units and won't take much damage before dying. The mine ability of the old bug has been removed. Instead it can now morph into the Exploit with the deploy button, or the bombard button.</td></table>

<table><td>https://springrts.com/mediawiki/images/c/c4/96x96Exploit.png</td><td>'''Exploit:''' This is the new name for the bug cannon. It's a building the Bug morphs into with the deploy or bombard command. The Exploit is a stationary artillery emplacement that does more damage the further the target is away. Even more frail than the Bug, so don't let any foe come near.</td></table>

<table><td>https://springrts.com/mediawiki/images/4/40/96x96NewWorm.png</td><td>'''Worm:''' The worm is a sneaky assassin, travelling cloacked, then surfacing only to kill many bits at once with its large area of effect weapon, which turn any slain units into virus. The worm large splash damage will damage your own units. However, it does practicaly no damage against other worms or virus. When cloacked, the worm does not automatically attack, you have to give attack orders manually. If you'd rather have your worms auto-attack even when cloacked, set autohold to off. The autohold setting of new worms is inherited from the Security Hole.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/f4/96x96DoS.png</td><td>'''Denial of Service:''' Not an artillery, but close: fire a beam that stun units. For bigger targets it'll take longer to stun them so perform a DDoS (use multiple) to stun them fast. Once the DoS stops firing the target will quickly unfreeze. It moves faster than the pointer but causes a particle trail that can be seen from far away.</td></table>

----

===Network units:===
The network faction is built around mobility, its small factories (Ports) don't produce units openly but instead increment a virtual counter (the Buffer). Packets in the Buffer can be materialized at any teleporter unit (currently that means the Port and the Connection), it's also possible to dematerialize the Packets back into the Buffer by making them enter a teleport.

<table><td>https://springrts.com/mediawiki/images/7/76/96x96Carrier.png</td><td>'''Carrier:''' The base building, like a Kernel or Security Hole.</td></table>

<table><td>https://springrts.com/mediawiki/images/4/46/96x96Port.png</td><td>'''Port:''' The production building. It puts Packets into the Buffer, to materialize them select the Dispatch command. Dispatch will send 12 Packets if available, you can hold ALT when giving the order to make the Port dispatch until the Buffer is empty.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/83/96x96Firewall.png</td><td>'''Firewall:''' This building can cover units (affects friendly units in a certain radius around the target location) in a protective shield for 20 seconds. The shield halves all damage the unit receives and throws the other half back at the attacker.</td></table>

<table><td>https://springrts.com/mediawiki/images/6/6c/96x96Gateway.png</td><td>'''Gateway:''' The constructor. It is lightly armed to help against enemy raids.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/8b/96x96Packet.png</td><td>'''Packet:''' The basic light spam unit, it's weaker in combat than both competitors but much faster.</td></table>

<table><td>https://springrts.com/mediawiki/images/2/26/96x96Connection.png</td><td>'''Connection:''' Mostly a mobile teleporter (i.e. can dispatch Packets and let them enter like a Port). The Connection has decent armor and an arc beam that can do a lot of damage to single targets and has good range. It can defeat most large units one on one but engaging Bytes will probably result in pointer fire which the Connection cannot withstand and the arc beam is not optimal for engaging swarms.</td></table>

<table><td>https://springrts.com/mediawiki/images/0/01/96x96Flow.png</td><td>'''Flow:''' An air unit. The Flow moves fairly slowly but can of course cross any terrain. It's equipped to attack light targets (spam units and fire support) but it's highly vulnerable to return fire. If you want to use them in open combat give them a meatshield and hope the enemy doesn't field long range units, Pointers, DoSes and Connections make short work of Flows if they hit.</td></table>

----

===All side Units:===

<table><td>https://springrts.com/mediawiki/images/9/98/96x96BadBlock.png</td><td>'''The Bad Block:''' A tiny wall, built by Assembler/Trojan/Gateway. Blocks small units movement. Do not block shots however. Easily removed by the Debug or simply crushing them with a Byte or Connection.</td></table>

<table><td>https://springrts.com/mediawiki/images/a/a4/96x96Mine.png</td><td>'''The Logic Bomb:''' A mine that can be built by the Assembler/Trojan/Gateway. And also launched by Bytes since Div0 2.2. It takes out Bits & Bugs in a single blow, has a decent damage radius, and doesn't chain explode. Use with care, as the blast hurts your own units too. Limited to 32.</td></table>

<table><td>https://springrts.com/mediawiki/images/3/35/96x96MineBlaster.png</td><td>'''The Debug:''' An easy way to clear an area of all mines and walls, this is a one shot weapon built by the Assembler/Trojan/Gateway.</td></table>

----

==Playing Guide for System:==


Playing Kernel Panic is fairly simple and quickly learned, but can be hard to master and can be very complex. It is recommended that beginners start with play the System faction, as they can be considered the least "gimmicky" of the factions.


One rather effective general strategy for a duel on small maps is to send three to five bits to destroy your enemy's early game units, and, to a lesser degree, for scouting purposes. This is most effective if they started with construction units, as this will likely cripple their plans for an early expansion, and gives you a slight head start. After the initial attack, if your scouting shows that your enemy started with offensive units, build a byte for defense, and place it between your Kernel and the hill. After that, build an assembler and use it to build a socket on one the three closest building locations, which should automatically start producing bits. After this, you should order your assembler to build more sockets on free spots close to it. It is crucial that all sockets' rally points are below them, as bits turning inside a socket will stall production until it is able to exit the factory. It is sometimes wise to repeat the prior process with one or two other assemblers. After this is done, construct about ten bits from your factor, and set your kernel to alternate between building bytes and pointers.


What units you build at your kernel, and what you use them for, is an important factor in winning. As buildings can't be resumed, sending in groups of bits to kill construction units creating buildings can be very effective at stopping expansion attempts. Building too many pointers, will result in them being destroyed by connections, bits and especially worms, due to their stealth. Also, bytes are easily destroyer by and pointers, and exploits. A good general purpose ratio seems to be to queue one byte and one pointer, but this will need adapting as the game develops, and depending on the enemy's play style.

Scouting is important too, as many enemies will leave their factories undefended, and knowing their build, and general unit use can help you in adapting the units you use to better fight them. Note that the Network can instantly spawn packets at any of their ports, or connections with their buffer system, meaning that all their factories should be considered defended. Single bits can be used to scout to find the enemy's current expansion attempts.

When attacking a Byte or Connection with bits, it is important to overwhelm it with large numbers of bits. For bytes, try to exploit a byte's blind spot directly under it, by moving bits into that area. If your byte is under attack, moving it backwards to keep the attacking units in it's shooting arc can help repel the attack. It is not recommended to engage a worm with bits, as it's attack will convert your bits to viruses on the worm's owner's side.


On Marble Madness, there are two main ways paths to victory. The simplest one is to control the hill and use pointers stationed on the hill to destroy the enemy's factories, and kernel. Gaining control of the hilltop will likely not be without resistance, because it requires a decent amount of time for units to reach the top of the hill, meaning most units involved will be spam units from your factories on it, and the fact that it will likely be highly contended. However, if you control it, you have a large advantage over the enemy as you can shell your opponents home base with ease. The other way is around the hill, which can be very effective if you control terrain you can use pointers to great effect. In both strategies, using pointers is the crucial factor. While they are hard to use correctly, they are game-winners as they destroy home bases and enemy units with ease.

----

==Credits:==
- Original concept by Boirunner<br>
- About all the work done by KDR_11k<br>
- Sounds by Noruas<br>
- Maintenance by zwzsg<br>
- Maps by Boirunner, Runecrafter, zwzsg, and TradeMark<br>
- Some LUA interface upgrade based of jK and trepan code<br>

----
Back to [[Games]]
[[Category:Games]]

Kernel Panic

2017-06-20T18:50:36Z

Zwzsg: Restored images

<center>[http://timblokdijk.nl/spring/Kernel%20Panic/logo/kernel0_hd.png https://springrts.com/mediawiki/images/f/fc/Kernel_Panic_Alpha_Title_Half.png]</center>

==Overview:==

''For the latest news and/or assistance, try the [http://springrts.com/phpbb/viewforum.php?f=43'''KP forum'''] or go to #kp when you log onto the lobby.''

'''Kernel Panic''' is a game about computers. Systems, Hackers and Networks wage war in a matrix of DOOM! The only constraints are time and space; unlike other real time strategy games, no resource economy exists in KP.

All units are free in this game, every factory built will be spamming units at all times. You can build more factories, but only on pre-defined areas (geothermal vents). All that remains is pure strategy and tactics.

KP makes for a frantically fast-paced, action-oriented game, with a very unique graphical style.

----

==Download links:==

Current Version of Kernel Panic is 4.6

* <u>Newcomers:</u>
** If you run '''Windows''' (2000,XP,Vista,7):
*** Here you can get a complete installer:
*** http://springfiles.com/spring/game-installers/kernel-panic-installer
*** Use it to install both Spring and Kernel Panic in one go.
*** Then use the shortcuts created in your Start Menu or Desktop.
** If you run '''Linux''':
*** Read the [[SetupGuide]] how to install the Spring engine on Linux systems
*** Get and unzip that file: http://springfiles.com/spring/game-installers/kernel-panic-zip
*** Put the content of /games/ into ~/.spring/games
*** Put the content of /maps/ into ~/.spring/maps
*** Discard the rest.
*** Run Spring directly, a greenish menu should pop up.
*** Click skirmish, duel, easy, run.
*** For multiplayer or advanced options, run SpringLobby

* <u>Experienced Users:</u>
** If you have already the Spring engine (or prefer to install it yourself): Here you can get a zip with the mod file, the maps, and a tiny exe for single player frontend. Unzip into your Spring root folder: http://springfiles.com/spring/game-installers/kernel-panic-zip
** If you are certain you have all the maps and just need a quick link to the mod file itself: http://springfiles.com/spring/games/kernel-panic-mod

----

==Media:==

===Youtube Videos:===

[http://youtube.com/watch?v=doF7owZ0blk&fmt=18 http://i.ytimg.com/vi/doF7owZ0blk/default.jpg]
[http://youtube.com/watch?v=Ug1c19yaZac http://i.ytimg.com/vi/Ug1c19yaZac/default.jpg] [http://youtube.com/watch?v=GAZQhRlt5bU http://i.ytimg.com/vi/GAZQhRlt5bU/default.jpg]
[http://www.youtube.com/watch?v=3q48ys5hFtI&fmt=18 http://i.ytimg.com/vi/3q48ys5hFtI/default.jpg]

----
===Still shots:===

[http://tof.canardpc.com/view/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg http://tof.canardpc.com/preview/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg] [http://tof.canardpc.com/view/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg http://tof.canardpc.com/preview/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg] [http://tof.canardpc.com/view/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg http://tof.canardpc.com/preview/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg]

[http://tof.canardpc.com/view/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg http://tof.canardpc.com/preview/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg] [http://tof.canardpc.com/view/e5184baf-6c95-4c90-8469-b00a4f092054.jpg http://tof.canardpc.com/preview/e5184baf-6c95-4c90-8469-b00a4f092054.jpg] [http://tof.canardpc.com/view/cbe6dae0-a696-450a-bf22-236043d76511.jpg http://tof.canardpc.com/preview/cbe6dae0-a696-450a-bf22-236043d76511.jpg]

----

==License:==
Extracted from the [http://pastebin.ca/2834721 <code>Kernel_Panic_readme.txt</code>] file:

<pre>
========--------------------------------------------
License:
--------
- The content of the /games/Kernel*.sd7 is Public Domain, save:
/LuaUI/Widgets/kp_buildbar.lua
/LuaRules/Gadgets/autohold.lua
/LuaRules/Gadgets/Burrow.lua
/LuaRules/Gadgets/game_spawn.lua
which are GPL, taken from http://www.caspring.org or http://springrts.com
- The maps Marble Madness and Direct Memory Access are Public Domain
- The maps Major Madness and Speed Balls 16 Way status are unknown
- The maps Central Hub, Corrupted Core, Dual Core, Quad Core were initially CC BY-NC-SA.
Then the author removed the CC cause ( http://cpc.cx/4u3 )
- The Spring engine is GPL, available from http://spring.clan-sy.com
</pre>

----

== Game Modes:==
By default the aim is to destroy the homebase and all the minifacs of all opposing teams.
<br /><br />
Other "mod options" available are:
* '''King Of The Hill :''' Keeps control of the map center for a given time to win.
* '''O.N.S. :''' Adds shields to buildings, preventing homebase rush.
* '''Save Our Mem :''' Unit leave "leaks" that must be reclaimed.
* '''Color Wars :''' Whoever controls the most territory when timer elapse wins.
* '''Heroes of Mainframe :''' You only control a very buffed up but single unit. Best used with "Pre-placed Minifacs".
* '''Rebalancing formula :''' Let you change the stat of any units of weapons without the hassle of making a mutator.
<br />
For details, read [http://pastebin.ca/2834721 <code>Kernel_Panic_readme.txt</code>] or click [?] next to each mod option in your lobby.
----

==Units and Buildings:==

===System units:===

<table><td>https://springrts.com/mediawiki/images/5/54/96x96Kernel.png</td><td>'''The Kernel:''' You start with one of these. It can build all mobile units in the game. Has rapid auto-heal and lots of health.</td></table>

<table><td>https://springrts.com/mediawiki/images/b/b2/96x96Socket.png</td><td>'''The Socket:''' The socket is a factory which can only be built on a geothermal vent. It can solely build bits, and slower than the kernel can. It autoheals, and has a decent amount of health.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/8c/96x96Terminal.png</td><td>'''The Terminal:'''(only available in Division Zero) This is a new structure that gets placed on geovents. It can dispatch a nuclear bomber once every 90 seconds that will deal about 16000 damage to a large target area, i.e. it destroys everything except factories. It does much less damage to the kernel and hole. The bomber can strike any position on the map, there is no defense.</td></table>

<table><td>https://springrts.com/mediawiki/images/1/1e/96x96Assembler.png</td><td>'''The Assembler:''' The assembler is a construction unit. It can build sockets, but it cannot assist-build. Slow, little health. Equipped with a radar to detect mines and other cloacked units.</td></table>

<table><td>https://springrts.com/mediawiki/images/0/0a/96x96Bit.png</td><td>'''The Bit:''' Your basic attacking unit. Cheap, fast, small, not very much health. Is armed with a SPARCling laser. Can be built by a kernel or a socket.</td></table>

<table><td>https://springrts.com/mediawiki/images/e/e3/96x96Byte.png</td><td>'''The Byte:''' A large, strong, and slow attacking unit. Can holds it's own against many bits, as it has lots of health and a powerful gun. More armored when closed. Can plow through bad blocks. The byte has an alternate firing mode, the mine launcher, which throws 5 mines at the cost of much health.</td></table>

<table><td>https://springrts.com/mediawiki/images/5/51/96x96Pointer.png</td><td>'''The Pointer:''' An artillery unit. Its normal shot is not so useful against moving units, but can kill kernels and sockets pretty quickly. Is slow and has little health, so it needs protection. The pointer has an alternate firing mode, the NX Flag, which set a wide area ablaze for a minute, causing constant damage to all units, or buildings within it's range.</td></table>

----

===Hacker units:===
<table><td>https://springrts.com/mediawiki/images/7/7f/96x96NewHoleLow.png</td><td>'''Security Hole:''' The Hacker kernel equivalent.</td></table>

<table><td>https://springrts.com/mediawiki/images/7/70/96x96Window.png</td><td>'''Window:''' The Hacker socket equivalent.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/fb/96x96Obelisk.png</td><td>'''Obelisk:''' This building is a stationary artillery weapon, it can fire an infection shot every 40 seconds (the obelisk has a pink fire on top when it's ready to shoot) that will cover a large area in poison. The poison does a bit of damage (about 1000) and turns any enemy that dies inside the cloud into a Virus. The weapon's range is fairly limited. Best used against stationnary herds of Bits/Bugs.</td></table>

<table><td>https://springrts.com/mediawiki/images/c/c5/96x96NewTrojan.png</td><td>'''Trojan:''' This unit is your constructor as well as radar platform (needed for detecting mines and cloaked units), just like the assembler. It builds all the same stuff as the assembler, except it has the window instead of the socket and the obelisk instead of the terminal.</td></table>

<table><td>https://springrts.com/mediawiki/images/9/94/96x96Virus.png</td><td>'''Virus:''' A crappy little swarm unit. It cannot be built but is produced when killing enemy units with certain weapons. Namely, the Virus, the Worm, and the Obelisk.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/ff/96x96NewBug.png</td><td>'''Bug:''' The Hacker spam unit. The Bug is weaker than the Bit but can sense movement outside of its LOS. It has a stronger weapon and more range but cannot shoot at things behind it or through friendly units and won't take much damage before dying. The mine ability of the old bug has been removed. Instead it can now morph into the Exploit with the deploy button, or the bombard button.</td></table>

<table><td>https://springrts.com/mediawiki/images/c/c4/96x96Exploit.png</td><td>'''Exploit:''' This is the new name for the bug cannon. It's a building the Bug morphs into with the deploy or bombard command. The Exploit is a stationary artillery emplacement that does more damage the further the target is away. Even more frail than the Bug, so don't let any foe come near.</td></table>

<table><td>https://springrts.com/mediawiki/images/4/40/96x96NewWorm.png</td><td>'''Worm:''' The worm is a sneaky assassin, travelling cloacked, then surfacing only to kill many bits at once with its large area of effect weapon, which turn any slain units into virus. The worm large splash damage will damage your own units. However, it does practicaly no damage against other worms or virus. When cloacked, the worm does not automatically attack, you have to give attack orders manually. If you'd rather have your worms auto-attack even when cloacked, set autohold to off. The autohold setting of new worms is inherited from the Security Hole.</td></table>

<table><td>https://springrts.com/mediawiki/images/f/f4/96x96DoS.png</td><td>'''Denial of Service:''' Not an artillery, but close: fire a beam that stun units. For bigger targets it'll take longer to stun them so perform a DDoS (use multiple) to stun them fast. Once the DoS stops firing the target will quickly unfreeze. It moves faster than the pointer but causes a particle trail that can be seen from far away.</td></table>

----

===Network units:===
The network faction is built around mobility, its small factories (Ports) don't produce units openly but instead increment a virtual counter (the Buffer). Packets in the Buffer can be materialized at any teleporter unit (currently that means the Port and the Connection), it's also possible to dematerialize the Packets back into the Buffer by making them enter a teleport.

<table><td>https://springrts.com/mediawiki/images/7/76/96x96Carrier.png</td><td>'''Carrier:''' The base building, like a Kernel or Security Hole.</td></table>

<table><td>https://springrts.com/mediawiki/images/4/46/96x96Port.png</td><td>'''Port:''' The production building. It puts Packets into the Buffer, to materialize them select the Dispatch command. Dispatch will send 12 Packets if available, you can hold ALT when giving the order to make the Port dispatch until the Buffer is empty.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/83/96x96Firewall.png</td><td>'''Firewall:''' This building can cover units (affects friendly units in a certain radius around the target location) in a protective shield for 20 seconds. The shield halves all damage the unit receives and throws the other half back at the attacker.</td></table>

<table><td>https://springrts.com/mediawiki/images/6/6c/96x96Gateway.png</td><td>'''Gateway:''' The constructor. It is lightly armed to help against enemy raids.</td></table>

<table><td>https://springrts.com/mediawiki/images/8/8b/96x96Packet.png</td><td>'''Packet:''' The basic light spam unit, it's weaker in combat than both competitors but much faster.</td></table>

<table><td>https://springrts.com/mediawiki/images/2/26/96x96Connection.png</td><td>'''Connection:''' Mostly a mobile teleporter (i.e. can dispatch Packets and let them enter like a Port). The Connection has decent armor and an arc beam that can do a lot of damage to single targets and has good range. It can defeat most large units one on one but engaging Bytes will probably result in pointer fire which the Connection cannot withstand and the arc beam is not optimal for engaging swarms.</td></table>

<table><td>https://springrts.com/mediawiki/images/0/01/96x96Flow.png</td><td>'''Flow:''' An air unit. The Flow moves fairly slowly but can of course cross any terrain. It's equipped to attack light targets (spam units and fire support) but it's highly vulnerable to return fire. If you want to use them in open combat give them a meatshield and hope the enemy doesn't field long range units, Pointers, DoSes and Connections make short work of Flows if they hit.</td></table>

----

===All side Units:===

<table><td>https://springrts.com/mediawiki/images/9/98/96x96BadBlock.png</td><td>'''The Bad Block:''' A tiny wall, built by Assembler/Trojan/Gateway. Blocks small units movement. Do not block shots however. Easily removed by the Debug or simply crushing them with a Byte or Connection.</td></table>

<table><td>https://springrts.com/mediawiki/images/a/a4/96x96Mine.png</td><td>'''The Logic Bomb:''' A mine that can be built by the Assembler/Trojan/Gateway. And also launched by Bytes since Div0 2.2. It takes out Bits & Bugs in a single blow, has a decent damage radius, and doesn't chain explode. Use with care, as the blast hurts your own units too. Limited to 32.</td></table>

<table><td>https://springrts.com/mediawiki/images/3/35/96x96MineBlaster.png</td><td>'''The Debug:''' An easy way to clear an area of all mines and walls, this is a one shot weapon built by the Assembler/Trojan/Gateway.</td></table>

----

==Playing Guide for System:==


Playing Kernel Panic is fairly simple and quickly learned, but can be hard to master and can be very complex. It is recommended that beginners start with play the System faction, as they can be considered the least "gimmicky" of the factions.


One rather effective general strategy for a duel on small maps is to send three to five bits to destroy your enemy's early game units, and, to a lesser degree, for scouting purposes. This is most effective if they started with construction units, as this will likely cripple their plans for an early expansion, and gives you a slight head start. After the initial attack, if your scouting shows that your enemy started with offensive units, build a byte for defense, and place it between your Kernel and the hill. After that, build an assembler and use it to build a socket on one the three closest building locations, which should automatically start producing bits. After this, you should order your assembler to build more sockets on free spots close to it. It is crucial that all sockets' rally points are below them, as bits turning inside a socket will stall production until it is able to exit the factory. It is sometimes wise to repeat the prior process with one or two other assemblers. After this is done, construct about ten bits from your factor, and set your kernel to alternate between building bytes and pointers.


What units you build at your kernel, and what you use them for, is an important factor in winning. As buildings can't be resumed, sending in groups of bits to kill construction units creating buildings can be very effective at stopping expansion attempts. Building too many pointers, will result in them being destroyed by connections, bits and especially worms, due to their stealth. Also, bytes are easily destroyer by and pointers, and exploits. A good general purpose ratio seems to be to queue one byte and one pointer, but this will need adapting as the game develops, and depending on the enemy's play style.

Scouting is important too, as many enemies will leave their factories undefended, and knowing their build, and general unit use can help you in adapting the units you use to better fight them. Note that the Network can instantly spawn packets at any of their ports, or connections with their buffer system, meaning that all their factories should be considered defended. Single bits can be used to scout to find the enemy's current expansion attempts.

When attacking a Byte or Connection with bits, it is important to overwhelm it with large numbers of bits. For bytes, try to exploit a byte's blind spot directly under it, by moving bits into that area. If your byte is under attack, moving it backwards to keep the attacking units in it's shooting arc can help repel the attack. It is not recommended to engage a worm with bits, as it's attack will convert your bits to viruses on the worm's owner's side.


On Marble Madness, there are two main ways paths to victory. The simplest one is to control the hill and use pointers stationed on the hill to destroy the enemy's factories, and kernel. Gaining control of the hilltop will likely not be without resistance, because it requires a decent amount of time for units to reach the top of the hill, meaning most units involved will be spam units from your factories on it, and the fact that it will likely be highly contended. However, if you control it, you have a large advantage over the enemy as you can shell your opponents home base with ease. The other way is around the hill, which can be very effective if you control terrain you can use pointers to great effect. In both strategies, using pointers is the crucial factor. While they are hard to use correctly, they are game-winners as they destroy home bases and enemy units with ease.

----

==Credits:==
- Original concept by Boirunner<br>
- About all the work done by KDR_11k<br>
- Sounds by Noruas<br>
- Minor edits by zwzsg<br>
- Maps by Boirunner, Runecrafter, zwzsg, and TradeMark<br>
- Some LUA interface upgrade based of jK and trepan code<br>

----
Back to [[Games]]
[[Category:Games]]

File:96x96Window.png

2017-06-20T18:36:02Z

Zwzsg: Kernel Panic - Hacker Windows

Kernel Panic - Hacker Windows

File:96x96Virus.png

2017-06-20T18:35:42Z

Zwzsg: Kernel Panic - Hacker Virus

Kernel Panic - Hacker Virus

File:96x96Terminal.png

2017-06-20T18:35:25Z

Zwzsg: Kernel Panic - System Terminal

Kernel Panic - System Terminal

File:96x96Socket.png

2017-06-20T18:35:11Z

Zwzsg: Kernel Panic - System Socket

Kernel Panic - System Socket

File:96x96Port.png

2017-06-20T18:34:56Z

Zwzsg: Kernel Panic - Network Port

Kernel Panic - Network Port

File:96x96Pointer.png

2017-06-20T18:34:29Z

Zwzsg: Kernel Panic - System Pointer

Kernel Panic - System Pointer

File:96x96Packet.png

2017-06-20T18:34:13Z

Zwzsg: Kernel Panic - Network Packet

Kernel Panic - Network Packet

File:96x96Obelisk.png

2017-06-20T18:34:00Z

Zwzsg: Kernel Panic - Hacker Obelisk

Kernel Panic - Hacker Obelisk

File:96x96NewWorm.png

2017-06-20T18:33:46Z

Zwzsg: Kernel Panic - Hacker Worm

Kernel Panic - Hacker Worm

File:96x96NewTrojan.png

2017-06-20T18:33:33Z

Zwzsg: Kernel Panic - Hacker Trojan

Kernel Panic - Hacker Trojan

File:96x96NewHoleLow.png

2017-06-20T18:33:18Z

Zwzsg: Kernel Panic - Hacker Hole

Kernel Panic - Hacker Hole

File:96x96NewHoleHigh.png

2017-06-20T18:32:47Z

Zwzsg: Kernel Panic - Hacker Hole

Kernel Panic - Hacker Hole

File:96x96NewBug.png

2017-06-20T18:32:29Z

Zwzsg: Kernel Panic - Hacker Bug

Kernel Panic - Hacker Bug

File:96x96MineBlaster.png

2017-06-20T18:32:16Z

Zwzsg: Kernel Panic - MineBlaster

Kernel Panic - MineBlaster

File:96x96Mine.png

2017-06-20T18:32:01Z

Zwzsg: Kernel Panic - Mine

Kernel Panic - Mine

File:96x96Kernel.png

2017-06-20T18:31:42Z

Zwzsg: Kernel Panic - System Kernel

Kernel Panic - System Kernel

File:96x96Gateway.png

2017-06-20T18:31:27Z

Zwzsg: Kernel Panic - Network Gateway

Kernel Panic - Network Gateway

File:96x96Flow.png

2017-06-20T18:31:12Z

Zwzsg: Kernel Panic - Network Flow

Kernel Panic - Network Flow

File:96x96Firewall.png

2017-06-20T18:30:49Z

Zwzsg: Kernel Panic - Network Firewall

Kernel Panic - Network Firewall

File:96x96Exploit.png

2017-06-20T18:30:20Z

Zwzsg: Kernel Panic - Hacker Exploit

Kernel Panic - Hacker Exploit

File:96x96DoS.png

2017-06-20T18:30:02Z

Zwzsg: Kernel Panic - Hacker DoS

Kernel Panic - Hacker DoS

File:96x96Connection.png

2017-06-20T18:29:32Z

Zwzsg: Kernel Panic - Network Connection

Kernel Panic - Network Connection

File:96x96Carrier.png

2017-06-20T18:29:08Z

Zwzsg: Kernel Panic - Network Carrier

Kernel Panic - Network Carrier

File:96x96Byte.png

2017-06-20T18:28:46Z

Zwzsg: Kernel Panic - System Byte

Kernel Panic - System Byte

File:96x96Bit.png

2017-06-20T18:28:30Z

Zwzsg: Kernel Panic - System Bit

Kernel Panic - System Bit

File:96x96BadBlock.png

2017-06-20T18:28:07Z

Zwzsg: Kernel Panic - Bad Block

Kernel Panic - Bad Block

File:96x96Assembler.png

2017-06-20T18:27:16Z

Zwzsg: Kernel Panic - System Assembler

Kernel Panic - System Assembler

File:Kernel Panic Alpha Title Half.png

2017-06-20T18:13:01Z

Zwzsg: Kernel Panic logo, by Tim Blokdijk, from https://springrts.com/phpbb/viewtopic.php?t=23663 edited to change huge, add alpha transparency, resize.

Kernel Panic logo, by Tim Blokdijk, from https://springrts.com/phpbb/viewtopic.php?t=23663 edited to change huge, add alpha transparency, resize.

Lua:Callins

2015-11-03T23:48:04Z

Zwzsg:

= Lua Callins =
This page is future looking to unified widget/gadget (aka "addon") handler, which may yet be some way off, c.f. the [https://github.com/spring/spring/blob/ebb704e008f6ea645947d07be1cfcc272af0428f/doc/changelog.txt#L71 changelog].

For now, to use these addons in a widget, replace addon with widget and, for a gadget, replace addon with gadget. For example,
<code><pre>
function widget:UnitCreated(unitID, unitDefID, unitTeam, builderID)
...
end
</pre></code>

Some functions may differ between (synced) gadget and widgets; those are in the [[#Synced_-_Unsynced_Shared]] section. Essentially the reason is that all information should be available to synced (game logic controlling) gadgets, but restricted to unsynced gadget/widget (e.g. information about an enemy unit only detected via radar and not yet in LOS). In such cases the full (synced) param list is documented.

== Common ==
{{LuaCallin
|name = Initialize
|params =
|return = none
|description = Called when the addon is (re)loaded.
}}

{{LuaCallin
|name = Shutdown
|params =
|return = none
|description = Called when the addon or the game is shutdown.
}}

== Unsynced Only ==

{{LuaCallin
|name = DefaultCommand
|params = type, id
|return = number cmdID
|description = Used to set the default command when a unit is selected. First parameter is the type of the object pointed at (either "unit or "feature") and the second is its unitID or featureID respectively.
}}

{{LuaCallin
|name = CommandNotify
|params = cmdID, cmdParams, cmdOptions
|return = bool removeCmd
|description = Called when a command is issued. Returning <code>true</code> deletes the command and does not send it through the network.
}}

{{LuaCallin
|name = WorldTooltip
|params = ttType, data1, data2, data3
|return = string newTooltip
|description = The parameters can be <code>"unit"</code>, <code>unitID</code>; <code>"feature"</code>, <code>featureID</code>; <code>"ground"</code>, <code>posX</code>, <code>posY</code>, <code>posZ</code> or <code>"selection"</code>.
}}

{{LuaCallin
|name = UnsyncedHeightMapUpdate
|params = ???
|return = none
|description = Called when the unsynced copy of the height-map is altered.
}}

{{LuaCallin
|name = GameProgress
|params = serverFrameNum
|return = none
|description = Called every 60 frames, calculating delta between GameFrame and GameProgress. Can give an ETA about catching up with simulation for mid-game join players.
}}

{{LuaCallin
|name = GameSetup
|params = state, ready, playerStates
|return = bool success, bool newReady
|description = ???
}}

{{LuaCallin
|name = SunChanged
|params = ???
|return = none
|description = ???
}}

{{LuaCallin
|name = AddConsoleLine
|params = msg, priority
|return = none
|description = Called when text is entered into the console (e.g. Spring.Echo).
}}

{{LuaCallin
|name = RecvSkirmishAIMessage
|params = aiTeam, dataStr
|return = ???
|description = ???
}}

{{LuaCallin
|name = RecvFromSynced
|params = ...
|return = none
|description = Receives data sent via [[Lua_System#Synced|SendToUnsynced]] callout.
}}

{{LuaCallin
|name = Save
|params = zip
|return = none
|description = Called when a chat command '/save' or '/savegame' is received. The single argument is a userdatum representing the savegame zip file. See [[Lua_SaveLoad#Save_.28_zip_.29_-.3E_nil|Lua_SaveLoad]].
}}

{{LuaCallin
|name = LoadProgress
|params = message, replaceLastLine
|return = none
|description = Only available to LuaIntro.
}}

{{LuaCallin
|name = GroupChanged
|params = groupID
|return = none
|description = Called when a unit is added to or removed from a control group. Currently implemented for widgets only.
}}

{{LuaCallin
|name = ConfigureLayout
|params = ???
|return = ???
|description = ???
}}

=== Input ===
{{LuaCallin
|name = IsAbove
|params = x, y
|return = bool isAbove
|description = Called every Update. Must return <code>true</code> for <code>Mouse*</code> events and <code>GetToolTip</code> to be called.
}}

{{LuaCallin
|name = GetTooltip
|params = x, y
|return = string tooltip
|description = Called when <code>IsAbove</code> returns true.
}}

{{LuaCallin
|name = KeyPress
|params = key, mods, isRepeat
|return = bool becomeOwner
|description = Called repeatedly when a key is pressed down. If you want an action to occur only once check for <code>isRepeat == false</code>. The <code>mods</code> parameter is a table, with keys <code>alt</code>, <code>ctrl</code>, <code>meta</code> and <code>shift</code> each having a boolean value. Return <code>true</code> if you don't want other callins or the engine to also receive this keypress.
}}

{{LuaCallin
|name = KeyRelease
|params = key
|return = bool
|description = Called when the key is released.
}}

{{LuaCallin
|name = TextInput
|params = utf8char
|return = none
|description = Called whenever a key press results in text input. Introduced in 97.0.
}}

{{LuaCallin
|name = JoystickEvent
|params = ???
|return = none
|description = ???
}}

{{LuaCallin
|name = MousePress
|params = x, y, button
|return = bool becomeMouseOwner
|description = Called when a mouse button is pressed. The <code>button</code> parameter supports up to 7 buttons. Must return <code>true</code> for <code>MouseRelease</code> and other functions to be called.
}}

{{LuaCallin
|name = MouseRelease
|params = x, y, button
|return = bool becomeMouseOwner
|description = Called when a mouse button is released. Please note that in order to have Spring call <code>MouseRelease</code>, you need to have a <code>MousePress</code> call-in in the same addon that returns <code>true</code>.
}}

{{LuaCallin
|name = MouseWheel
|params = up, value
|return = none
|description = Called when the mouse wheel is moved. The parameters indicate the direction and amount of travel.
}}

{{LuaCallin
|name = MouseMove
|params = x, y, dx, dy, button
|return = none
|description = Called when the mouse is moved. The <code>dx</code> and <code>dy</code> parameters indicate the distance travelled, whereas the first two indicate the final position.
}}

=== Players ===
{{LuaCallin
|name = PlayerChanged
|params = playerID
|return = none
|description = Called whenever a player's status changes e.g. becoming a spectator.
}}

{{LuaCallin
|name = PlayerAdded
|params = playerID
|return = none
|description = Called whenever a new player joins the game.
}}

{{LuaCallin
|name = PlayerRemoved
|params = playerID, reason
|return = none
|description = Called whenever a player is removed from the game.
}}

=== Drawing ===

{{LuaCallin
|name = ViewResize
|params = viewSizeX, viewSizeY
|return = none
|description = Called whenever the window is resized.
}}

{{LuaCallin
|name = Update
|params = dt
|return = none
|description = Called for every draw frame. The parameter is the time since the last update. Perform calculations in here and only drawing in Draw* callins.}}

Inside the Draw* functions, you can use the [[Lua_OpenGL_Api | Lua OpenGL Api]] to draw graphics.

{{LuaCallin
|name = DrawGenesis
|params =
|return = none
|description = Doesn't render to screen! Use this callin to update textures, shaders, etc.
}}

{{LuaCallin
|name = DrawWorldPreUnit
|params =
|return = none
|description = Spring draws units, features, some water types, cloaked units, and the sun.
}}

{{LuaCallin
|name = DrawWorld
|params =
|return = none
|description = Spring draws command queues, 'map stuff', and map marks.
}}

{{LuaCallin
|name = DrawWorldShadow
|params =
|return = none
|description = ???
}}

{{LuaCallin
|name = DrawWorldReflection
|params =
|return = none
|description = ???
}}

{{LuaCallin
|name = DrawWorldRefraction
|params =
|return = none
|description = ???
}}

{{LuaCallin
|name = DrawScreen
|params =
|return = none
|description = ???
}}

{{LuaCallin
|name = DrawScreenEffects
|params = vsx, vsy
|return = none
|description = Where <code>vsx</code>, <code>vsy</code> are screen coordinates.
}}

{{LuaCallin
|name = DrawLoadScreen
|params =
|return = none
|description = {{new|95.0}} Only available to LuaIntro, draws custom load screens.
}}

{{LuaCallin
|name = DrawInMinimap
|params = sx, sy
|return = none
|description = Where <code>sx</code>, <code>sy</code> are values relative to the minimap's position and scale.
}}

{{LuaCallin
|name = DrawInMinimapBackground
|params = sx, sy
|return = none
|description = Where <code>sx</code>, <code>sy</code> are values relative to the minimap's position and scale.
}}

=== Custom Object Rendering ===
For the following calls <code>drawMode</code> can be one of the following, <code>notDrawing = 0</code>, <code>normalDraw = 1</code>, <code>shadowDraw = 2</code>, <code>reflectionDraw = 3</code>, <code>refractionDraw = 4</code>.

{{LuaCallin
|name = DrawUnit
|params = unitID, drawMode
|return = bool suppressEngineDraw
|description = For custom rendering of units, [[Lua_UnitRendering#Lua.27s_DrawXYZ-Callin|enabled here]].
}}

{{LuaCallin
|name = DrawFeature
|params = unitID, drawMode
|return = bool suppressEngineDraw
|description = For custom rendering of features, [[Lua_UnitRendering#Lua.27s_DrawXYZ-Callin|enabled here]].
}}

{{LuaCallin
|name = DrawShield
|params = unitID, weaponID, drawMode
|return = bool suppressEngineDraw
|description = For custom rendering of [[Gamedev:WeaponDefs#Shield_(WeaponType)|shields]].
}}

{{LuaCallin
|name = DrawProjectile
|params = projectileID, drawMode
|return = bool suppressEngineDraw
|description = For custom rendering of weapon (& other) projectiles.
}}

== Synced - Unsynced Shared ==

{{LuaCallin
|name = GotChatMsg
|params = msg, player
|return = none
|description = Called when a player issues a UI command e.g. types <code>/foo</code> or <code>/luarules foo</code>.
}}

=== Game ===

{{LuaCallin
|name = GameID
|params = gameID
|return = none
|description = Called once to deliver the gameID.
}}

{{LuaCallin
|name = GamePaused
|params =
|return = none
|description = Called when the game is paused.
}}

{{LuaCallin
|name = GameOver
|params = winningAllyTeams
|return = none
|description = The parameter is a list of winning allyTeams, if empty the game result was undecided (like when dropping from an host).
}}

{{LuaCallin
|name = GameFrame
|params = frame
|return = none
|description = Called for every game simulation frame (30 per second).
}}

{{LuaCallin
|name = GamePreload
|params =
|return = none
|description = Called before the 0 gameframe.
}}

{{LuaCallin
|name = GameStart
|params =
|return = none
|description = Called upon the start of the game.
}}

=== Teams ===
{{LuaCallin
|name = TeamChanged
|params = teamID
|return = none
|description = ???
}}

{{LuaCallin
|name = TeamDied
|params = teamID
|return = none
|description = Called when a team dies (see [[Lua_SyncedCtrl#Game_End|Spring.KillTeam]]).
}}

=== Units ===
{{LuaCallin
|name = UnitCreated
|params = unitID, unitDefID, unitTeam, builderID
|return = none
|description = Called at the moment the unit is created.
}}

{{LuaCallin
|name = UnitFinished
|params = unitID, unitDefID, unitTeam
|return = none
|description = Called at the moment the unit is completed.
}}

{{LuaCallin
|name = UnitFromFactory
|params = unitID, unitDefID, unitTeam, factID, factDefID, userOrders
|return = none
|description = Called when a factory finishes construction of a unit.
}}

{{LuaCallin
|name = UnitGiven
|params = unitID, unitDefID, newTeam, oldTeam
|return = none
|description = Called when a unit is transferred between teams.
}}

{{LuaCallin
|name = UnitTaken
|params = unitID, unitDefID, oldTeam, newTeam
|return = none
|description = Called when a unit is transferred between teams.
}}

{{LuaCallin
|name = UnitDamaged
|params = unitID, unitDefID, unitTeam, damage, paralyzer, weaponDefID, projectileID, attackerID, attackerDefID, attackerTeam
|return = none
|description = Called when a unit is damaged (after <code>UnitPreDamaged</code>).
}}

{{LuaCallin
|name = UnitDestroyed
|params = unitID, unitDefID, unitTeam, attackerID, attackerDefID, attackerTeam
|return = none
|description = Called when a unit is destroyed.
}}

{{LuaCallin
|name = UnitStunned
|params = unitID, unitDefID, unitTeam, stunned
|return = none
|description = Called when a unit changes its stun status. {{new|99.0}}
}}

{{LuaCallin
|name = UnitUnitCollision
|params = colliderID, collideeID
|return = none
|description = Called when two units collide. Both units must be registered with [[Lua_System#Synced|Script.SetWatchUnit]].
}}

{{LuaCallin
|name = UnitFeatureCollision
|params = colliderID, collideeID
|return = none
|description = Called when a unit collides with a feature. The unit must be registered with [[Lua_System#Synced|Script.SetWatchUnit]] and the feature registered with [[Lua_System#Synced|Script.SetWatchFeature]].
}}

{{LuaCallin
|name = UnitCommand
|params = unitID, unitDefID, teamID, cmdID, cmdParams, cmdOptions
|return = none
|description = Called after when a unit accepts a command, after <code>AllowCommand</code> returns <code>true</code>.
}}

{{LuaCallin
|name = UnitCmdDone
|params = unitID, unitDefID, unitTeam, cmdID, cmdTag, cmdParams, cmdOpts
|return = none
|description = Called when a unit completes a command.
}}

{{LuaCallin
|name = UnitLoaded
|params = unitID, unitDefID, unitTeam, transportID, transportTeam
|return = none
|description = Called when a unit is loaded by a transport.
}}

{{LuaCallin
|name = UnitUnloaded
|params = unitID, unitDefID, unitTeam, transportID, transportTeam
|return = none
|description = Called when a unit is unloaded by a transport.
}}

{{LuaCallin
|name = UnitExperience
|params = unitID, unitDefID, unitTeam, experience, oldExperience
|return = none
|description = Called when a unit gains experience greater or equal to the minimum limit set by calling [[Lua_SyncedCtrl#Other|Spring.SetExperienceGrade]].
}}

{{LuaCallin
|name = UnitIdle
|params = unitID, unitDefID, unitTeam
|return = none
|description = Called when a unit is idle (empty command queue).
}}

{{LuaCallin
|name = UnitCloaked
|params = unitID, unitDefID, unitTeam
|return = none
|description = Called when a unit cloaks.
}}

{{LuaCallin
|name = UnitDecloaked
|params = unitID, unitDefID, unitTeam
|return = none
|description = Called when a unit decloaks.
}}

{{LuaCallin
|name = UnitMoved
|params = ???
|return = none
|description = ??? Not implemented in base handler
}}

{{LuaCallin
|name = UnitMoveFailed
|params = ???
|return = none
|description = ??? Not implemented in base handler
}}

{{LuaCallin
|name = StockpileChanged
|params = unitID, unitDefID, unitTeam, weaponNum, oldCount, newCount
|return = none
|description = Called when a units stockpile of weapons increases or decreases. See {{xtaglink|Gamedev:WeaponDefs|stockpile}}.
}}

{{LuaCallin
|name = UnitEnteredLos
|params = unitID, unitTeam, allyTeam, unitDefID
|return = none
|description = Called when a unit enters LOS of an allyteam.
}}

{{LuaCallin
|name = UnitLeftLos
|params = unitID, unitTeam, allyTeam, unitDefID
|return = none
|description = Called when a unit leaves LOS of an allyteam.
}}

{{LuaCallin
|name = UnitEnteredRadar
|params = unitID, unitTeam, allyTeam, unitDefID
|return = none
|description = Called when a unit enters radar of an allyteam.
}}

{{LuaCallin
|name = UnitLeftRadar
|params = unitID, unitTeam, allyTeam, unitDefID
|return = none
|description = Called when a unit leaves radar of an allyteam.
}}

{{LuaCallin
|name = UnitEnteredAir
|params = ???
|return = none
|description = ??? Not implemented by base handler
}}

{{LuaCallin
|name = UnitLeftAir
|params = ???
|return = none
|description = ??? Not implemented by base handler
}}

{{LuaCallin
|name = UnitEnteredWater
|params = ???
|return = none
|description = ??? Not implemented by base handler
}}

{{LuaCallin
|name = UnitLeftWater
|params = ???
|return = none
|description = ??? Not implemented by base handler
}}

{{LuaCallin
|name = UnitSeismicPing
|params = x, y, z, strength, allyTeam, unitID, unitDefID
|return = none
|description = Called when a unit emits a seismic ping. See {{xtaglink|Gamedev:UnitDefs|seismicSignature}}.
}}

=== Features ===
{{LuaCallin
|name = FeatureCreated
|params = featureID, allyTeamID
|return = none
|description = Called when a feature is created.
}}

{{LuaCallin
|name = FeatureDamaged
|params = featureID, featureDefID, featureTeam, damage, weaponDefID, projectileID, attackerID, attackerDefID, attackerTeam
|return = none
|description = Called when a feature is damaged.
}}

{{LuaCallin
|name = FeatureDestroyed
|params = featureID, allyTeamID
|return = none
|description = Called when a feature is destroyed.
}}

{{LuaCallin
|name = FeatureMoved
|params = ???
|return = none
|description = ???
}}

=== Projectiles ===
The following Callins are only called for weaponDefIDs registered via [[Lua_System#Synced|Script.SetWatchWeapon]].

{{LuaCallin
|name = ProjectileCreated
|params = proID, proOwnerID, weaponDefID
|return = none
|description = Called when the projectile is created.
}}

{{LuaCallin
|name = ProjectileDestroyed
|params = proID
|return = none
|description = Called when the projectile is destroyed.
}}

== Synced Only ==
{{LuaCallin
|name = CommandFallback
|params = unitID, unitDefID, unitTeam, cmdID, cmdParams, cmdOptions, cmdTag
|return = bool used, bool finished
|description = Called when the unit reaches an unknown command in its queue (i.e. one not handled by the engine). If no addon returns <code>used</code> as <code>true</code> the command is dropped, if an addon returns <code>true, true</code> the command is removed because it's done, with <code>true, false</code> it's kept in the queue and <code>CommandFallback</code> gets called again on the next slowupdate.
}}

{{LuaCallin
|name = AllowCommand
|params = unitID, unitDefID, unitTeam, cmdID, cmdParams, cmdOptions, cmdTag, synced
|return = bool allow
|description = Called when the command is given, before the unit's queue is altered. The return value is whether it should be let into the queue. The queue remains untouched when a command is blocked, whether it would be queued or replace the queue.
}}

{{LuaCallin
|name = AllowUnitCreation
|params = unitDefID, builderID, builderTeam, x, y, z, facing
|return = bool allow
|description = Called just before unit is created, the boolean return value determines whether or not the creation is permitted.
}}

{{LuaCallin
|name = AllowUnitTransfer
|params = unitID, unitDefID, oldTeam, newTeam, capture
|return = bool allow
|description = Called just before a unit is transferred to a different team, the boolean return value determines whether or not the transfer is permitted.
}}

{{LuaCallin
|name = AllowUnitBuildStep
|params = builderID, builderTeam, unitID, unitDefID, part
|return = bool allow
|description = Called just before a unit progresses its build percentage, the boolean return value determines whether or not the build makes progress.
}}

{{LuaCallin
|name = AllowFeatureCreation
|params = featureDefID, teamID, x, y, z
|return = bool allow
|description = Called just before feature is created, the boolean return value determines whether or not the creation is permitted.
}}

{{LuaCallin
|name = AllowFeatureBuildStep
|params = builderID, builderTeam, featureID, featureDefID, part
|return = bool allow
|description = Called just before a feature progresses its build percentage, the boolean return value determines whether or not the progress change is permitted.
}}

{{LuaCallin
|name = AllowResourceLevel
|params = teamID, res, level
|return = bool allow
|description = Called when a team sets the sharing level of a resource, the boolean return value determines whether or not the sharing level is permitted.
}}

{{LuaCallin
|name = AllowResourceTransfer
|params = oldTeamID, newTeamID, res, amount
|return = bool allow
|description = Called just before resources are transferred between players, the boolean return value determines whether or not the transfer is permitted.
}}

{{LuaCallin
|name = AllowStartPosition
|params = clampedX, clampedY, clampedZ, playerID, readyState, rawX, rawY, rawZ
|return = bool allow
|description = <code>clamped</code> are the coordinates clamped into start-boxes, <code>raw</code> is where player tried to place their marker. The <code>readyState</code> can be any one of
* <code>0</code> - player picked a position,
* <code>1</code> - player clicked ready,
* <code>2</code> - player pressed ready OR the game was force-started (player did not click ready, but is now forcibly readied) or
* <code>3</code> - the player failed to load.
* {{new|95.0}} the default 'failed to choose' start-position is the north-west point of their startbox, or <code>(0,0,0)</code> if they do not have a startbox.
}}

{{LuaCallin
|name = AllowDirectUnitControl
|params = unitID, unitDefID, unitTeam, playerID
|return = bool allow
|description = Determines if this unit can be controlled directly in FPS view.
}}

{{LuaCallin
|name = AllowWeaponTargetCheck
|params = attackerID, attackerWeaponNum, attackerWeaponDefID
|return = bool allowCheck, bool ignoreCheck
|description = Determines if this weapon can automatically generate targets itself. See also {{xtaglink|Gamedev:WeaponDefs|commandFire}} weaponDef tag. The <code>ignoreCheck</code> return value was added in 99.0 to allow ignoring the callin i.e. running normal engine check for this weapon.
}}

{{LuaCallin
|name = AllowWeaponTarget
|params = attackerID, targetID, attackerWeaponNum, attackerWeaponDefID, defPriority
|return = bool allowed, number newPriority
|description = Controls blocking of a specific target from being considered during a weapon's periodic auto-targeting sweep. The second return value is the new priority for this target (if you don't want to change it, return defPriority). Lower priority targets are targeted first.
}}

{{LuaCallin
|name = AllowWeaponInterceptTarget
|params = interceptorUnitID, interceptorWeaponID, targetProjectileID
|return = bool allowed
|description = Controls blocking of a specific intercept target from being considered during an {{xtaglink|Gamedev:WeaponDefs|interceptor}} weapon's periodic auto-targeting sweep. Only called for weaponDefIDs registered via [[Lua_System#Synced|Script.SetWatchWeapon]].
}}

{{LuaCallin
|name = AllowBuilderHoldFire
|params = unitID, unitDefID, action
|return = bool actionAllowed
|description = {{new|98.0}} {{Sourcelinkhash|5a82d750b89e72024bb0bb62cf05ea257737e0ac}} Called when a construction unit wants to "use his nano beams".<br><code>action</code> is one of following:
* <code>-1</code> Build
* <code>CMD.REPAIR</code> Repair
* <code>CMD.RECLAIM</code> Reclaim
* <code>CMD.RESTORE</code> Restore
* <code>CMD.RESURRECT</code> Resurrect
* <code>CMD.CAPTURE</code> Capture
}}

{{LuaCallin
|name = Explosion
|params = weaponDefID, px, py, pz, AttackerID
|return = bool noGfx
|description = Called when an explosion occurs. If it returns <code>true</code> then no graphical effects are drawn by the engine for this explosion.
}}

{{LuaCallin
|name = TerraformComplete
|params = unitID, unitDefID, unitTeam, buildUnitID, buildUnitDefID, buildUnitTeam
|return = bool stop
|description = Called when pre-building terrain levelling terraforms are completed (c.f. {{xtaglink|Gamedev:UnitDefs|levelGround}}). If the return value is <code>true</code> the current build order is terminated.
}}

{{LuaCallin
|name = MoveCtrlNotify
|params = unitID, unitDefID, unitTeam, data
|return = bool moveCtrlComplete
|description = Enable both [[Lua_MoveCtrl#Options|Spring.MoveCtrl.SetCollideStop]] and [[Lua_MoveCtrl#Options|Spring.MoveCtrl.SetTrackGround]] to enable this call-in, data was supposed to indicate the type of notification but currently never has a value other than <code>1</code> ("unit hit the ground"). The return value determines whether or not the unit should remain script-controlled (<code>false</code>) or return to engine controlled movement (<code>true</code>).
}}

{{LuaCallin
|name = RecvLuaMsg
|params = msg, playerID
|return = none
|description = Receives messages from unsynced sent via [[Lua_UnsyncedCtrl#SendLuaMessage|Spring.SendLuaRulesMsg]].
}}

{{LuaCallin
|name = Load
|params = zip
|return = none
|description = Called after <code>GamePreload</code> and before <code>GameStart</code>. See [[Lua_SaveLoad#Load_.28_zip_.29_-.3E_nil|Lua_SaveLoad]].
}}

=== Damage Controllers ===
For the following callins, in addition to being a regular weapon, <code>weaponDefID</code> may be one of the following:
* <code>-1</code> - debris collision, also default of [[Lua_SyncedCtrl#Unit_Control|Spring.AddUnitDamage]]
* <code>-2</code> - ground collision
* <code>-3</code> - object collision
* <code>-4</code> - fire damage
* <code>-5</code> - water damage
* <code>-6</code> - kill damage
* <code>-7</code> - crush damage

{{LuaCallin
|name = UnitPreDamaged
|params = unitID, unitDefID, unitTeam, damage, paralyzer, weaponDefID, projectileID, attackerID, attackerDefID, attackerTeam
|return = number newDamage, number impulseMult
|description = Called before damage is applied to the unit, allows fine control over how much damage and [http://en.wikipedia.org/wiki/Impulse_(physics) impulse] is applied.
}}

{{LuaCallin
|name = ShieldPreDamaged
|params = proID, proOwnerID, shieldEmitterWeaponNum, shieldCarrierUnitID, bounceProjectile
|return = bool handleCollision
|description = Called before any engine shield-vs-projectile logic executes. If the return value is <code>true</code> the gadget handles the collision event and the engine does not remove the projectile.
}}

{{LuaCallin
|name = FeaturePreDamaged
|params = featureID, featureDefID, featureTeam, damage, weaponDefID, projectileID, attackerID, attackerDefID, attackerTeam
|return = number newDamage, number impulseMult
|description = Called before damage is applied to the feature, allows fine control over how much damage and [http://en.wikipedia.org/wiki/Impulse_(physics) impulse] is applied.
}}

[[Category: Lua]]

Lua:Callins

2015-11-03T22:03:07Z

Zwzsg: I wonder how to get the full list of callin return values....

= Lua Callins =
This page is future looking to unified widget/gadget (aka "addon") handler, which may yet be some way off, c.f. the [https://github.com/spring/spring/blob/ebb704e008f6ea645947d07be1cfcc272af0428f/doc/changelog.txt#L71 changelog].

For now, to use these addons in a widget, replace addon with widget and, for a gadget, replace addon with gadget. For example,
<code><pre>
function widget:UnitCreated(unitID, unitDefID, unitTeam, builderID)
...
end
</pre></code>

Some functions may differ between (synced) gadget and widgets; those are in the [[#Synced_-_Unsynced_Shared]] section. Essentially the reason is that all information should be available to synced (game logic controlling) gadgets, but restricted to unsynced gadget/widget (e.g. information about an enemy unit only detected via radar and not yet in LOS). In such cases the full (synced) param list is documented.

Warning: Some callins, such as KeyPress, may return a bool, to indicate that they grabbed the event and that it should not be available for others, despite being marked with none return on this list.

== Common ==
{{LuaCallin
|name = Initialize
|params =
|return = none
|description = Called when the addon is (re)loaded.
}}

{{LuaCallin
|name = Shutdown
|params =
|return = none
|description = Called when the addon or the game is shutdown.
}}

== Unsynced Only ==

{{LuaCallin
|name = DefaultCommand
|params = type, id
|return = number cmdID
|description = Used to set the default command when a unit is selected. First parameter is the type of the object pointed at (either "unit or "feature") and the second is its unitID or featureID respectively.
}}

{{LuaCallin
|name = CommandNotify
|params = cmdID, cmdParams, cmdOptions
|return = bool removeCmd
|description = Called when a command is issued. Returning <code>true</code> deletes the command and does not send it through the network.
}}

{{LuaCallin
|name = WorldTooltip
|params = ttType, data1, data2, data3
|return = string newTooltip
|description = The parameters can be <code>"unit"</code>, <code>unitID</code>; <code>"feature"</code>, <code>featureID</code>; <code>"ground"</code>, <code>posX</code>, <code>posY</code>, <code>posZ</code> or <code>"selection"</code>.
}}

{{LuaCallin
|name = UnsyncedHeightMapUpdate
|params = ???
|return = none
|description = Called when the unsynced copy of the height-map is altered.
}}

{{LuaCallin
|name = GameProgress
|params = serverFrameNum
|return = none
|description = Called every 60 frames, calculating delta between GameFrame and GameProgress. Can give an ETA about catching up with simulation for mid-game join players.
}}

{{LuaCallin
|name = GameSetup
|params = state, ready, playerStates
|return = bool success, bool newReady
|description = ???
}}

{{LuaCallin
|name = SunChanged
|params = ???
|return = none
|description = ???
}}

{{LuaCallin
|name = AddConsoleLine
|params = msg, priority
|return = none
|description = Called when text is entered into the console (e.g. Spring.Echo).
}}

{{LuaCallin
|name = RecvSkirmishAIMessage
|params = aiTeam, dataStr
|return = ???
|description = ???
}}

{{LuaCallin
|name = RecvFromSynced
|params = ...
|return = none
|description = Receives data sent via [[Lua_System#Synced|SendToUnsynced]] callout.
}}

{{LuaCallin
|name = Save
|params = zip
|return = none
|description = Called when a chat command '/save' or '/savegame' is received. The single argument is a userdatum representing the savegame zip file. See [[Lua_SaveLoad#Save_.28_zip_.29_-.3E_nil|Lua_SaveLoad]].
}}

{{LuaCallin
|name = LoadProgress
|params = message, replaceLastLine
|return = none
|description = Only available to LuaIntro.
}}

{{LuaCallin
|name = GroupChanged
|params = groupID
|return = none
|description = Called when a unit is added to or removed from a control group. Currently implemented for widgets only.
}}

{{LuaCallin
|name = ConfigureLayout
|params = ???
|return = ???
|description = ???
}}

=== Input ===
{{LuaCallin
|name = IsAbove
|params = x, y
|return = bool isAbove
|description = Called every Update. Must return <code>true</code> for <code>Mouse*</code> events and <code>GetToolTip</code> to be called.
}}

{{LuaCallin
|name = GetTooltip
|params = x, y
|return = string tooltip
|description = Called when <code>IsAbove</code> returns true.
}}

{{LuaCallin
|name = KeyPress
|params = key, mods, isRepeat
|return = none
|description = Called repeatedly when a key is pressed down. If you want an action to occur only once check for <code>isRepeat == false</code>. The <code>mods</code> parameter is a table, with keys <code>alt</code>, <code>ctrl</code>, <code>meta</code> and <code>shift</code> each having a boolean value.
}}

{{LuaCallin
|name = KeyRelease
|params = key
|return = none
|description = Called when the key is released.
}}

{{LuaCallin
|name = TextInput
|params = utf8char
|return = none
|description = Called whenever a key press results in text input. Introduced in 97.0.
}}

{{LuaCallin
|name = JoystickEvent
|params = ???
|return = none
|description = ???
}}

{{LuaCallin
|name = MousePress
|params = x, y, button
|return = bool becomeMouseOwner
|description = Called when a mouse button is pressed. The <code>button</code> parameter supports up to 7 buttons. Must return <code>true</code> for <code>MouseRelease</code> and other functions to be called.
}}

{{LuaCallin
|name = MouseRelease
|params = x, y, button
|return = bool becomeMouseOwner
|description = Called when a mouse button is released. Please note that in order to have Spring call <code>MouseRelease</code>, you need to have a <code>MousePress</code> call-in in the same addon that returns <code>true</code>.
}}

{{LuaCallin
|name = MouseWheel
|params = up, value
|return = none
|description = Called when the mouse wheel is moved. The parameters indicate the direction and amount of travel.
}}

{{LuaCallin
|name = MouseMove
|params = x, y, dx, dy, button
|return = none
|description = Called when the mouse is moved. The <code>dx</code> and <code>dy</code> parameters indicate the distance travelled, whereas the first two indicate the final position.
}}

=== Players ===
{{LuaCallin
|name = PlayerChanged
|params = playerID
|return = none
|description = Called whenever a player's status changes e.g. becoming a spectator.
}}

{{LuaCallin
|name = PlayerAdded
|params = playerID
|return = none
|description = Called whenever a new player joins the game.
}}

{{LuaCallin
|name = PlayerRemoved
|params = playerID, reason
|return = none
|description = Called whenever a player is removed from the game.
}}

=== Drawing ===

{{LuaCallin
|name = ViewResize
|params = viewSizeX, viewSizeY
|return = none
|description = Called whenever the window is resized.
}}

{{LuaCallin
|name = Update
|params = dt
|return = none
|description = Called for every draw frame. The parameter is the time since the last update. Perform calculations in here and only drawing in Draw* callins.}}

Inside the Draw* functions, you can use the [[Lua_OpenGL_Api | Lua OpenGL Api]] to draw graphics.

{{LuaCallin
|name = DrawGenesis
|params =
|return = none
|description = Doesn't render to screen! Use this callin to update textures, shaders, etc.
}}

{{LuaCallin
|name = DrawWorldPreUnit
|params =
|return = none
|description = Spring draws units, features, some water types, cloaked units, and the sun.
}}

{{LuaCallin
|name = DrawWorld
|params =
|return = none
|description = Spring draws command queues, 'map stuff', and map marks.
}}

{{LuaCallin
|name = DrawWorldShadow
|params =
|return = none
|description = ???
}}

{{LuaCallin
|name = DrawWorldReflection
|params =
|return = none
|description = ???
}}

{{LuaCallin
|name = DrawWorldRefraction
|params =
|return = none
|description = ???
}}

{{LuaCallin
|name = DrawScreen
|params =
|return = none
|description = ???
}}

{{LuaCallin
|name = DrawScreenEffects
|params = vsx, vsy
|return = none
|description = Where <code>vsx</code>, <code>vsy</code> are screen coordinates.
}}

{{LuaCallin
|name = DrawLoadScreen
|params =
|return = none
|description = {{new|95.0}} Only available to LuaIntro, draws custom load screens.
}}

{{LuaCallin
|name = DrawInMinimap
|params = sx, sy
|return = none
|description = Where <code>sx</code>, <code>sy</code> are values relative to the minimap's position and scale.
}}

{{LuaCallin
|name = DrawInMinimapBackground
|params = sx, sy
|return = none
|description = Where <code>sx</code>, <code>sy</code> are values relative to the minimap's position and scale.
}}

=== Custom Object Rendering ===
For the following calls <code>drawMode</code> can be one of the following, <code>notDrawing = 0</code>, <code>normalDraw = 1</code>, <code>shadowDraw = 2</code>, <code>reflectionDraw = 3</code>, <code>refractionDraw = 4</code>.

{{LuaCallin
|name = DrawUnit
|params = unitID, drawMode
|return = bool suppressEngineDraw
|description = For custom rendering of units, [[Lua_UnitRendering#Lua.27s_DrawXYZ-Callin|enabled here]].
}}

{{LuaCallin
|name = DrawFeature
|params = unitID, drawMode
|return = bool suppressEngineDraw
|description = For custom rendering of features, [[Lua_UnitRendering#Lua.27s_DrawXYZ-Callin|enabled here]].
}}

{{LuaCallin
|name = DrawShield
|params = unitID, weaponID, drawMode
|return = bool suppressEngineDraw
|description = For custom rendering of [[Gamedev:WeaponDefs#Shield_(WeaponType)|shields]].
}}

{{LuaCallin
|name = DrawProjectile
|params = projectileID, drawMode
|return = bool suppressEngineDraw
|description = For custom rendering of weapon (& other) projectiles.
}}

== Synced - Unsynced Shared ==

{{LuaCallin
|name = GotChatMsg
|params = msg, player
|return = none
|description = Called when a player issues a UI command e.g. types <code>/foo</code> or <code>/luarules foo</code>.
}}

=== Game ===

{{LuaCallin
|name = GameID
|params = gameID
|return = none
|description = Called once to deliver the gameID.
}}

{{LuaCallin
|name = GamePaused
|params =
|return = none
|description = Called when the game is paused.
}}

{{LuaCallin
|name = GameOver
|params = winningAllyTeams
|return = none
|description = The parameter is a list of winning allyTeams, if empty the game result was undecided (like when dropping from an host).
}}

{{LuaCallin
|name = GameFrame
|params = frame
|return = none
|description = Called for every game simulation frame (30 per second).
}}

{{LuaCallin
|name = GamePreload
|params =
|return = none
|description = Called before the 0 gameframe.
}}

{{LuaCallin
|name = GameStart
|params =
|return = none
|description = Called upon the start of the game.
}}

=== Teams ===
{{LuaCallin
|name = TeamChanged
|params = teamID
|return = none
|description = ???
}}

{{LuaCallin
|name = TeamDied
|params = teamID
|return = none
|description = Called when a team dies (see [[Lua_SyncedCtrl#Game_End|Spring.KillTeam]]).
}}

=== Units ===
{{LuaCallin
|name = UnitCreated
|params = unitID, unitDefID, unitTeam, builderID
|return = none
|description = Called at the moment the unit is created.
}}

{{LuaCallin
|name = UnitFinished
|params = unitID, unitDefID, unitTeam
|return = none
|description = Called at the moment the unit is completed.
}}

{{LuaCallin
|name = UnitFromFactory
|params = unitID, unitDefID, unitTeam, factID, factDefID, userOrders
|return = none
|description = Called when a factory finishes construction of a unit.
}}

{{LuaCallin
|name = UnitGiven
|params = unitID, unitDefID, newTeam, oldTeam
|return = none
|description = Called when a unit is transferred between teams.
}}

{{LuaCallin
|name = UnitTaken
|params = unitID, unitDefID, oldTeam, newTeam
|return = none
|description = Called when a unit is transferred between teams.
}}

{{LuaCallin
|name = UnitDamaged
|params = unitID, unitDefID, unitTeam, damage, paralyzer, weaponDefID, projectileID, attackerID, attackerDefID, attackerTeam
|return = none
|description = Called when a unit is damaged (after <code>UnitPreDamaged</code>).
}}

{{LuaCallin
|name = UnitDestroyed
|params = unitID, unitDefID, unitTeam, attackerID, attackerDefID, attackerTeam
|return = none
|description = Called when a unit is destroyed.
}}

{{LuaCallin
|name = UnitStunned
|params = unitID, unitDefID, unitTeam, stunned
|return = none
|description = Called when a unit changes its stun status. {{new|99.0}}
}}

{{LuaCallin
|name = UnitUnitCollision
|params = colliderID, collideeID
|return = none
|description = Called when two units collide. Both units must be registered with [[Lua_System#Synced|Script.SetWatchUnit]].
}}

{{LuaCallin
|name = UnitFeatureCollision
|params = colliderID, collideeID
|return = none
|description = Called when a unit collides with a feature. The unit must be registered with [[Lua_System#Synced|Script.SetWatchUnit]] and the feature registered with [[Lua_System#Synced|Script.SetWatchFeature]].
}}

{{LuaCallin
|name = UnitCommand
|params = unitID, unitDefID, teamID, cmdID, cmdParams, cmdOptions
|return = none
|description = Called after when a unit accepts a command, after <code>AllowCommand</code> returns <code>true</code>.
}}

{{LuaCallin
|name = UnitCmdDone
|params = unitID, unitDefID, unitTeam, cmdID, cmdTag, cmdParams, cmdOpts
|return = none
|description = Called when a unit completes a command.
}}

{{LuaCallin
|name = UnitLoaded
|params = unitID, unitDefID, unitTeam, transportID, transportTeam
|return = none
|description = Called when a unit is loaded by a transport.
}}

{{LuaCallin
|name = UnitUnloaded
|params = unitID, unitDefID, unitTeam, transportID, transportTeam
|return = none
|description = Called when a unit is unloaded by a transport.
}}

{{LuaCallin
|name = UnitExperience
|params = unitID, unitDefID, unitTeam, experience, oldExperience
|return = none
|description = Called when a unit gains experience greater or equal to the minimum limit set by calling [[Lua_SyncedCtrl#Other|Spring.SetExperienceGrade]].
}}

{{LuaCallin
|name = UnitIdle
|params = unitID, unitDefID, unitTeam
|return = none
|description = Called when a unit is idle (empty command queue).
}}

{{LuaCallin
|name = UnitCloaked
|params = unitID, unitDefID, unitTeam
|return = none
|description = Called when a unit cloaks.
}}

{{LuaCallin
|name = UnitDecloaked
|params = unitID, unitDefID, unitTeam
|return = none
|description = Called when a unit decloaks.
}}

{{LuaCallin
|name = UnitMoved
|params = ???
|return = none
|description = ??? Not implemented in base handler
}}

{{LuaCallin
|name = UnitMoveFailed
|params = ???
|return = none
|description = ??? Not implemented in base handler
}}

{{LuaCallin
|name = StockpileChanged
|params = unitID, unitDefID, unitTeam, weaponNum, oldCount, newCount
|return = none
|description = Called when a units stockpile of weapons increases or decreases. See {{xtaglink|Gamedev:WeaponDefs|stockpile}}.
}}

{{LuaCallin
|name = UnitEnteredLos
|params = unitID, unitTeam, allyTeam, unitDefID
|return = none
|description = Called when a unit enters LOS of an allyteam.
}}

{{LuaCallin
|name = UnitLeftLos
|params = unitID, unitTeam, allyTeam, unitDefID
|return = none
|description = Called when a unit leaves LOS of an allyteam.
}}

{{LuaCallin
|name = UnitEnteredRadar
|params = unitID, unitTeam, allyTeam, unitDefID
|return = none
|description = Called when a unit enters radar of an allyteam.
}}

{{LuaCallin
|name = UnitLeftRadar
|params = unitID, unitTeam, allyTeam, unitDefID
|return = none
|description = Called when a unit leaves radar of an allyteam.
}}

{{LuaCallin
|name = UnitEnteredAir
|params = ???
|return = none
|description = ??? Not implemented by base handler
}}

{{LuaCallin
|name = UnitLeftAir
|params = ???
|return = none
|description = ??? Not implemented by base handler
}}

{{LuaCallin
|name = UnitEnteredWater
|params = ???
|return = none
|description = ??? Not implemented by base handler
}}

{{LuaCallin
|name = UnitLeftWater
|params = ???
|return = none
|description = ??? Not implemented by base handler
}}

{{LuaCallin
|name = UnitSeismicPing
|params = x, y, z, strength, allyTeam, unitID, unitDefID
|return = none
|description = Called when a unit emits a seismic ping. See {{xtaglink|Gamedev:UnitDefs|seismicSignature}}.
}}

=== Features ===
{{LuaCallin
|name = FeatureCreated
|params = featureID, allyTeamID
|return = none
|description = Called when a feature is created.
}}

{{LuaCallin
|name = FeatureDamaged
|params = featureID, featureDefID, featureTeam, damage, weaponDefID, projectileID, attackerID, attackerDefID, attackerTeam
|return = none
|description = Called when a feature is damaged.
}}

{{LuaCallin
|name = FeatureDestroyed
|params = featureID, allyTeamID
|return = none
|description = Called when a feature is destroyed.
}}

{{LuaCallin
|name = FeatureMoved
|params = ???
|return = none
|description = ???
}}

=== Projectiles ===
The following Callins are only called for weaponDefIDs registered via [[Lua_System#Synced|Script.SetWatchWeapon]].

{{LuaCallin
|name = ProjectileCreated
|params = proID, proOwnerID, weaponDefID
|return = none
|description = Called when the projectile is created.
}}

{{LuaCallin
|name = ProjectileDestroyed
|params = proID
|return = none
|description = Called when the projectile is destroyed.
}}

== Synced Only ==
{{LuaCallin
|name = CommandFallback
|params = unitID, unitDefID, unitTeam, cmdID, cmdParams, cmdOptions, cmdTag
|return = bool used, bool finished
|description = Called when the unit reaches an unknown command in its queue (i.e. one not handled by the engine). If no addon returns <code>used</code> as <code>true</code> the command is dropped, if an addon returns <code>true, true</code> the command is removed because it's done, with <code>true, false</code> it's kept in the queue and <code>CommandFallback</code> gets called again on the next slowupdate.
}}

{{LuaCallin
|name = AllowCommand
|params = unitID, unitDefID, unitTeam, cmdID, cmdParams, cmdOptions, cmdTag, synced
|return = bool allow
|description = Called when the command is given, before the unit's queue is altered. The return value is whether it should be let into the queue. The queue remains untouched when a command is blocked, whether it would be queued or replace the queue.
}}

{{LuaCallin
|name = AllowUnitCreation
|params = unitDefID, builderID, builderTeam, x, y, z, facing
|return = bool allow
|description = Called just before unit is created, the boolean return value determines whether or not the creation is permitted.
}}

{{LuaCallin
|name = AllowUnitTransfer
|params = unitID, unitDefID, oldTeam, newTeam, capture
|return = bool allow
|description = Called just before a unit is transferred to a different team, the boolean return value determines whether or not the transfer is permitted.
}}

{{LuaCallin
|name = AllowUnitBuildStep
|params = builderID, builderTeam, unitID, unitDefID, part
|return = bool allow
|description = Called just before a unit progresses its build percentage, the boolean return value determines whether or not the build makes progress.
}}

{{LuaCallin
|name = AllowFeatureCreation
|params = featureDefID, teamID, x, y, z
|return = bool allow
|description = Called just before feature is created, the boolean return value determines whether or not the creation is permitted.
}}

{{LuaCallin
|name = AllowFeatureBuildStep
|params = builderID, builderTeam, featureID, featureDefID, part
|return = bool allow
|description = Called just before a feature progresses its build percentage, the boolean return value determines whether or not the progress change is permitted.
}}

{{LuaCallin
|name = AllowResourceLevel
|params = teamID, res, level
|return = bool allow
|description = Called when a team sets the sharing level of a resource, the boolean return value determines whether or not the sharing level is permitted.
}}

{{LuaCallin
|name = AllowResourceTransfer
|params = oldTeamID, newTeamID, res, amount
|return = bool allow
|description = Called just before resources are transferred between players, the boolean return value determines whether or not the transfer is permitted.
}}

{{LuaCallin
|name = AllowStartPosition
|params = clampedX, clampedY, clampedZ, playerID, readyState, rawX, rawY, rawZ
|return = bool allow
|description = <code>clamped</code> are the coordinates clamped into start-boxes, <code>raw</code> is where player tried to place their marker. The <code>readyState</code> can be any one of
* <code>0</code> - player picked a position,
* <code>1</code> - player clicked ready,
* <code>2</code> - player pressed ready OR the game was force-started (player did not click ready, but is now forcibly readied) or
* <code>3</code> - the player failed to load.
* {{new|95.0}} the default 'failed to choose' start-position is the north-west point of their startbox, or <code>(0,0,0)</code> if they do not have a startbox.
}}

{{LuaCallin
|name = AllowDirectUnitControl
|params = unitID, unitDefID, unitTeam, playerID
|return = bool allow
|description = Determines if this unit can be controlled directly in FPS view.
}}

{{LuaCallin
|name = AllowWeaponTargetCheck
|params = attackerID, attackerWeaponNum, attackerWeaponDefID
|return = bool allowCheck, bool ignoreCheck
|description = Determines if this weapon can automatically generate targets itself. See also {{xtaglink|Gamedev:WeaponDefs|commandFire}} weaponDef tag. The <code>ignoreCheck</code> return value was added in 99.0 to allow ignoring the callin i.e. running normal engine check for this weapon.
}}

{{LuaCallin
|name = AllowWeaponTarget
|params = attackerID, targetID, attackerWeaponNum, attackerWeaponDefID, defPriority
|return = bool allowed, number newPriority
|description = Controls blocking of a specific target from being considered during a weapon's periodic auto-targeting sweep. The second return value is the new priority for this target (if you don't want to change it, return defPriority). Lower priority targets are targeted first.
}}

{{LuaCallin
|name = AllowWeaponInterceptTarget
|params = interceptorUnitID, interceptorWeaponID, targetProjectileID
|return = bool allowed
|description = Controls blocking of a specific intercept target from being considered during an {{xtaglink|Gamedev:WeaponDefs|interceptor}} weapon's periodic auto-targeting sweep. Only called for weaponDefIDs registered via [[Lua_System#Synced|Script.SetWatchWeapon]].
}}

{{LuaCallin
|name = AllowBuilderHoldFire
|params = unitID, unitDefID, action
|return = bool actionAllowed
|description = {{new|98.0}} {{Sourcelinkhash|5a82d750b89e72024bb0bb62cf05ea257737e0ac}} Called when a construction unit wants to "use his nano beams".<br><code>action</code> is one of following:
* <code>-1</code> Build
* <code>CMD.REPAIR</code> Repair
* <code>CMD.RECLAIM</code> Reclaim
* <code>CMD.RESTORE</code> Restore
* <code>CMD.RESURRECT</code> Resurrect
* <code>CMD.CAPTURE</code> Capture
}}

{{LuaCallin
|name = Explosion
|params = weaponDefID, px, py, pz, AttackerID
|return = bool noGfx
|description = Called when an explosion occurs. If it returns <code>true</code> then no graphical effects are drawn by the engine for this explosion.
}}

{{LuaCallin
|name = TerraformComplete
|params = unitID, unitDefID, unitTeam, buildUnitID, buildUnitDefID, buildUnitTeam
|return = bool stop
|description = Called when pre-building terrain levelling terraforms are completed (c.f. {{xtaglink|Gamedev:UnitDefs|levelGround}}). If the return value is <code>true</code> the current build order is terminated.
}}

{{LuaCallin
|name = MoveCtrlNotify
|params = unitID, unitDefID, unitTeam, data
|return = bool moveCtrlComplete
|description = Enable both [[Lua_MoveCtrl#Options|Spring.MoveCtrl.SetCollideStop]] and [[Lua_MoveCtrl#Options|Spring.MoveCtrl.SetTrackGround]] to enable this call-in, data was supposed to indicate the type of notification but currently never has a value other than <code>1</code> ("unit hit the ground"). The return value determines whether or not the unit should remain script-controlled (<code>false</code>) or return to engine controlled movement (<code>true</code>).
}}

{{LuaCallin
|name = RecvLuaMsg
|params = msg, playerID
|return = none
|description = Receives messages from unsynced sent via [[Lua_UnsyncedCtrl#SendLuaMessage|Spring.SendLuaRulesMsg]].
}}

{{LuaCallin
|name = Load
|params = zip
|return = none
|description = Called after <code>GamePreload</code> and before <code>GameStart</code>. See [[Lua_SaveLoad#Load_.28_zip_.29_-.3E_nil|Lua_SaveLoad]].
}}

=== Damage Controllers ===
For the following callins, in addition to being a regular weapon, <code>weaponDefID</code> may be one of the following:
* <code>-1</code> - debris collision, also default of [[Lua_SyncedCtrl#Unit_Control|Spring.AddUnitDamage]]
* <code>-2</code> - ground collision
* <code>-3</code> - object collision
* <code>-4</code> - fire damage
* <code>-5</code> - water damage
* <code>-6</code> - kill damage
* <code>-7</code> - crush damage

{{LuaCallin
|name = UnitPreDamaged
|params = unitID, unitDefID, unitTeam, damage, paralyzer, weaponDefID, projectileID, attackerID, attackerDefID, attackerTeam
|return = number newDamage, number impulseMult
|description = Called before damage is applied to the unit, allows fine control over how much damage and [http://en.wikipedia.org/wiki/Impulse_(physics) impulse] is applied.
}}

{{LuaCallin
|name = ShieldPreDamaged
|params = proID, proOwnerID, shieldEmitterWeaponNum, shieldCarrierUnitID, bounceProjectile
|return = bool handleCollision
|description = Called before any engine shield-vs-projectile logic executes. If the return value is <code>true</code> the gadget handles the collision event and the engine does not remove the projectile.
}}

{{LuaCallin
|name = FeaturePreDamaged
|params = featureID, featureDefID, featureTeam, damage, weaponDefID, projectileID, attackerID, attackerDefID, attackerTeam
|return = number newDamage, number impulseMult
|description = Called before damage is applied to the feature, allows fine control over how much damage and [http://en.wikipedia.org/wiki/Impulse_(physics) impulse] is applied.
}}

[[Category: Lua]]

AI:Development:Lang:Lua

2014-08-25T01:54:07Z

Zwzsg: /* References */ adding Spring Tank AI

[[Engine_Development|Development]] < [[AI:Development|AI Development]] < Lua AI Development

<h1>Writing a Lua AI</h1>

== Introduction ==

=== Lua AIs are different ===
Lua for AIs is quite different from all the other AI languages supported by spring. Lua AIs use a completely different interface, and they can not be shipped separately, but only bundled with a mod.

=== Things to know ===
* They have to be bundled with a mod. Therefore, you should consider contacting the mod developer(s) in question early, to see if they are at all interested in an AI.
* A Lua AI is actually a regular gadget. The difference is just that it is listed in the mods LuaAI.lua file. See [[Lua_Scripting|Lua Scripting]] for details.
* This brings up the problem that AIs can "accidentally" cheat or even move units of the enemy! It is up to the AI writer to avoid that. All AI players of the same type also share the same variables and tables. One way to avoid that is to put everything into a teamdata[teamID] table. Or the use of classes.

== How to start ==
For a start, choose a single mod you want your AI to work with.
You will also want to contact the mods developer(s) before you start to code,
or soon thereafter.

Things you need to get comfortable with:
* the Lua scripting language
* Lua scripting for spring (gadgets)

You may combine learning Lua for spring with writing simplistic gadgets or widgets for spring, and publishing them [http://springrts.com/phpbb/viewforum.php?f=23 in the forum],
as this way you get practical training and feedback about your code from the pros, plus the community eventually gets a usefull addon.
When you start feeling comfortable, you should inspect the code of Lua AIs that are already available.
Source code of these AIs can be found in the mod archives, which you may open with 7zip, or it may be available separately (see [[#References|References]]).

=== Integrating the AI Gadget ===
This section explains everything you have to do to integrate your Lua AI into a mod. Which at the same time is everything that separates a Lua AI form a gadget.

In the root of the mods archive, you need the file ''LuaAI.lua'',
which should look about like this:
<code>
-- file: LuaAI.lua
local listOfLuaAIs = {
{
name = "MyFirstAI",
desc = "Beats even the best players with Core, most others with Arm too",
},
}
return listOfLuaAIs
</code>

Besides all the other stuff you need for a gadget (you should know this by now),
you will need something like this in your code (eg under ''{mod_root}/LuaRules/Gadgets/MyFirstAI_v01.lua''):
<code>
function gadget:GetInfo()
return {
name = "MyFirstAI",
desc = "An AI that knows how to play Mod X",
author = "John Doe",
date = "2020-12-31",
license = "Public Domain",
layer = 82,
enabled = true
}
end

function gadget:GameStart()
-- Initialise AI for all teams that are set to use it
for _,t in ipairs(Spring.GetTeamList()) do
local _,_,_,isAI,side = Spring.GetTeamInfo(t)
if Spring.GetTeamLuaAI(t) == gadget:GetInfo().name then
Spring.Echo("Team "..t.." assigned to "..gadget:GetInfo().name)
local pos = {}
local home_x,home_y,home_z = Spring.GetTeamStartPosition(t)
end
end
end
</code>
'''Note:'''
The above example will not work if your AI controls multiple teams because ''home_x,home_y,home_z'' are not stored ''per team.''

That's it, the rest of the game is using regular gadget functions, and in particular [http://springrts.com/wiki/Lua_SyncedCtrl#Give_Order Spring.GiveOrderToUnit()]. Now you should be able to use this AI when starting the modified mod in the lobby, when you click on the ''Add Bot'' button. From Spring 95.0 onwards, lua AIs can be selected from the Spring.exe menu.

Enjoy!

== References ==
* NOE AI: http://springrts.com/phpbb/viewtopic.php?f=55&t=28259
* ST AI source: http://pastebin.com/v1kNRBDj
* KP AI source: http://pastebin.com/f771164a0
* CRAIG source:
** to browse: http://github.com/tvo/craig/tree/master
** for git: git://github.com/tvo/craig.git
* C.R.A.I.G. is inside S44 and SWIW
* forum thread: [http://springrts.com/phpbb/viewtopic.php?f=15&t=25639 LuaAI information]
* forum threads about an AI for the game Conflict Terra: [http://springrts.com/phpbb/viewtopic.php?f=63&t=26148] [http://springrts.com/phpbb/viewtopic.php?f=63&t=26214] [http://springrts.com/phpbb/viewtopic.php?f=15&t=26207] (among the OT, some more or less common LuaAI problems are discussed)

[[Category: AI Dev]]

Kernel Panic

2014-08-22T17:50:36Z

Zwzsg: added a ----

http://img390.imageshack.us/img390/6289/kernelhd0.png

==Overview:==

''For the latest news and/or assistance, try the [http://springrts.com/phpbb/viewforum.php?f=43'''KP forum'''] or go to #kp when you log onto the lobby.''

'''Kernel Panic''' is a game about computers. Systems, Hackers and Networks wage war in a matrix of DOOM! The only constraints are time and space; unlike other real time strategy games, no resource economy exists in KP.

All units are free in this game, every factory built will be spamming units at all times. You can build more factories, but only on pre-defined areas (geothermal vents). All that remains is pure strategy and tactics.

KP makes for a frantically fast-paced, action-oriented game, with a very unique graphical style.

----

==Download links:==

Current Version of Kernel Panic is 4.6

* <u>Newcomers:</u>
** If you run '''Windows''' (2000,XP,Vista,7):
*** Here you can get a complete installer:
*** http://springfiles.com/spring/game-installers/kernel-panic-installer
*** Use it to install both Spring and Kernel Panic in one go.
*** Then use the shortcuts created in your Start Menu or Desktop.
** If you run '''Linux''':
*** Read the [[SetupGuide]] how to install the Spring engine on Linux systems
*** Get and unzip that file: http://springfiles.com/spring/game-installers/kernel-panic-zip
*** Put the content of /games/ into ~/.spring/games
*** Put the content of /maps/ into ~/.spring/maps
*** Discard the rest.
*** Run Spring directly, a greenish menu should pop up.
*** Click skirmish, duel, easy, run.
*** For multiplayer or advanced options, run SpringLobby

* <u>Experienced Users:</u>
** If you have already the Spring engine (or prefer to install it yourself): Here you can get a zip with the mod file, the maps, and a tiny exe for single player frontend. Unzip into your Spring root folder: http://springfiles.com/spring/game-installers/kernel-panic-zip
** If you are certain you have all the maps and just need a quick link to the mod file itself: http://springfiles.com/spring/games/kernel-panic-mod

----

==Media:==

===Youtube Videos:===

[http://youtube.com/watch?v=doF7owZ0blk&fmt=18 http://i.ytimg.com/vi/doF7owZ0blk/default.jpg]
[http://youtube.com/watch?v=Ug1c19yaZac http://i.ytimg.com/vi/Ug1c19yaZac/default.jpg] [http://youtube.com/watch?v=GAZQhRlt5bU http://i.ytimg.com/vi/GAZQhRlt5bU/default.jpg]
[http://www.youtube.com/watch?v=3q48ys5hFtI&fmt=18 http://i.ytimg.com/vi/3q48ys5hFtI/default.jpg]

----
===Still shots:===

[http://tof.canardpc.com/view/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg http://tof.canardpc.com/preview/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg] [http://tof.canardpc.com/view/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg http://tof.canardpc.com/preview/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg] [http://tof.canardpc.com/view/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg http://tof.canardpc.com/preview/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg]

[http://tof.canardpc.com/view/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg http://tof.canardpc.com/preview/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg] [http://tof.canardpc.com/view/e5184baf-6c95-4c90-8469-b00a4f092054.jpg http://tof.canardpc.com/preview/e5184baf-6c95-4c90-8469-b00a4f092054.jpg] [http://tof.canardpc.com/view/cbe6dae0-a696-450a-bf22-236043d76511.jpg http://tof.canardpc.com/preview/cbe6dae0-a696-450a-bf22-236043d76511.jpg]

----

==License:==
Extracted from the [http://pastebin.ca/2834721 <code>Kernel_Panic_readme.txt</code>] file:

<pre>
========--------------------------------------------
License:
--------
- The content of the /games/Kernel*.sd7 is Public Domain, save:
/LuaUI/Widgets/kp_buildbar.lua
/LuaRules/Gadgets/autohold.lua
/LuaRules/Gadgets/Burrow.lua
/LuaRules/Gadgets/game_spawn.lua
which are GPL, taken from http://www.caspring.org or http://springrts.com
- The maps Marble Madness and Direct Memory Access are Public Domain
- The maps Major Madness and Speed Balls 16 Way status are unknown
- The maps Central Hub, Corrupted Core, Dual Core, Quad Core were initially CC BY-NC-SA.
Then the author removed the CC cause ( http://cpc.cx/4u3 )
- The Spring engine is GPL, available from http://spring.clan-sy.com
</pre>

----

== Game Modes:==
By default the aim is to destroy the homebase and all the minifacs of all opposing teams.
<br /><br />
Other "mod options" available are:
* '''King Of The Hill :''' Keeps control of the map center for a given time to win.
* '''O.N.S. :''' Adds shields to buildings, preventing homebase rush.
* '''Save Our Mem :''' Unit leave "leaks" that must be reclaimed.
* '''Color Wars :''' Whoever controls the most territory when timer elapse wins.
* '''Heroes of Mainframe :''' You only control a very buffed up but single unit. Best used with "Pre-placed Minifacs".
* '''Rebalancing formula :''' Let you change the stat of any units of weapons without the hassle of making a mutator.
<br />
For details, read [http://pastebin.ca/2834721 <code>Kernel_Panic_readme.txt</code>] or click [?] next to each mod option in your lobby.
----

==Units and Buildings:==

===System units:===

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Kernel.png</td><td>'''The Kernel:''' You start with one of these. It can build all mobile units in the game. Has rapid auto-heal and lots of health.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Socket.png</td><td>'''The Socket:''' The socket is a factory which can only be built on a geothermal vent. It can solely build bits, and slower than the kernel can. It autoheals, and has a decent amount of health.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Terminal.png</td><td>'''The Terminal:'''(only available in Division Zero) This is a new structure that gets placed on geovents. It can dispatch a nuclear bomber once every 90 seconds that will deal about 16000 damage to a large target area, i.e. it destroys everything except factories. It does much less damage to the kernel and hole. The bomber can strike any position on the map, there is no defense.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Assembler.png</td><td>'''The Assembler:''' The assembler is a construction unit. It can build sockets, but it cannot assist-build. Slow, little health. Equipped with a radar to detect mines and other cloacked units.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Bit.png</td><td>'''The Bit:''' Your basic attacking unit. Cheap, fast, small, not very much health. Is armed with a SPARCling laser. Can be built by a kernel or a socket.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Byte.png</td><td>'''The Byte:''' A large, strong, and slow attacking unit. Can holds it's own against many bits, as it has lots of health and a powerful gun. More armored when closed. Can plow through bad blocks. The byte has an alternate firing mode, the mine launcher, which throws 5 mines at the cost of much health.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Pointer.png</td><td>'''The Pointer:''' An artillery unit. Its normal shot is not so useful against moving units, but can kill kernels and sockets pretty quickly. Is slow and has little health, so it needs protection. The pointer has an alternate firing mode, the NX Flag, which set a wide area ablaze for a minute, causing constant damage to all units, or buildings within it's range.</td></table>

----

===Hacker units:===
<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96NewHoleLow.png</td><td>'''Security Hole:''' The Hacker kernel equivalent.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Window.png</td><td>'''Window:''' The Hacker socket equivalent.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Obelisk.png</td><td>'''Obelisk:''' This building is a stationary artillery weapon, it can fire an infection shot every 40 seconds (the obelisk has a pink fire on top when it's ready to shoot) that will cover a large area in poison. The poison does a bit of damage (about 1000) and turns any enemy that dies inside the cloud into a Virus. The weapon's range is fairly limited. Best used against stationnary herds of Bits/Bugs.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96NewTrojan.png</td><td>'''Trojan:''' This unit is your constructor as well as radar platform (needed for detecting mines and cloaked units), just like the assembler. It builds all the same stuff as the assembler, except it has the window instead of the socket and the obelisk instead of the terminal.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Virus.png</td><td>'''Virus:''' A crappy little swarm unit. It cannot be built but is produced when killing enemy units with certain weapons. Namely, the Virus, the Worm, and the Obelisk.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96NewBug.png</td><td>'''Bug:''' The Hacker spam unit. The Bug is weaker than the Bit but can sense movement outside of its LOS. It has a stronger weapon and more range but cannot shoot at things behind it or through friendly units and won't take much damage before dying. The mine ability of the old bug has been removed. Instead it can now morph into the Exploit with the deploy button, or the bombard button.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Exploit.png</td><td>'''Exploit:''' This is the new name for the bug cannon. It's a building the Bug morphs into with the deploy or bombard command. The Exploit is a stationary artillery emplacement that does more damage the further the target is away. Even more frail than the Bug, so don't let any foe come near.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96NewWorm.png</td><td>'''Worm:''' The worm is a sneaky assassin, travelling cloacked, then surfacing only to kill many bits at once with its large area of effect weapon, which turn any slain units into virus. The worm large splash damage will damage your own units. However, it does practicaly no damage against other worms or virus. When cloacked, the worm does not automatically attack, you have to give attack orders manually. If you'd rather have your worms auto-attack even when cloacked, set autohold to off. The autohold setting of new worms is inherited from the Security Hole.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96DoS.png</td><td>'''Denial of Service:''' Not an artillery, but close: fire a beam that stun units. For bigger targets it'll take longer to stun them so perform a DDoS (use multiple) to stun them fast. Once the DoS stops firing the target will quickly unfreeze. It moves faster than the pointer but causes a particle trail that can be seen from far away.</td></table>

----

===Network units:===
The network faction is built around mobility, its small factories (Ports) don't produce units openly but instead increment a virtual counter (the Buffer). Packets in the Buffer can be materialized at any teleporter unit (currently that means the Port and the Connection), it's also possible to dematerialize the Packets back into the Buffer by making them enter a teleport.

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Carrier.png</td><td>'''Carrier:''' The base building, like a Kernel or Security Hole.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Port.png</td><td>'''Port:''' The production building. It puts Packets into the Buffer, to materialize them select the Dispatch command. Dispatch will send 12 Packets if available, you can hold ALT when giving the order to make the Port dispatch until the Buffer is empty.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Firewall.png</td><td>'''Firewall:''' This building can cover units (affects friendly units in a certain radius around the target location) in a protective shield for 20 seconds. The shield halves all damage the unit receives and throws the other half back at the attacker.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Gateway.png</td><td>'''Gateway:''' The constructor. It is lightly armed to help against enemy raids.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Packet.png</td><td>'''Packet:''' The basic light spam unit, it's weaker in combat than both competitors but much faster.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Connection.png</td><td>'''Connection:''' Mostly a mobile teleporter (i.e. can dispatch Packets and let them enter like a Port). The Connection has decent armor and an arc beam that can do a lot of damage to single targets and has good range. It can defeat most large units one on one but engaging Bytes will probably result in pointer fire which the Connection cannot withstand and the arc beam is not optimal for engaging swarms.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Flow.png</td><td>'''Flow:''' An air unit. The Flow moves fairly slowly but can of course cross any terrain. It's equipped to attack light targets (spam units and fire support) but it's highly vulnerable to return fire. If you want to use them in open combat give them a meatshield and hope the enemy doesn't field long range units, Pointers, DoSes and Connections make short work of Flows if they hit.</td></table>

----

===All side Units:===

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96BadBlock.png</td><td>'''The Bad Block:''' A tiny wall, built by Assembler/Trojan/Gateway. Blocks small units movement. Do not block shots however. Easily removed by the Debug or simply crushing them with a Byte or Connection.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Mine.png</td><td>'''The Logic Bomb:''' A mine that can be built by the Assembler/Trojan/Gateway. And also launched by Bytes since Div0 2.2. It takes out Bits & Bugs in a single blow, has a decent damage radius, and doesn't chain explode. Use with care, as the blast hurts your own units too. Limited to 32.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96MineBlaster.png</td><td>'''The Debug:''' An easy way to clear an area of all mines and walls, this is a one shot weapon built by the Assembler/Trojan/Gateway.</td></table>

----

==Playing Guide for System:==


Playing Kernel Panic is fairly simple and quickly learned, but can be hard to master and can be very complex. It is recommended that beginners start with play the System faction, as they can be considered the least "gimmicky" of the factions.


One rather effective general strategy for a duel on small maps is to send three to five bits to destroy your enemy's early game units, and, to a lesser degree, for scouting purposes. This is most effective if they started with construction units, as this will likely cripple their plans for an early expansion, and gives you a slight head start. After the initial attack, if your scouting shows that your enemy started with offensive units, build a byte for defense, and place it between your Kernel and the hill. After that, build an assembler and use it to build a socket on one the three closest building locations, which should automatically start producing bits. After this, you should order your assembler to build more sockets on free spots close to it. It is crucial that all sockets' rally points are below them, as bits turning inside a socket will stall production until it is able to exit the factory. It is sometimes wise to repeat the prior process with one or two other assemblers. After this is done, construct about ten bits from your factor, and set your kernel to alternate between building bytes and pointers.


What units you build at your kernel, and what you use them for, is an important factor in winning. As buildings can't be resumed, sending in groups of bits to kill construction units creating buildings can be very effective at stopping expansion attempts. Building too many pointers, will result in them being destroyed by connections, bits and especially worms, due to their stealth. Also, bytes are easily destroyer by and pointers, and exploits. A good general purpose ratio seems to be to queue one byte and one pointer, but this will need adapting as the game develops, and depending on the enemy's play style.

Scouting is important too, as many enemies will leave their factories undefended, and knowing their build, and general unit use can help you in adapting the units you use to better fight them. Note that the Network can instantly spawn packets at any of their ports, or connections with their buffer system, meaning that all their factories should be considered defended. Single bits can be used to scout to find the enemy's current expansion attempts.

When attacking a Byte or Connection with bits, it is important to overwhelm it with large numbers of bits. For bytes, try to exploit a byte's blind spot directly under it, by moving bits into that area. If your byte is under attack, moving it backwards to keep the attacking units in it's shooting arc can help repel the attack. It is not recommended to engage a worm with bits, as it's attack will convert your bits to viruses on the worm's owner's side.


On Marble Madness, there are two main ways paths to victory. The simplest one is to control the hill and use pointers stationed on the hill to destroy the enemy's factories, and kernel. Gaining control of the hilltop will likely not be without resistance, because it requires a decent amount of time for units to reach the top of the hill, meaning most units involved will be spam units from your factories on it, and the fact that it will likely be highly contended. However, if you control it, you have a large advantage over the enemy as you can shell your opponents home base with ease. The other way is around the hill, which can be very effective if you control terrain you can use pointers to great effect. In both strategies, using pointers is the crucial factor. While they are hard to use correctly, they are game-winners as they destroy home bases and enemy units with ease.

----

==Credits:==
- Original concept by Boirunner<br>
- About all the work done by KDR_11k<br>
- Sounds by Noruas<br>
- Minor edits by zwzsg<br>
- Maps by Boirunner, Runecrafter, zwzsg, and TradeMark<br>
- Some LUA interface upgrade based of jK and trepan code<br>

----
Back to [[Games]]
[[Category:Games]]

Kernel Panic

2014-08-22T17:46:24Z

Zwzsg: Made Kernel_Panic_readme.txt link clickable

http://img390.imageshack.us/img390/6289/kernelhd0.png

==Overview:==

''For the latest news and/or assistance, try the [http://springrts.com/phpbb/viewforum.php?f=43'''KP forum'''] or go to #kp when you log onto the lobby.''

'''Kernel Panic''' is a game about computers. Systems, Hackers and Networks wage war in a matrix of DOOM! The only constraints are time and space; unlike other real time strategy games, no resource economy exists in KP.

All units are free in this game, every factory built will be spamming units at all times. You can build more factories, but only on pre-defined areas (geothermal vents). All that remains is pure strategy and tactics.

KP makes for a frantically fast-paced, action-oriented game, with a very unique graphical style.

----

==Download links:==

Current Version of Kernel Panic is 4.6

* <u>Newcomers:</u>
** If you run '''Windows''' (2000,XP,Vista,7):
*** Here you can get a complete installer:
*** http://springfiles.com/spring/game-installers/kernel-panic-installer
*** Use it to install both Spring and Kernel Panic in one go.
*** Then use the shortcuts created in your Start Menu or Desktop.
** If you run '''Linux''':
*** Read the [[SetupGuide]] how to install the Spring engine on Linux systems
*** Get and unzip that file: http://springfiles.com/spring/game-installers/kernel-panic-zip
*** Put the content of /games/ into ~/.spring/games
*** Put the content of /maps/ into ~/.spring/maps
*** Discard the rest.
*** Run Spring directly, a greenish menu should pop up.
*** Click skirmish, duel, easy, run.
*** For multiplayer or advanced options, run SpringLobby

* <u>Experienced Users:</u>
** If you have already the Spring engine (or prefer to install it yourself): Here you can get a zip with the mod file, the maps, and a tiny exe for single player frontend. Unzip into your Spring root folder: http://springfiles.com/spring/game-installers/kernel-panic-zip
** If you are certain you have all the maps and just need a quick link to the mod file itself: http://springfiles.com/spring/games/kernel-panic-mod

----

==Media:==

===Youtube Videos:===

[http://youtube.com/watch?v=doF7owZ0blk&fmt=18 http://i.ytimg.com/vi/doF7owZ0blk/default.jpg]
[http://youtube.com/watch?v=Ug1c19yaZac http://i.ytimg.com/vi/Ug1c19yaZac/default.jpg] [http://youtube.com/watch?v=GAZQhRlt5bU http://i.ytimg.com/vi/GAZQhRlt5bU/default.jpg]
[http://www.youtube.com/watch?v=3q48ys5hFtI&fmt=18 http://i.ytimg.com/vi/3q48ys5hFtI/default.jpg]

----
===Still shots:===

[http://tof.canardpc.com/view/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg http://tof.canardpc.com/preview/076c8061-5505-44a1-96f4-1bb68e6b7ae5.jpg] [http://tof.canardpc.com/view/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg http://tof.canardpc.com/preview/4e607ea7-c428-4ca3-8b70-b12cbf44c18c.jpg] [http://tof.canardpc.com/view/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg http://tof.canardpc.com/preview/23b958ce-d5c9-4b66-b3f9-684db81f9683.jpg]

[http://tof.canardpc.com/view/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg http://tof.canardpc.com/preview/44f4804f-ec99-40f9-a2e2-c3dc0b7617b8.jpg] [http://tof.canardpc.com/view/e5184baf-6c95-4c90-8469-b00a4f092054.jpg http://tof.canardpc.com/preview/e5184baf-6c95-4c90-8469-b00a4f092054.jpg] [http://tof.canardpc.com/view/cbe6dae0-a696-450a-bf22-236043d76511.jpg http://tof.canardpc.com/preview/cbe6dae0-a696-450a-bf22-236043d76511.jpg]

----

==License:==
Extracted from the [http://pastebin.ca/2834721 <code>Kernel_Panic_readme.txt</code>] file:

<pre>
========--------------------------------------------
License:
--------
- The content of the /games/Kernel*.sd7 is Public Domain, save:
/LuaUI/Widgets/kp_buildbar.lua
/LuaRules/Gadgets/autohold.lua
/LuaRules/Gadgets/Burrow.lua
/LuaRules/Gadgets/game_spawn.lua
which are GPL, taken from http://www.caspring.org or http://springrts.com
- The maps Marble Madness and Direct Memory Access are Public Domain
- The maps Major Madness and Speed Balls 16 Way status are unknown
- The maps Central Hub, Corrupted Core, Dual Core, Quad Core were initially CC BY-NC-SA.
Then the author removed the CC cause ( http://cpc.cx/4u3 )
- The Spring engine is GPL, available from http://spring.clan-sy.com
</pre>

== Game Modes:==
By default the aim is to destroy the homebase and all the minifacs of all opposing teams.
<br /><br />
Other "mod options" available are:
* '''King Of The Hill :''' Keeps control of the map center for a given time to win.
* '''O.N.S. :''' Adds shields to buildings, preventing homebase rush.
* '''Save Our Mem :''' Unit leave "leaks" that must be reclaimed.
* '''Color Wars :''' Whoever controls the most territory when timer elapse wins.
* '''Heroes of Mainframe :''' You only control a very buffed up but single unit. Best used with "Pre-placed Minifacs".
* '''Rebalancing formula :''' Let you change the stat of any units of weapons without the hassle of making a mutator.
<br />
For details, read [http://pastebin.ca/2834721 <code>Kernel_Panic_readme.txt</code>] or click [?] next to each mod option in your lobby.
----

==Units and Buildings:==

===System units:===

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Kernel.png</td><td>'''The Kernel:''' You start with one of these. It can build all mobile units in the game. Has rapid auto-heal and lots of health.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Socket.png</td><td>'''The Socket:''' The socket is a factory which can only be built on a geothermal vent. It can solely build bits, and slower than the kernel can. It autoheals, and has a decent amount of health.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Terminal.png</td><td>'''The Terminal:'''(only available in Division Zero) This is a new structure that gets placed on geovents. It can dispatch a nuclear bomber once every 90 seconds that will deal about 16000 damage to a large target area, i.e. it destroys everything except factories. It does much less damage to the kernel and hole. The bomber can strike any position on the map, there is no defense.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Assembler.png</td><td>'''The Assembler:''' The assembler is a construction unit. It can build sockets, but it cannot assist-build. Slow, little health. Equipped with a radar to detect mines and other cloacked units.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Bit.png</td><td>'''The Bit:''' Your basic attacking unit. Cheap, fast, small, not very much health. Is armed with a SPARCling laser. Can be built by a kernel or a socket.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Byte.png</td><td>'''The Byte:''' A large, strong, and slow attacking unit. Can holds it's own against many bits, as it has lots of health and a powerful gun. More armored when closed. Can plow through bad blocks. The byte has an alternate firing mode, the mine launcher, which throws 5 mines at the cost of much health.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Pointer.png</td><td>'''The Pointer:''' An artillery unit. Its normal shot is not so useful against moving units, but can kill kernels and sockets pretty quickly. Is slow and has little health, so it needs protection. The pointer has an alternate firing mode, the NX Flag, which set a wide area ablaze for a minute, causing constant damage to all units, or buildings within it's range.</td></table>

----

===Hacker units:===
<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96NewHoleLow.png</td><td>'''Security Hole:''' The Hacker kernel equivalent.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Window.png</td><td>'''Window:''' The Hacker socket equivalent.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Obelisk.png</td><td>'''Obelisk:''' This building is a stationary artillery weapon, it can fire an infection shot every 40 seconds (the obelisk has a pink fire on top when it's ready to shoot) that will cover a large area in poison. The poison does a bit of damage (about 1000) and turns any enemy that dies inside the cloud into a Virus. The weapon's range is fairly limited. Best used against stationnary herds of Bits/Bugs.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96NewTrojan.png</td><td>'''Trojan:''' This unit is your constructor as well as radar platform (needed for detecting mines and cloaked units), just like the assembler. It builds all the same stuff as the assembler, except it has the window instead of the socket and the obelisk instead of the terminal.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Virus.png</td><td>'''Virus:''' A crappy little swarm unit. It cannot be built but is produced when killing enemy units with certain weapons. Namely, the Virus, the Worm, and the Obelisk.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96NewBug.png</td><td>'''Bug:''' The Hacker spam unit. The Bug is weaker than the Bit but can sense movement outside of its LOS. It has a stronger weapon and more range but cannot shoot at things behind it or through friendly units and won't take much damage before dying. The mine ability of the old bug has been removed. Instead it can now morph into the Exploit with the deploy button, or the bombard button.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Exploit.png</td><td>'''Exploit:''' This is the new name for the bug cannon. It's a building the Bug morphs into with the deploy or bombard command. The Exploit is a stationary artillery emplacement that does more damage the further the target is away. Even more frail than the Bug, so don't let any foe come near.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96NewWorm.png</td><td>'''Worm:''' The worm is a sneaky assassin, travelling cloacked, then surfacing only to kill many bits at once with its large area of effect weapon, which turn any slain units into virus. The worm large splash damage will damage your own units. However, it does practicaly no damage against other worms or virus. When cloacked, the worm does not automatically attack, you have to give attack orders manually. If you'd rather have your worms auto-attack even when cloacked, set autohold to off. The autohold setting of new worms is inherited from the Security Hole.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96DoS.png</td><td>'''Denial of Service:''' Not an artillery, but close: fire a beam that stun units. For bigger targets it'll take longer to stun them so perform a DDoS (use multiple) to stun them fast. Once the DoS stops firing the target will quickly unfreeze. It moves faster than the pointer but causes a particle trail that can be seen from far away.</td></table>

----

===Network units:===
The network faction is built around mobility, its small factories (Ports) don't produce units openly but instead increment a virtual counter (the Buffer). Packets in the Buffer can be materialized at any teleporter unit (currently that means the Port and the Connection), it's also possible to dematerialize the Packets back into the Buffer by making them enter a teleport.

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Carrier.png</td><td>'''Carrier:''' The base building, like a Kernel or Security Hole.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Port.png</td><td>'''Port:''' The production building. It puts Packets into the Buffer, to materialize them select the Dispatch command. Dispatch will send 12 Packets if available, you can hold ALT when giving the order to make the Port dispatch until the Buffer is empty.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Firewall.png</td><td>'''Firewall:''' This building can cover units (affects friendly units in a certain radius around the target location) in a protective shield for 20 seconds. The shield halves all damage the unit receives and throws the other half back at the attacker.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Gateway.png</td><td>'''Gateway:''' The constructor. It is lightly armed to help against enemy raids.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Packet.png</td><td>'''Packet:''' The basic light spam unit, it's weaker in combat than both competitors but much faster.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Connection.png</td><td>'''Connection:''' Mostly a mobile teleporter (i.e. can dispatch Packets and let them enter like a Port). The Connection has decent armor and an arc beam that can do a lot of damage to single targets and has good range. It can defeat most large units one on one but engaging Bytes will probably result in pointer fire which the Connection cannot withstand and the arc beam is not optimal for engaging swarms.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Flow.png</td><td>'''Flow:''' An air unit. The Flow moves fairly slowly but can of course cross any terrain. It's equipped to attack light targets (spam units and fire support) but it's highly vulnerable to return fire. If you want to use them in open combat give them a meatshield and hope the enemy doesn't field long range units, Pointers, DoSes and Connections make short work of Flows if they hit.</td></table>

----

===All side Units:===

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96BadBlock.png</td><td>'''The Bad Block:''' A tiny wall, built by Assembler/Trojan/Gateway. Blocks small units movement. Do not block shots however. Easily removed by the Debug or simply crushing them with a Byte or Connection.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96Mine.png</td><td>'''The Logic Bomb:''' A mine that can be built by the Assembler/Trojan/Gateway. And also launched by Bytes since Div0 2.2. It takes out Bits & Bugs in a single blow, has a decent damage radius, and doesn't chain explode. Use with care, as the blast hurts your own units too. Limited to 32.</td></table>

<table><td>http://zwzsg.luckz.de/pics/spring/icons/96x96MineBlaster.png</td><td>'''The Debug:''' An easy way to clear an area of all mines and walls, this is a one shot weapon built by the Assembler/Trojan/Gateway.</td></table>

----

==Playing Guide for System:==


Playing Kernel Panic is fairly simple and quickly learned, but can be hard to master and can be very complex. It is recommended that beginners start with play the System faction, as they can be considered the least "gimmicky" of the factions.


One rather effective general strategy for a duel on small maps is to send three to five bits to destroy your enemy's early game units, and, to a lesser degree, for scouting purposes. This is most effective if they started with construction units, as this will likely cripple their plans for an early expansion, and gives you a slight head start. After the initial attack, if your scouting shows that your enemy started with offensive units, build a byte for defense, and place it between your Kernel and the hill. After that, build an assembler and use it to build a socket on one the three closest building locations, which should automatically start producing bits. After this, you should order your assembler to build more sockets on free spots close to it. It is crucial that all sockets' rally points are below them, as bits turning inside a socket will stall production until it is able to exit the factory. It is sometimes wise to repeat the prior process with one or two other assemblers. After this is done, construct about ten bits from your factor, and set your kernel to alternate between building bytes and pointers.


What units you build at your kernel, and what you use them for, is an important factor in winning. As buildings can't be resumed, sending in groups of bits to kill construction units creating buildings can be very effective at stopping expansion attempts. Building too many pointers, will result in them being destroyed by connections, bits and especially worms, due to their stealth. Also, bytes are easily destroyer by and pointers, and exploits. A good general purpose ratio seems to be to queue one byte and one pointer, but this will need adapting as the game develops, and depending on the enemy's play style.

Scouting is important too, as many enemies will leave their factories undefended, and knowing their build, and general unit use can help you in adapting the units you use to better fight them. Note that the Network can instantly spawn packets at any of their ports, or connections with their buffer system, meaning that all their factories should be considered defended. Single bits can be used to scout to find the enemy's current expansion attempts.

When attacking a Byte or Connection with bits, it is important to overwhelm it with large numbers of bits. For bytes, try to exploit a byte's blind spot directly under it, by moving bits into that area. If your byte is under attack, moving it backwards to keep the attacking units in it's shooting arc can help repel the attack. It is not recommended to engage a worm with bits, as it's attack will convert your bits to viruses on the worm's owner's side.


On Marble Madness, there are two main ways paths to victory. The simplest one is to control the hill and use pointers stationed on the hill to destroy the enemy's factories, and kernel. Gaining control of the hilltop will likely not be without resistance, because it requires a decent amount of time for units to reach the top of the hill, meaning most units involved will be spam units from your factories on it, and the fact that it will likely be highly contended. However, if you control it, you have a large advantage over the enemy as you can shell your opponents home base with ease. The other way is around the hill, which can be very effective if you control terrain you can use pointers to great effect. In both strategies, using pointers is the crucial factor. While they are hard to use correctly, they are game-winners as they destroy home bases and enemy units with ease.

----

==Credits:==
- Original concept by Boirunner<br>
- About all the work done by KDR_11k<br>
- Sounds by Noruas<br>
- Minor edits by zwzsg<br>
- Maps by Boirunner, Runecrafter, zwzsg, and TradeMark<br>
- Some LUA interface upgrade based of jK and trepan code<br>

----
Back to [[Games]]
[[Category:Games]]