Starbase wiki - User contributions [en]

Robotic arms

2024-07-03T22:12:02Z

Scrapper 101: Added the ClosedAlphaContent tag, as it was missing beforehand.

{{ClosedAlphaContent}}

{{Otherlang2
|de=Robot_arms:de
|fr=Robot_arms/fr
|zh-cn=机械臂
|ru=Роботизированные манипуляторы
|ua=Роботизовані маніпулятори
|jp=ロボットアーム
}}{{SB Infobox Begin
|{{SB Infobox Header
|image=[[Image:Robot_arms.png]]
|factionLogo=
|caption=
|name=
|border=none
}}

|{{SB Infobox Device General Information
|type=Utility machinery
|function=Automation
|availability=
|size=<ul><li>156×156×432 cm ''(small)''</li><li>156×156×720 cm ''(med)''</li></ul>
|mass=<ul><li>9,236.2 kg ''(small)''</li><li>14.382.2 kg ''(med)''</li></ul>
|volume=<ul><li>928.26 kv ''(small)''</li><li>1445.45 kv ''(med)''</li></ul>
|corrosionResistance=300
|primaryMaterial=400
|suppressUnitsKg=1
|suppressUnitsKv=1
}}

|{{SB Infobox Device IO
|electricIn=Approx. 5-10 e/s
|electricOut=
|coolantIn=
|coolantOut=
|propellantIn=
|propellantOut=
|fuelIn=
|fuelOut=
|sockets=
|YOLOLchips=
|modInterfaces=1
|deviceInterfaces=1
}}

|{{SB Infobox Device Construction
|overrideHeader=
|aegisium=
|ajatite=
|arkanium=
|bastium=100%
|charodium=
|corazium=
|exorium=
|haderite=
|ice=
|ilmatrium=
|karnite=
|kutonium=
|lukium=
|merkerium=
|nhurgite=
|oninum=
|surtrite=
|tengium=
|ukonium=
|valkite=
|vokarium=
|xhalium=
}}
}}

Robot arms are a series of mechanical joints that enable a wide variety of automated tasks, such as ship-building [[factories]] and assembly lines. Each segment can be controlled individually through a player's [[Universal tool|universal tool]], or by a device such as a [[Levers|lever]], but these movements can also be computed automatically. Robot arms have a special tool-head at their end, which allows a user to equip [[Tools|tools]] to perform specific tasks. They can also accept a standard [[Hardpoints|hardpoint]] onto the tool-head, which enables the use of such devices as a [[Range finder|rangefinder]] or any of a variety of weapons.

== Basic information ==

* Robot arms consist of two types of joints, revolute and prismatic, which can be stacked together to form articulated arms of varying complexity.
** The basic arm configuration has one or two telescoping segments, and an end segment with a revolute joint. More arms or tool holders can be attached to this revolute joint.
* The base of any arm combination has to be attached to a special turret base joint.
** There are four different sizes of the basic arm.

== Device fields ==

{|class="wikitable"
! YOLOL field
! description
! range
|-
! '''TargetArmLength'''
| Telescoping arm target length
| [0,100]: percent of maximum extension
|-
! '''CurrentArmLength'''
| Current arm length updated during arm movement
| [0,100]: percent of maximum extension
|-
! '''EndPosition'''
| Extension at maximum arm length
|
|-
!'''StartPosition'''
| Extension at minimim arm length
|
|-
!'''TargetVelocity'''
| Target velocity of telescoping movement
|
|}

{|class="wikitable"
! YOLOL field
! description
! range
|-
! '''TargetArmAngle'''
| Rotating joint target angle
| [-180,180]: degrees
|-
! '''CurrentArmAngle'''
| Rotating joint current angle updated during arm rotation
| [-180,180]: degrees
|-
! '''MaxRotation'''
| Maximum rotation
|
|-
!'''MinRotation'''
| Minimum rotation
|
|-
!'''TargetVelocity'''
| Target velocity of rotation
|
|}

To learn more about how to use fields, consult these wiki pages:
* [[Universal tool|Universal Tool]]
* [[Data networks|Data networks]]
* [[YOLOL|YOLOL]]

== Videos ==
{{#evt:
service=youtube
|id=https://www.youtube.com/watch?v=LDy9Kt3KuGE
}}

{{#evt:
service=youtube
|id=https://www.youtube.com/watch?v=Borzb8ipqZ8
}}



[[Category:Devices and machines|Robot arms]]

Device fields

2024-07-03T22:06:53Z

Scrapper 101: Robot arms are no longer in game, they have not been for a while now.

{{Otherlang2
|en=Device_fields
|de=Device_fields:de
|fr=Device_fields:fr
|zh-cn=设备参数
}}
Device fields are used to control and read the status of [[Devices_and_machines|devices]] connected to a [[Data_networks|data network]]. They can be read or set by the [[Universal tool]], [[YOLOL Chip]], or by other devices on the same network.

= List of Device Fields =
== Base mounted devices ==

===[[Battery]]===
{{#lsth:Battery|Device fields}}

===[[Cargo beam|Cargo beam]]===
{{#lsth:Cargo beam|Device fields}}

===[[Fixed mount|Fixed mount]]===
{{#lsth:Fixed mount|Device fields}}

===[[Generator (Assembly)|Generator]]===
{{#lsth:Generator|Device fields}}

===[[Hinges|Hinges]]===
{{#lsth:Hinges|Device fields}}

===[[Mounted weapons]]===
{{#lsth:Mounted weapons|Device fields}}

===[[Radio transmitters|Radio transmitters]]===
{{#lsth:Radio transmitters|Device fields}}

===[[Range finder|Range finder]]===
{{#lsth:Range finder|Device fields}}

===[[Robot arms|Robot arms (Outdated, no longer in game)]]===
{{#lsth:Robot arms|Device fields}}

===[[Thrusters|Thrusters]]===
{{#lsth:Thrusters|Device fields}}

===[[Turntable|Turntable]]===
{{#lsth:Turntable|Device fields}}

== Interactables ==

=== [[Buttons]] ===
{{#lsth:Buttons|Device fields}}

===[[Lamps|Lamps]]===
{{#lsth:Lamps|Device fields}}

===[[Levers|Levers]]===
{{#lsth:Levers|Device fields}}

===[[Propellant tank|Propellant]]===
{{#lsth:Propellant tank|Device fields}}

== Rail devices ==

===[[Rail mover|Mover]]===
{{#lsth:Rail mover|Device fields}}

===[[Rail relay|Relay]]===
{{#lsth:Rail relay|Device fields}}

===[[Rail sensor strip|Sensor strip]]===
{{#lsth:Rail sensor strip|Device fields}}

===[[Rail trigger|Trigger]]===
{{#lsth:Rail trigger|Device fields}}

== Screens ==

=== [[Information screen]] ===
{{#lsth:Information screen|Device fields}}

===[[Modular displays|Modular displays]]===
{{#lsth:Modular displays|Device fields}}

== Utility Devices ==

===[[Cargo lock frame (Assembly)]]===
{{#lsth:Cargo lock frame (Assembly)|Device fields}}

===[[Flight control unit|Flight control unit]]===
{{#lsth:Flight control unit|Device fields}}

===[[Main flight computer|Main flight computer]]===
{{#lsth:Main flight computer|Device fields}}

===[[Mining laser (Assembly)|Mining laser]]===
{{#lsth:Mining laser|Device fields}}

===[[Network relay]]===
{{#lsth:Network relay|Device fields}}

===[[Tractor beam (Assembly)|Tractor beam]]===
{{#lsth:Tractor beam|Device fields}}

== YOLOL devices ==

===[[YOLOL Chip]]===
{{#lsth:YOLOL Chip|Device fields}}

===[[Chip socket]]===
{{#lsth:Chip socket|Device fields}}

===[[Memory chip]]===
{{#lsth:Memory chip|Device fields}}

===[[Modular device rack]]===
{{#lsth:Modular device rack|Device fields}}

YOLOL Tricks

2024-07-03T22:00:50Z

Scrapper 101: Talk about professional chips being impossible to obtain is outdated information, updated with new info.

{{Otherlang2
|ru=Фишки YOLOL
|ua=Особливості YOLOL
}}

[[YOLOL]] is a rather constrained language. The line and chip length limits and slow execution speed incentivize clever shortcuts. The small math library and limited operation space require building larger operations from smaller building blocks. To those ends, this page serves to catalog a variety of things you can accomplish with YOLOL that might not be obvious from the main [YOLOL] documentation.

== General tips ==
Anything that accept numbers also accept something that represents a number. For example if you wanted to use a button to turn something on instead of doing
if :Button then :Device=1 else :Device=0 end
You can achieve the same thing by simply doing
:Device=:Button
":Button" is actually just a value, most buttons are either 0 (not clicked) or 1 (clicked) so setting :Device to be :Button is really no different from setting it to 0 and 1, its just that our number is now "dynamic" in the sense that it is directly tied to the value of the :Button.
Understanding this can be used for many things, we can incorporate this into our goto# by simply doing something like "goto:Button+1" which will goto1 if :Button is 0 and goto2 if :Button is 1.
So that means we can both use something that has the value of a number instead of a number as well as carry out math to determine what the number actually should be.
Assume we want :Device to get the value 100 if :Button is pressed, and have the value 0 if it is not pressed. We can do that like this:
:Device=:Button*100
It is also useful to know that if a line contains a runtime error then this line will be skipped entirely. This means you can skip lines by dividing by 0. Just directly dividing by 0 is of course not helpful but if we use a "dynamic value" in the sense that we are dividing by a variable, such as :Button, that means we sometimes will have a line containing no errors so it runs and sometimes it contains an error and will be skipped.
goto2/:Button
If our :Button is 0 this is dividing by zero so the entire line is skipped, if :Button is 1 we are instead dividing 2 with 1 which returns 2.

=== Need more decimals? ===
YOLOL supports 3 decimal places, 1.234, which may cause you some issues. If your final number however isn't the one that needs a higher amount of accuracy than this but rather the requirement for more than 3 decimals is somewhere in the equation giving you your number then you can solve this issue by multiplying your numbers used during the equation and then dividing the final number. For example if you need to multiply x with 1.2345 and .234 simply is not accurate enough you could instead multiply x with 12.345 and then divide the result by the same amount, in this case 10.

=== Don't have professional chips? ===
Trigonometric functions are locked behind [[Professional YOLOL chip|professional chips]], which resources to build may be difficult to obtain. Here is a solution for those not wanting to use them:

polynomial approximations for sin/cos functions '''''(!! for sin/cos make sure -180<:x<180 !!)'''<ref>[https://www.reddit.com/r/starbase/comments/puz32d/extremely_unprofessional_sinusoidal_approximations/ Extremely unprofessional sinusoidal approximations]</ref>

'''sin(x):'''

<code>i=:x/180 :sinx=4*i*(1-ABS i)</code>

'''cos(x):'''

<code>i=:x/180 i+=.5-2*(i>.5) :cosx1=4*i*(1-ABS i)</code> (using the cos(x)=sin(x+90) identity)

<code>i=:x/180 :cosx2=i^2*(-6+4*ABS i)+1</code> (standalone derivation; slightly shorter but different error bars so ymmv when using it with sin)

'''asin(y):'''

<code>:asiny=40*:y^3+50*:y</code>

'''acos(y):'''

<code>:acosy=-40*:y^3-50*:y+90</code>

'''atan(y):'''

<code>i=:y/SQRT(1+:y^2) :atany=40*i^3+50*i</code> (using the asin identity)

== String Manipulation ==
{| class="wikitable"
|-
! Nickname !! Code !! Explanation
|-
| If Empty || '''string-(string+otherstring)''' || If '''otherstring''' is empty then this evaluates to an empty string, else it evaluates to '''string'''
|-
| Select || '''a="foo1" b="bar2" c="meh3" x=2 s=a+b+c-x-a-b-c s=="bar"''' || One string from a set can be selected by concatenating them with indices, then removing an index, then removing all the strings which will fail for the un-indexed one. If one index is a substring of another then the order of the strings will matter.
|-
| Contains || '''s="~meh~foo~bar~" t="foo" c=s!=s-("~"+t+"~")''' || Evaluates to 1 if '''t''' is present in test set '''s''', and 0 if not Alternatively, if the values in the string to test ('''s''') are arranged in alphabetically descending order, '''s>s-("~"+t+"~")''' can also be used. For non-distinct values, (for example searching for '''"tin"''' in the string '''"non-distinct values"''') the delimiter ('''"~"''') can be omitted. Depending on the values that can occur in '''s''' and '''t''', some or all of the delimiters ('''"~"''') can be omitted, or changed into other values, such as numbers.
|}

== Number tricks ==
{| class="wikitable"
|-
! Nickname !! Code !! Explanation
|-
| Not || '''0^b''' '''1-b''' '''b==0''' || Used to negate a '''0''' or '''1''' value. '''0^b''': Does not need parenthesis when used in a multiplication. Works any non-negative input value, not only '''0''' and '''1'''. Requires an Advanced or Professional chip '''1-b''': Works '''only''' with '''0''' and '''1'''. Works on all chips. '''b==0''': Works with all input values, not only '''0''' and '''1'''. Works on all chips.
|-
| Select || '''a+(b-a)*s''' '''a*0^s+b*s''' || Select one of '''a''' or '''b''' based on a '''0''' or '''1''', '''s''' select signal. Equivalent to '''if s then result=b else result=a end'''
|-
| Hex || '''0xHEXDIGITS''' || write a number in base 16, digits from 0-9 and a,b,c,d,e,f; works only in [[YOLOL]]'''
|-
| Scientific || '''AeB''' || A*10^B; works in [[YOLOL]] and when written by the U-tool in device fields'''
|}

==Skipping IF Statements==
If statements can in many cases be avoided which can save us a considerable amount of characters, as we will no longer waste characters on "if", "then", and "end". Multiplication (*) works as a replacement for AND while addition (+) works as a replacement for OR in many scenarios.

if :ButtonState==1 and :DoorState==1 then :LampOn=1 end

While this if statement could be made shorter by skipping out on unnecessary spaces and removing the unnecessary "==1" part of the comparison we could also skip out on using an if statement entirely.

:LampOn=:ButtonState*:DoorState

This will assign LampOn the value of ButtonState multiplied with DoorState. if both are 1 that returns a 1, if either one (or both) of them is zero then it returns zero, making this a functional replacement for an if statement containing AND. We could do the same thing for OR by instead using addition.

Using math to avoid the necessity of IF statements works in many cases and tend to be easy to do when the values involved are 0 and 1, such as for anything which is either on or off. If you need to shorten down your code for one reason or the other this is a good venue to explore. Lets finish this section with a slightly beefier example of this in use.

if :One and :Two then :LampOn=1 goto2 end if :One<1 and :Three then :LampOn=1 end

Here we are checking if :One and :Two are true (equal to 1) and if they are we change :LampOn to 1 and move to line 2. IF they are not we check if One is False (0) and Three is true (1) and in that case we still turn on the lamp.
However if we skip out on using if statements to approach this we could shorten it to this:

:LampOn=(:One*:Two)+((1-:One)*:Three)

Keep this in mind when writing your yolol and you will find yourself saving a lot of characters and fitting more things on the same line and even more things on the same chip!

When you need to disable whole script with one button and squeeze-in some variables initialisation:
if :Button != 1 then goto1 end a = 123 b = 456 c = 789
This can be shortened to:
a=123 b=456 c=789 goto1+:Button
When '''Button''' disabled '''goto''' will jump to line 1, otherwise it will jump to line 2.

== Code Golf ==
If you want to develop readable code and only shorten it for deployment, consider using [https://github.com/dbaumgarten/yodk yodk] or [https://github.com/martindevans/Yolol Yololc] which can minify your code for you.

Shortening identifiers to one character saves bytes, use '''f=b''' rather than '''foo=bar'''.

Reassigning fields to identifiers saves bytes if you use them more than a few times. '''f=:f f f f f f f f f''' is shorter than ''':f :f :f :f :f :f :f :f '''.

Most whitespace is optional. You only actually need a space when code would be ambiguous without it. Spaces can almost always be omitted before ''':''', after '''if''' or '''then''' or '''end''', between a number or symbol and a letter, and in various other places.

[[Category:Networks|YOLOL]]

Common YOLOL

2024-07-03T21:58:49Z

Scrapper 101: Edits a lot of the generator script information and examples to let new players ( and pre-exiting ones ) know that generator scripts may or may not work on ships anymore.

A collection of small common scripts meant to be easily copied and understood for the [[YOLOL|YOLOL]] beginners.

''This page is a "Work In Progress". Don't hesitate to contribute! Just make sure to respect the following rules:
* Avoid complex codes. As said, These must be easily understood by beginners. If you can't simplify your scripts, please add some comments to explain the most technical parts.
* Avoid as possible to modify the [[Device fields|device fields]]. If necessary, it must be specified which field has to be renamed (left column) and/or set to a given value (right column). ''

==[[Flight control unit|Flight Control Unit]]==

===Single Forward/Backward Lever===
Requires a center lever bound to '''"FcuForward"'''. ''Note: You can easily modify the default regular lever from most prebuilt ships and cockpit modules to be used as a center Lever. Just change the '''"LeverMinOutput"''' value from 0 to -100. Also don't forget to modify your control binds ("V" on keyboard by default).''

:FcuBackward=-:FcuForward goto1

===Speed Limiter===
Requires to modify the lever bound to '''"FcuForward"''' which shall be renamed '''"Fwd"''' and another regular lever with '''"LeverState"''' renamed '''"Limiter"'''. This script allow you to set a maximum forward speed to your ship, which is useful when you need more accurate movements (e.g. while mining or docking).

:FcuForward=:Fwd/100*:Limiter goto1

''Note: If you already modified your '''"FcuFoward"''' lever to be used as a '''"Single Forward/Backward Lever"''' (see above), you can use the '''"Backward"''' lever made useless as the '''"Limiter"''' lever. Just make sure you have '''"FcuForward"''' renamed '''"FwdBwd"''' instead so you can modify forward and backward thrust individually. This way your YOLOL scripts should be written as follows:''

:FcuForward=:FwdBwd/100*:Limiter goto1

:FcuBackward=-:FwdBwd goto1

===Turtle Mode===
Similar to the previous script but with a button instead of a lever. '''"ButtonState"''' should be renamed '''"Turtle"''' and '''"ButtonStyle"''' set to '''"1"'''. In addition set the '''"ButtonOffStateValue"''' to '''"100"''' and the '''"ButtonOnStateValue"''' to the desired speed reduction. For example having '''"30"''' means 30% of maximum speed when the button is active.

:FcuForward=:Fwd/100*:Turtle goto1

===Gradual Generator Script===
*Please Note That Due To Some Not So Recent Changes, Most Generator Scripts May Not Work Due To Generators Having To "Spool Up" Before Providing Enough Power To Not Drain The Battery(s) So Make Sure Your Ship Either Has Enough Batteries To Keep Running, Or The Script You Are Using Is Advanced Enough To Keep Your Ship Going.*

This script makes the fuel rate limit of the fuel chamber inversely proportional to the charge level of the batteries.

:Generator=100-:Battery_1/100 goto1

Alternatively, the script below will keep the batteries fuller by setting the fuel rate limit to its maximum when batteries are below 90% of charge.

:Generator=1000-:Battery_1/10 goto1

===Flagged Generator Script===
This script set the fuel rate limit to 25% (just enough to supply 2 box thrusters with a bit of spare charge) if the level of the batteries is below 9999 and adding 50% if below 5000. 0.001% is enough fuel rate to let the generator "sleep" when the ship stand still and the batteries are full.

:Generator=25*(:Battery_1<9999)+50*(:Battery_1<5000)+0.001 goto1

===Advanced Generator Script===
This script is tweakable to your ship configuration. Field names are those of the Laborer Module, except for the '''"Generator"''' button which should be renamed '''"PWR"''' so the script can control the fuel rate while the button still being functional. Optionally you can add an override lever with '''"LeverState"''' renamed '''"PWR"''' as well.

MaxBattery=20000 // total capacity
LowBattery=0.99*MaxBattery // start charging below 99%
MinBattery=0.20*MaxBattery // max charge rate below 20%
MaxGenerator=100 // max fuel rate
MinGenerator=2 // min fuel rate (near 100% charge)
h=MaxGenerator c=MinGenerator // auxiliary variables,
f=MaxBattery l=LowBattery e=MinBattery // no need to change these
r=(h-c)/(f-e) z=h-r*l a=r*(f-l) // reboot: remove "goto9" briefly
y=:PWR-z-r*(:Battery_1+:Battery_2)+c*(y>c)+a*(y>0) :Generator=y goto9

It is assumed that the following device fields are set as explained (''Note: The "PWR" button is already set up in the Laborer Module''):

{| class="wikitable"
! Ship Part !! Field Name !! Set Field value
|-
| "PWR" Button || ButtonOnStateValue|| 100
|-
| "PWR" Button || ButtonOffStateValue|| 0
|-
| "PWR" Button || ButtonStyle || 1
|-
| "PWR" Lever (optional) || LeverMinOutput || 0
|-
| "PWR" Lever (optional) || LeverMaxOutput || 200
|-
| "PWR" Lever (optional) || LeverCenteringSpeed || 0
|}

==[[Material point scanner|Material Point Scanner]]==

===Material Point Scanner Script===
Requires two displays for '''"Material"''' and '''"Volume"''', two buttons to toggle the '''"Active"''' and '''"Scan"''' fields of the scanner, and a third button with '''"ButtonState"''' renamed '''"Next"''' and '''"ButtonStyle"''' set to '''"1"'''.

:Index=(:Index+:Next)*(:Index<:ScanResults) :Next=0
:Material=:Material :Volume=:Volume goto1

===Automatic Material Point Scanner Script===
This is a modified version of the above script so it can be used when the scanner is '''"Active"''' without the need of any additional buttons.
''Note: launching a new scan reinitialize the index to '''"0"'''.''

:Scan=1
//Pause
:Index=Next
Next=(Next+1)*(Next<:ScanResults)
:Material=:Material :Volume=:Volume goto1

==[[Mining laser|Mining Laser]]==
''Note: [[Mining laser|Mining Lasers]] were updated to have an activation cost, which is why pulsing lasers is not economic anymore.''
===Pulsed Mining Laser===
Requires a button with '''"ButtonState"''' renamed '''"Mining"''' and '''"ButtonStyle"''' set to '''"1"'''. Reduces power consumption by continuously switching mining laser "On" and "Off" while the button is active.

:MiningLaserOn=(1-:MiningLaserOn)*:Mining goto1

===Configurable Pulsed Mining Laser===
Similar to the previous script but with configurable timers for the "On" and "Off" phases of the laser.
''Note: Each phase is calculated in a number of YOLOL "tick" (0.2sec). So in the example, the "On" phase last 2*0.2=0.4sec and the "Off" phase 3*0.2=0.6 sec, which makes the power comsumption just a bit lower than the power production of a regular generator module (= one fuel chamber and three generator units, all in tier 1).''

On=2 Off=3 :MiningLaserOn=(T<On)*:Mining T++ T*=T<(On+Off) goto1

==[[Navigation receivers|Navigation Receiver]]==

===Received Signal Display===
Requires a text panel with '''"PanelValue"''' renamed '''"Nav"'''.

if :SignalStrength>0 then goto2 else :Nav="No Signal" goto1 end
:Nav=:Message+"\n"+(1000000-:SignalStrength)/1000+"km" goto1

==[[Ore collector|Ore Collector]]==

===Mining Laser/ Ore Collector Swapping Power===
Requires a button with '''"ButtonState"''' renamed '''"Collecting"''' and '''"ButtonStyle"''' set to '''"1"'''. Reduces power consumption by switching ore collector "On" only if the button is active And the mining laser is "Off". ''Note: this script works best alongside the "Pulsed Mining Laser" scripts.''

:ToggleOn=(1-:MiningLaserOn)*:Collecting goto1

==[[Ship transponder|Ship Transponder]]==

===Outside Safezone Warning===
Requires an active transponder and either a warning button or a safety lid button. The button blink whenever you're outside of the safe zone. ''Note: the button needs to be active in order to blink.''

:ButtonEnableBlink=1-:InsideSafeZone goto1

===Stations Building Availability===
Same as the previous one, but the button blink wherever you're allowed to build a station.

:ButtonEnableBlink=:StationsAllowed goto1

[[Category:Networks|Common YOLOL]]

YOLOL

2024-07-03T21:45:46Z

Scrapper 101: Removal of a lot of "Runtime errors" as they work in game, some are left as I haven't tested them yet, no need to confuse players.

{{Otherlang2
|en=YOLOL
|de=YOLOL:de
|fr=YOLOL:fr
|ru=YOLOL:ru
|ua=YOLOL:ua
|jp=YOLOL:jp
|zh-cn=YOLOL语言
}}

== Summary ==

{{#evt:service=youtube|id=https://www.youtube.com/watch?v=7lXK6_bktUk|alignment=center}}

YOLOL is a programming language used to control and manage electrical [[Devices and machines|devices]]. 
The code is written on lines in [[YOLOL Chip|YOLOL chips]] which are then inserted into [[Chip socket|chip sockets]], that read and relay their messages. 
The programming language enables the programming and controlling of almost any device within the known universe.

== Basic information ==

=== How it works ===
The code is written to and executed from programmable chips, and can be used to both monitor and control electrical [[Devices and machines|devices]] connected to a [[Data networks|data network]]. 
Lines of code are executed in sequence from top to bottom, repeating the cycle of the chip after the last line has been executed, unless the script includes programmed instructions for specific line changes or stopping the execution completely.

To put it simply:

# Code execution starts from line 1
# After reading line 1, it proceeds to the next line based on the chip's time interval
# The process is then repeated for the lines 2, 3, 4... etc.
# The chip will begin executing line 1 again after the last line has been executed (unless the last line contains a goto statement or execution has been paused)

So blank lines still use 0.2 seconds and can be used as a brief execution delay. (lines with only a comment are effectively the same as a blank line.)

=== Limitations ===

* Lines take 0.2 seconds to execute.
* A line can contain a maximum of 70 characters (comments and spaces included).*
* Some functions only work on specific YOLOL chips.

*Note that because of this some examples shown below might not work in-game.

== Command references ==

=== Case insensitive ===

The programming language is fully case '''insensitive'''. 
This means that the following two example scripts function identically to each other:

if '''ButtonState''' == 1 then '''DoorState''' = 1 end

IF '''buttonstate''' == 1 THEN '''doorstate''' = 1 END
* Both scripts set the '''doorstate''' into 1, if '''buttonstate''' value is 1.
* The characters in the programming language can be written in either lowercase or uppercase letters.
** They are still parsed as case insensitive.
** This way it's possible to have the code look a bit more organized.

=== Variables ===

* The variables in the programming language are weakly typed (don't enforce type validity), and support two data types: '''Fixed-point decimals''' (up to 0.001 precision) and '''Strings''' (up to 1024 characters long).
** To put it simply, the variables can either be introduced as strings or numbers, ignoring the earlier variable type if the previous type is not identical, without causing an error.
* Each variable is always of a single type, though it will be implicitly converted when required.
* The default value of an uninitialized variable is 0, and null values are not supported.
* True/False are numerical values of non-0 and 0.
** True != 0
** False == 0

Assigning a value to a variable always converts the variable to the newly assigned value's type.

'''Example:'''

ultimateAutopilot= 128.643
* This results in the variable '''ultimateAutopilot''' containing a numeric value of 128.643

ultimateAutopilot= "Error prone"
* This results in the variable '''ultimateAutopilot''' to be a string variable "''Error prone''", and numeric value of 128.643 is removed.

==== Decimals ====

Numeric values in the programming language are 64-bit fixed-point decimals. 
The variables hold decimal numbers up to three decimal accuracy. 
As a result, the maximum value range (even during operations) is [-9223372036854775.808, 9223372036854775.807]

pieVariable= 3.142
* The above script assigns a numeric value of 3.142 to the variable '''pieVariable'''.
** Supplying more precise values than the variables can store works, but doesn't affect the end result.

notPieVariable= 0.5772156649
* The above script attempts to assign a numeric value of 0.5772156649 to the variable '''notPieVariable'''.
* The end result however is notPieVariable == 0.577
** Here, the more precise values are cut, leaving only three decimals behind.

==== Strings ====

To specify a string literal in the programming language, the desired string value must be surrounded with double quotation marks.
Strings can hold up to 127 characters.

badRobots= "saltberia"
* This script assigns the string value of "''saltberia''" to the variable '''badRobots'''.

==== Device fields / External variables ====

External variables and device fields can be used in the programming language with the following syntax: 
* ''':variableName'''
**'''variableName''' being the configured device field id.
A colon prefix ''':''' is used to tell the script that an external variable is being accessed, instead of using one that may or may not be declared or used in the script. 
A programmable [[YOLOL Chip|chip]] that is connected to a [[Devices and machines|device]] has access to all the devices in the same [[Data networks|network]]. 
It can then modify and listen to any device fields it has access to. 

if ''':ButtonState''' == 1 then ''':DoorState''' = 1 end
* The script above will send the value of 1 to any devices listening to the device field '''DoorState''' if the value of '''ButtonState''' is 1 in the data network.

==== Naming Limitations ====
Currently variables containing keywords such as '''if''' or '''end''' can be parsed incorrectly, and must be avoided.

==== Memory Chips and Relays ====

[[YOLOL memory chip|Memory Chips]] provide 10 device fields that aren't tied to the function of devices and can be used to share variables and their values between multiple [[YOLOL_Chip|YOLOL Chips]]. 
In a [[Memory_relay|Memory Relay]] they can also be used to copy data from one device field to another, which allows
* separation of networks e.g. for keeping the data networks less noisy and smaller
* a combination of shortened variable names in yolol and long variable names in displays e.g. for cockpit interfaces

== Operators and commands ==

Note that the available operators may be limited by the type of the programmable [[YOLOL Chip|chip]]. 
Basic chips have a limited selection of functions while more advanced ones can perform more complex operations natively.

=== Basic arithmetic and assignment operators ===

{| class="wikitable"
|-
! Operation || Numeric operation || String operation || Chip availability
|-
| A + B || Addition || String A is appended by String B. || All
|-
| A - B || Subtraction || The last appearance of String B in String A is removed from String A. || All
|-
| A * B || Multiplication || String A is multiplied by String B. || All
|-
| A / B || Division || Divides String A by String B. || All
|-
| A ++ || PostIncrement (A=A+1) || Appends a space to String A. Evaluates to the original value. || All
|-
| A -- || PostDecrement (A=A-1) || Removes the last character of the string. Results in runtime error when trying to remove "". Evaluates to the original value. || All
|-
| ++ A || PreIncrement (A=A+1) || Appends a space to String A. Evaluates to the modified value. || All
|-
| -- A || PreDecrement (A=A-1) || Removes the last character of the string. Results in runtime error when trying to remove "". Evaluates to the modified value. || All
|-
| A = B || Assignment (Variable A is set to the value of variable B) || Assignment || All
|-
| A += B || Addition-assignment (A=A+B) || A is assigned the value of string-operation A+B || All
|-
| A -= B || Subtraction-assignment (A=A-B) || A is assigned the value of string-operation A-B || All
|-
| A *= B || Multiplication-assignment (A=A*B) || Runtime error. The rest of the line is skipped. || All
|-
| A /= B || Division-assignment (A=A/B) || Runtime error. The rest of the line is skipped. || All
|-
| A ^= B || Exponentiation-assignment (A=A^B) || Runtime error. The rest of the line is skipped. || Advanced, Professional
|-
| A %= B || Modulo-assignment (A=A%B) || Runtime error. The rest of the line is skipped. || Advanced, Professional
|-
| A ^ B || Exponentiation || Runtime error. The rest of the line is skipped. || Advanced, Professional
|-
| A % B || Modulo || Runtime error. The rest of the line is skipped. || Advanced, Professional
|-
| ABS A || Modulus (absol value) (A=A if A>=0, else A=-A) || Runtime error. The rest of the line is skipped. || Advanced, Professional
|-
| A! || Factorial || || Advanced, Professional
|-
| SQRT A || Square root of A || || Advanced, Professional
|-
| SIN A || Sine of A (degrees) || || Professional
|-
| COS A || Cosine of A (degrees) || || Professional
|-
| TAN A || Tangent of A (degrees) || || Professional
|-
| ASIN A || Inverse sine of A (degrees) || || Professional
|-
| ACOS A || Inverse cosine of A (degrees) || || Professional
|-
| ATAN A || Inverse tangent of A (degrees) || || Professional
|}

=== Logical operators ===

Logical operators are checks that identify if the statement is true or false. 
All logical operations return either '''"0 for False"''' or '''"1 for True"'''.
The '''NOT''', '''AND''', and '''OR''' keywords consider 0 to be falsy and anything not 0 to be truthy.

{| class="wikitable"
|-
! Operation || Numeric operation || String operation || Chip availability
|-
| A B || Greater than || returns 0 if String A is first in alphabetical order, returns 1 if not. || All
|-
| A <= B ||Less than or equal to || returns 1 if String A is first in alphabetical order or identical to String B, returns 0 if not. || All
|-
| A >= B || Greater than or equal to || returns 0 if String A is first in alphabetical order or identical to String B, returns 1 if not. || All
|-
| A != B || Not equal to || returns 1 if String A is not equal to String B, 0 if it is. || All
|-
| A == B || Equal to || returns 1 if String A is equal to String B, 0 if not. || All
|-
| NOT A || Not || Returns 1 if A is 0, otherwise returns 0. || All
|-
| A AND B || And || Returns 1 if neither A nor B are 0, otherwise returns 0. || All
|-
| A OR B || Or || Returns 1 if either A or B is not 0, otherwise returns 0. || All
|}

=== Mixing variable types in operations ===

Mixing variable types in an operation handles the operation using all parameters as ''strings''.

previouslyNumber= "10" + 15
* The above script results in '''previouslyNumber''' containing the string value "1015".
** Note that the involved parameters themselves don't change types, their values are just cast as strings for the purpose of the operation:

purelyNumber = 15
purelyString = "10" + purelyNumber
* When this script has executed, '''purelyString''' contains the string value of "1015", while '''purelyNumber''' still contains the numeric value of 15.

=== Goto ===

Goto syntax is used when the normal script reading order from 1->20 is not desired, or needs to be altered.

Goto is used with the following syntax:
*'''goto lineNumber'''
** lineNumber is the line which this command will take the script execution. 
** Any remaining script that is on the same line after the goto-command will not be executed.
*** using if statements before goto ignores goto syntax, assuming the if-statement is false
** Multiple goto commands can be added on the same line using conditionals, as '''False''' goto commands are skipped.
** Numeric values outside the [1,20] range are clamped to this range.
** Non-integer values are floored.
** String values will result in a Runtime Error.

if variable == 5 then '''goto 4''' end '''goto 6'''

The script above will go to line number 4, if '''variable''' has a value of 5. 
Otherwise it will go to line number 6. Numerical operations can also be done "inside" the goto, e.g.

goto 4+1

=== If-else conditional ===

If-else statements are used to branch out the script into different paths. 
They use the following syntax:
* '''if ''condition'' then ''statement'' else ''statement'' end'''
** Condition is a statement that results in a numeric value (where 0 is parsed as False, anything else as True), and statements are pieces of script that are run.
** All If-else conditional stations must have '''end''' syntax written after statement is complete.
** The statement has to be on one line. The if, then, else and end cannot be on different lines.

If can be used to branch script execution into two possible outcomes temporarily based on variable value(s). 
'''Example:''' 
'''if''' variable != 2 '''then''' endResult = 3 '''else''' endResult = 4 '''end'''

* This script sets the value of '''endResult''' to 3 if '''variable''' does not have the value of 2.
* If '''variable''''s value is 2, '''endResult''' is set to the value of 4.

Note that the else statement -part can be left out if not needed. 

'''Example:''' 
'''if''' variable != 2 '''then''' endResult = 3 '''end'''
*This script only sets the value of 3 to '''endResult''' if '''variable''' does not have a value of 2, and doesn't do anything else.

==== Nesting if statements ====

It is possible to place if-conditionals inside the true/false statement blocks to achieve further branching of execution. 
Example: 
'''if''' variable == 0 '''then''' endResult = 1 '''else''' '''if''' variable == 1 '''then''' endResult = 2 '''end''' '''end'''
* This script sets '''endResult''' to 1 if '''variable''' equals 0.
* If '''variable''' doesn't equal 0, but it equals 1, '''endResult''' is set to 2.

Example: 
'''if''' variable == 0 '''then''' '''if''' endResult == 1 '''then''' endResult = 2 '''end''' '''else''' endResult = 1 '''end'''
* This script sets '''endResult''' to 2 if '''variable''' has a value of 0, and '''endResult''' equals to 1.
* Otherwise it sets '''endResult''' to 1.

=== Comments ===

Comments are useful when writing code that is used by a lot of programmers. 
Note that comments also use up space from the pre-determined 70 character line limit and are not excluded from it. 

Commenting is used with the following syntax:
*// '''text'''
** Text can be any single-line set of characters.

'''//''' This is a comment. It will explain how other lines of script work.
* An example of a possible comment syntax

== Order of Operations ==

Operations are conducted in the following order, when operators have the same precedence, left to right. 
To change order of operations, use ( ): e.g. 3*2+1=6+1=7 is the same as (3*2)+1=6+1=7 but is different from 3*(2+1)=3*3=9.
Where a line has multiple statements, they are executed left to right.

{| class="wikitable"
|-
! Operators
! Comments
|-
| ++ --
|
|-
| <nowiki>!</nowiki>
|
|-
| operators
| sqrt, abs, sin etc.
|-
| <nowiki>-</nowiki>
| negate
|-
| ^
|
|-
| */%
|
|-
| <nowiki>< > == != <= >=</nowiki>
| Surprise!
|-
| <nowiki>+-</nowiki>
|
|-
| not (logical negation)
|
|-
| or
|
|-
| and
|
|-
|}

== Errors ==

There are two types of errors that can happen with the programming language.
# Syntax errors
# Runtime errors

* Syntax errors come from invalid and unparseable script and will result in the whole line not being executed.
* Runtime errors are only catchable while the script is being executed. They result in the execution of the line being interrupted, but any effects until the error will remain.

== Known Bugs/Unintended Behavior ==
This is a list of known problems regarding yolol: 

* variablenames including keywords like "if" in them will parse with the keyword in mind, resulting in a syntax error. Example: :life would be parsed as :l if e

==YOLOL Tips & Tricks==
* [[Common YOLOL|Common YOLOL scripts]]
* [[YOLOL Tricks]]

== Related Pages ==
* [[Data networks]]
* [[Devices and machines]]
* [[Device fields]]
* [[Universal tool|Universal tool]]
* [[YOLOL Chip]]
* [[Memory chip]]

[[Category:Networks|YOLOL]]

Towing beam

2022-08-06T06:34:03Z

Scrapper 101: Changed Energy input value to be what stated in Starbase Video Game.

{{Otherlang2
|ru=Буксировочный_луч
}}{{SB Infobox Begin
|{{SB Infobox Header
|image=[[Image:Towing beam.png]]
|factionLogo=
|caption=
|name=
|border=none
}}

|{{SB Infobox Device General Information
|type=Utility device
|function=Towing other ships

|size=204×72×72 cm
|mass=3,198.9
|volume=395.9
|corrosionResistance=400
|primaryMaterial=Bastium
|suppressUnitsKg
|suppressUnitsKv
|subComponents=
}}

|{{SB Infobox Device IO
|electricIn=5 e/s per ton towed
|electricOut=
|energyCapacity=
|coolantIn=
|coolantOut=
|coolantCapacity=
|coolantRefresh=
|heatGeneration=
|heatDissipation
|propellantIn=
|propellantOut=
|propellantCapacity
|fuelIn=
|fuelOut=
|fuelCapacity
|sockets=
|YOLOLchips=
|modInterfaces=
|deviceInterfaces=
|enhancement=
}}

|{{SB Infobox Device Construction
|headerOverride=
|aegisium=
|ajatite=
|arkanium=
|bastium=10%
|charodium=
|corazium=
|exorium=25%
|haderite=
|ice=
|ilmatrium=
|karnite=
|kutonium=35%
|lukium=
|merkerium=
|nhurgite=
|oninum=
|surtrite=
|tengium=
|ukonium=
|valkite=
|vokarium=30%
|xhalium=
}}
}}<section begin=summary/>The towing beam is a device that can be used to tow other ships.

The towing beam uses power relative to the mass of the ship being towed (5e/s per ton), this mass is also added to the ship's mass, slowing the towing ship, but not adding any stress.

Outside of a safezone any ship can be towed, inside a safezone only un-owned ships are able to be towed.<section end=summary/>

== Device fields ==
<section begin=deviceFields/>
{|class="wikitable"
! YOLOL field
! description
! range
|-
! '''TowBeamOnState'''
| The towing beam turns off when this is set to 0 and on when set to anything else
| 0 - 1
|-
! '''TowBeamSearchLength'''
| The distance the beam will try extend to, and try to grab ships from.
| 200
|-
! '''TowBeamStatus'''
| 0 if off, 1 if on, 2 if a ship is being towed.
| 0 - 2
|-
! '''LockedMass'''
| The mass of the towed ship, in kg.
| 0 -
|-
|}
<section end=deviceFields/>
To learn more about how to use fields, consult these wiki pages:
* [[Universal tool|Universal Tool]]
* [[Data networks|Data networks]]
* [[YOLOL|YOLOL]]

== Related Pages ==

[[Towing beam (Assembly)]]

[[Category:Devices and machines]]