Starbase wiki - User contributions [en]

Common YOLOL

2021-08-30T16:57:35Z

Vox Serico: /* Fuel chamber */ Cleaned up the duplicated standard generator scripts with renamed fields

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

''This page is a WIP. Please contribute to it! (Avoid complex scripts and the renaming of fields.)''

==[[Fuel chamber]]==
Ships will require enough batteries to act as a buffer for the generator spool up time.

==="Standard" Generator Script===
:FuelChamberUnitRateLimit=100-:StoredBatteryPower/100 goto 1

Makes the fuel chambers' rate limit follow the battery charge inversely.
''<br/>Note: The [[Laborer Module]] ship rewarded during the tutorial has these fields renamed by default to: <code>Generator</code> and <code>Battery_1</code>''

===Settable on/off Generator flag===
c=(c<1)*(:Battery_1<5000)+c*(:Battery_1<9999) :Gen=c*22+0.001 goto 1
Fitting this code on the Laborer Module requires renaming at least one device. (here the Generator was renamed Gen)

5000 and 9999 are the start-charging and stop-charging levels. 22 is just enough charge to run the stock two box thrusters.

===Generator Script (Basic YOLOL Chip)===

This YOLOL script is inspired by the standard generator script and is further optimized.
You can set from which amount of stored battery power the generator should generate less compared to the stored battery power.

It is assumed that specific YOLOL fields are renamed:
{| class="wikitable"
|-
! Ship Part !! Old YOLOL field name !! New YOLOL field name
|-
| Every Fuel Chamber || FuelChamberUnitRateLimit || Gen
|-
| One Rechargeable Battery || StoredBatteryPower || Bat
|}

Depending on the amount of batteries and the amount of generators, a higher or lower value can be used for the variable "a" in the script. A too high value leads to the fact that the algorithm cannot find an optimal balance for the FuelChamberUnitRateLimit/Gen.

====Generator Script====

// Variables for Tweaking
a = 9500 // If Battery Amount is lower than this, Gen is 100%
// Static variables and precalculation
c = 10000 // Max Stored Battery Power
d = 100 // 100%
e = (c-a)/d
// Final Generator Scriptline
:Gen=((:Bat<a)*d)+((:Bat>a)*((:Bat-c)*-1)/e) goto 8

====Generator Script with On/Off Button and Minimum Power Production====

If the battery consumption is very high and the amount of rechargeable batteries is not enough until the generator produces enough power, you should consider using the following version of the script.

Use a Hybrid-Button with the following field names and values configured:
{| class="wikitable"
|-
! Name !! Value
|-
| On || 0
|-
| ButtonOnStateValue || 1
|-
| ButtonOffStateValue || 0
|-
| ButtonStyle || 1
|}

The variable b can be used to set the minimum amount of power that the generators should generate. A too low value, can lead to the fact that the generators do not provide enough power yet and the batteries are already discharged. A too high value leads to the fuel rod consumption during standstill being too high.

// Variables for Tweaking
a = 9500 // If Battery Amount is lower than this, Gen is 100%
b = 10 // If Button is On, Gen will be at least this much
// Static variables and precalculation
c = 10000 // Max Stored Battery Power
d = 100 // 100%
e=(c-a)/d f=(d/b)
// Final Generator Scriptline
:Gen=:On*(((:Bat<a)*d)+((:Bat>a)*(((:Bat-c)*-1)+(:Bat-a)/f)/e)) goto 9

==[[Flight control unit]]==
===Single lever forward/backward script (Basic YOLOL Chip)===

''Note: This script assumes you have a center lever bound to FcuForward''

====Default device fields====

:FcuBackward=-:FcuForward goto 1

==[[Material point scanner]]==
===Material Point Scanner Script===
''Note: Additionally to two output panels for '''"Material"''' and '''"Volume"''' and two buttons to toggle '''"Active"''' and '''"Scan"''' install a third button and rename '''"ButtonState"''' to '''"Next"''' and set its '''"ButtonStyle"''' to '''1'''.''
:Material=:Material :Volume=:Volume
:Index=(:Index+:Next)*(:Index<:ScanResults) :Next=0 goto 1

===Continuous Material Point Scanner Script===
''Note: This is a modified version of the above script''
:Material=:Material :Volume=:Volume
:Index=(:Index+:Next)*(:Index<:ScanResults) :Next=1
//pause
:Scan=1
goto 1

==[[Mining laser]]==
===Pulsed Mining Lasers===
Reduces power consumption by pulsing mining lasers on and off while a button is pressed. The duration of the on and off state are each configurable in number of ticks. (One tick is about 0.2 seconds)
on=1 off=2 :MiningLaserOn=:ButtonState*(t<on) t++ t*=t<(on+off) goto1

==[[Navigation receivers]]==
===Receiver Signal Display===
Using a display named '''Nav'''
if :SignalStrength>0 then goto2 else :Nav="No Signal" goto1 end
:Nav=:Message+"\n"+(1000000-:SignalStrength)/1000+" km" goto1

Common YOLOL

2021-08-30T16:04:26Z

Vox Serico: Short page description. Moved WIP notice to the top.

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

''This page is a WIP. Please contribute to it! (Avoid complex scripts and the renaming of fields.)''

==[[Fuel chamber]]==
===Standard Generator Script (Basic YOLOL Chip)===

''Note: This script will require enough batteries on the ship to act as a buffer for the generator spool up time.''

====Default Fields====

:FuelChamberUnitRateLimit=100-:StoredBatteryPower/100 goto 1

====Non Default Fields====

''Note: This version of the script assumes either "'''GeneratorUnitRateLimit'''" or "'''FuelChamberRateLimit'''" (preferably the latter) are renamed to "'''limit'''", and at least one battery exists on the network with it's "'''StoredBatteryPower'''" field renamed to "'''bat'''".''

:limit=100-:bat/100 goto 1

====Tutorial Laborer====

''Note: The Laborer has renamed field names by default so this version will work for the tutorial ship.''

:Generator=100-:Battery_1/100 goto 1

===Settable on/off Generator flag===
c=(c<1)*(:Battery_1<5000)+c*(:Battery_1<9999) :Gen=c*22+0.001 goto 1
Fitting this code on the Laborer Module requires renaming at least one device. (here the Generator was renamed Gen)

5000 and 9999 are the start-charging and stop-charging levels. 22 is just enough charge to run the stock two box thrusters.

===Generator Script (Basic YOLOL Chip)===

This YOLOL script is inspired by the standard generator script and is further optimized.
You can set from which amount of stored battery power the generator should generate less compared to the stored battery power.

It is assumed that specific YOLOL fields are renamed:
{| class="wikitable"
|-
! Ship Part !! Old YOLOL field name !! New YOLOL field name
|-
| Every Fuel Chamber || FuelChamberUnitRateLimit || Gen
|-
| One Rechargeable Battery || StoredBatteryPower || Bat
|}

Depending on the amount of batteries and the amount of generators, a higher or lower value can be used for the variable "a" in the script. A too high value leads to the fact that the algorithm cannot find an optimal balance for the FuelChamberUnitRateLimit/Gen.

====Generator Script====

// Variables for Tweaking
a = 9500 // If Battery Amount is lower than this, Gen is 100%
// Static variables and precalculation
c = 10000 // Max Stored Battery Power
d = 100 // 100%
e = (c-a)/d
// Final Generator Scriptline
:Gen=((:Bat<a)*d)+((:Bat>a)*((:Bat-c)*-1)/e) goto 8

====Generator Script with On/Off Button and Minimum Power Production====

If the battery consumption is very high and the amount of rechargeable batteries is not enough until the generator produces enough power, you should consider using the following version of the script.

Use a Hybrid-Button with the following field names and values configured:
{| class="wikitable"
|-
! Name !! Value
|-
| On || 0
|-
| ButtonOnStateValue || 1
|-
| ButtonOffStateValue || 0
|-
| ButtonStyle || 1
|}

The variable b can be used to set the minimum amount of power that the generators should generate. A too low value, can lead to the fact that the generators do not provide enough power yet and the batteries are already discharged. A too high value leads to the fuel rod consumption during standstill being too high.

// Variables for Tweaking
a = 9500 // If Battery Amount is lower than this, Gen is 100%
b = 10 // If Button is On, Gen will be at least this much
// Static variables and precalculation
c = 10000 // Max Stored Battery Power
d = 100 // 100%
e=(c-a)/d f=(d/b)
// Final Generator Scriptline
:Gen=:On*(((:Bat<a)*d)+((:Bat>a)*(((:Bat-c)*-1)+(:Bat-a)/f)/e)) goto 9

==[[Flight control unit]]==
===Single lever forward/backward script (Basic YOLOL Chip)===

''Note: This script assumes you have a center lever bound to FcuForward''

====Default device fields====

:FcuBackward=-:FcuForward goto 1

==[[Material point scanner]]==
===Material Point Scanner Script===
''Note: Additionally to two output panels for '''"Material"''' and '''"Volume"''' and two buttons to toggle '''"Active"''' and '''"Scan"''' install a third button and rename '''"ButtonState"''' to '''"Next"''' and set its '''"ButtonStyle"''' to '''1'''.''
:Material=:Material :Volume=:Volume
:Index=(:Index+:Next)*(:Index<:ScanResults) :Next=0 goto 1

===Continuous Material Point Scanner Script===
''Note: This is a modified version of the above script''
:Material=:Material :Volume=:Volume
:Index=(:Index+:Next)*(:Index<:ScanResults) :Next=1
//pause
:Scan=1
goto 1

==[[Mining laser]]==
===Pulsed Mining Lasers===
Reduces power consumption by pulsing mining lasers on and off while a button is pressed. The duration of the on and off state are each configurable in number of ticks. (One tick is about 0.2 seconds)
on=1 off=2 :MiningLaserOn=:ButtonState*(t<on) t++ t*=t<(on+off) goto1

==[[Navigation receivers]]==
===Receiver Signal Display===
Using a display named '''Nav'''
if :SignalStrength>0 then goto2 else :Nav="No Signal" goto1 end
:Nav=:Message+"\n"+(1000000-:SignalStrength)/1000+" km" goto1

''This page is a WIP. Please contribute to it!''

Common YOLOL

2021-08-30T11:32:29Z

Vox Serico: Reorganized scripts into sections of their main device/machine.

==[[Fuel chamber]]==
===Standard Generator Script (Basic YOLOL Chip)===

''Note: This script will require enough batteries on the ship to act as a buffer for the generator spool up time.''

====Default Fields====

:FuelChamberUnitRateLimit=100-:StoredBatteryPower/100 goto 1

====Non Default Fields====

''Note: This version of the script assumes either "'''GeneratorUnitRateLimit'''" or "'''FuelChamberRateLimit'''" (preferably the latter) are renamed to "'''limit'''", and at least one battery exists on the network with it's "'''StoredBatteryPower'''" field renamed to "'''bat'''".''

:limit=100-:bat/100 goto 1

====Tutorial Laborer====

''Note: The Laborer has renamed field names by default so this version will work for the tutorial ship.''

:Generator=100-:Battery_1/100 goto 1

===Settable on/off Generator flag===
c=(c<1)*(:Battery_1<5000)+c*(:Battery_1<9999) :Gen=c*22+0.001 goto 1
Fitting this code on the Laborer Module requires renaming at least one device. (here the Generator was renamed Gen)

5000 and 9999 are the start-charging and stop-charging levels. 22 is just enough charge to run the stock two box thrusters.

===Awesome Generator Script (Basic YOLOL Chip)===

This YOLOL script is inspired by the standard generator script and is further optimized.
You can set from which amount of stored battery power the generator should generate less compared to the stored battery power.

It is assumed that specific YOLOL fields are renamed:
{| class="wikitable"
|-
! Ship Part !! Old YOLOL field name !! New YOLOL field name
|-
| Every Fuel Chamber || FuelChamberUnitRateLimit || Gen
|-
| One Rechargeable Battery || StoredBatteryPower || Bat
|}

Depending on the amount of batteries and the amount of generators, a higher or lower value can be used for the variable "a" in the script. A too high value leads to the fact that the algorithm cannot find an optimal balance for the FuelChamberUnitRateLimit/Gen.

====Awesome Generator Script====

// Variables for Tweaking
a = 9500 // If Battery Amount is lower than this, Gen is 100%
// Static variables and precalculation
c = 10000 // Max Stored Battery Power
d = 100 // 100%
e = (c-a)/d
// Final Generator Scriptline
:Gen=((:Bat<a)*d)+((:Bat>a)*((:Bat-c)*-1)/e) goto 8

====Awesome Generator Script with On/Off Button and Minimum Power Production====

If the battery consumption is very high and the amount of rechargeable batteries is not enough until the generator produces enough power, you should consider using the following version of the script.

Use a Hybrid-Button with the following field names and values configured:
{| class="wikitable"
|-
! Name !! Value
|-
| On || 0
|-
| ButtonOnStateValue || 1
|-
| ButtonOffStateValue || 0
|-
| ButtonStyle || 1
|}

The variable b can be used to set the minimum amount of power that the generators should generate. A too low value, can lead to the fact that the generators do not provide enough power yet and the batteries are already discharged. A too high value leads to the fuel rod consumption during standstill being too high.

// Variables for Tweaking
a = 9500 // If Battery Amount is lower than this, Gen is 100%
b = 10 // If Button is On, Gen will be at least this much
// Static variables and precalculation
c = 10000 // Max Stored Battery Power
d = 100 // 100%
e=(c-a)/d f=(d/b)
// Final Generator Scriptline
:Gen=:On*(((:Bat<a)*d)+((:Bat>a)*(((:Bat-c)*-1)+(:Bat-a)/f)/e)) goto 9

==[[Flight control unit]]==
===Single lever forward/backward script (Basic YOLOL Chip)===

''Note: This script assumes you have a center lever bound to FcuForward''

====Default device fields====

:FcuBackward=-:FcuForward goto 1

==[[Material point scanner]]==
===Material Point Scanner Script===
''Note: Additionally to two output panels for '''"Material"''' and '''"Volume"''' and two buttons to toggle '''"Active"''' and '''"Scan"''' install a third button and rename '''"ButtonState"''' to '''"Next"''' and set its '''"ButtonStyle"''' to '''1'''.''
:Material=:Material :Volume=:Volume
:Index=(:Index+:Next)*(:Index<:ScanResults) :Next=0 goto 1

===Continuous Material Point Scanner Script===
''Note: This is a modified version of the above script''
:Material=:Material :Volume=:Volume
:Index=(:Index+:Next)*(:Index<:ScanResults) :Next=1
//pause
:Scan=1
goto 1

==[[Mining laser]]==
===Pulsed Mining Lasers===
Reduces power consumption by pulsing mining lasers on and off while a button is pressed. The duration of the on and off state are each configurable in number of ticks. (One tick is about 0.2 seconds)
on=1 off=2 :MiningLaserOn=:ButtonState*(t<on) t++ t*=t<(on+off) goto1

==[[Navigation receivers]]==
===Receiver Signal Display===
Using a display named '''Nav'''
if :SignalStrength>0 then goto2 else :Nav="No Signal" goto1 end
:Nav=:Message+"\n"+(1000000-:SignalStrength)/1000+" km" goto1

''This page is a WIP. Please contribute to it!''

Common YOLOL

2021-08-30T11:14:09Z

Vox Serico: /* Pulsed Signal Script */ Reduced script complexity. Reworded the description.

==Standard Generator Script (Basic YOLOL Chip)==

''Note: This script will require enough batteries on the ship to act as a buffer for the generator spool up time.''

===Default Fields===

:FuelChamberUnitRateLimit=100-:StoredBatteryPower/100 goto 1

===Non Default Fields===

''Note: This version of the script assumes either "'''GeneratorUnitRateLimit'''" or "'''FuelChamberRateLimit'''" (preferably the latter) are renamed to "'''limit'''", and at least one battery exists on the network with it's "'''StoredBatteryPower'''" field renamed to "'''bat'''".''

:limit=100-:bat/100 goto 1

===Tutorial Laborer===

''Note: The Laborer has renamed field names by default so this version will work for the tutorial ship.''

:Generator=100-:Battery_1/100 goto 1

==Settable on/off Generator flag==
c=(c<1)*(:Battery_1<5000)+c*(:Battery_1<9999) :Gen=c*22+0.001 goto 1
Fitting this code on the Laborer Module requires renaming at least one device. (here the Generator was renamed Gen)

5000 and 9999 are the start-charging and stop-charging levels. 22 is just enough charge to run the stock two box thrusters.

==Awesome Generator Script (Basic YOLOL Chip)==

This YOLOL script is inspired by the standard generator script and is further optimized.
You can set from which amount of stored battery power the generator should generate less compared to the stored battery power.

It is assumed that specific YOLOL fields are renamed:
{| class="wikitable"
|-
! Ship Part !! Old YOLOL field name !! New YOLOL field name
|-
| Every Fuel Chamber || FuelChamberUnitRateLimit || Gen
|-
| One Rechargeable Battery || StoredBatteryPower || Bat
|}

Depending on the amount of batteries and the amount of generators, a higher or lower value can be used for the variable "a" in the script. A too high value leads to the fact that the algorithm cannot find an optimal balance for the FuelChamberUnitRateLimit/Gen.

===Awesome Generator Script===

// Variables for Tweaking
a = 9500 // If Battery Amount is lower than this, Gen is 100%
// Static variables and precalculation
c = 10000 // Max Stored Battery Power
d = 100 // 100%
e = (c-a)/d
// Final Generator Scriptline
:Gen=((:Bat<a)*d)+((:Bat>a)*((:Bat-c)*-1)/e) goto 8

===Awesome Generator Script with On/Off Button and Minimum Power Production===

If the battery consumption is very high and the amount of rechargeable batteries is not enough until the generator produces enough power, you should consider using the following version of the script.

Use a Hybrid-Button with the following field names and values configured:
{| class="wikitable"
|-
! Name !! Value
|-
| On || 0
|-
| ButtonOnStateValue || 1
|-
| ButtonOffStateValue || 0
|-
| ButtonStyle || 1
|}

The variable b can be used to set the minimum amount of power that the generators should generate. A too low value, can lead to the fact that the generators do not provide enough power yet and the batteries are already discharged. A too high value leads to the fuel rod consumption during standstill being too high.

// Variables for Tweaking
a = 9500 // If Battery Amount is lower than this, Gen is 100%
b = 10 // If Button is On, Gen will be at least this much
// Static variables and precalculation
c = 10000 // Max Stored Battery Power
d = 100 // 100%
e=(c-a)/d f=(d/b)
// Final Generator Scriptline
:Gen=:On*(((:Bat<a)*d)+((:Bat>a)*(((:Bat-c)*-1)+(:Bat-a)/f)/e)) goto 9

==Receiver Signal Display==
Using a display named '''Nav'''
if :SignalStrength>0 then goto2 else :Nav="No Signal" goto1 end
:Nav=:Message+"\n"+(1000000-:SignalStrength)/1000+" km" goto1

==Single lever forward/backward script (Basic YOLOL Chip)==

''Note: This script assumes you have a center lever bound to FcuForward''

===Default device fields===

:FcuBackward=-:FcuForward goto 1

==Material Point Scanner Script==
''Note: Additionally to two output panels for '''"Material"''' and '''"Volume"''' and two buttons to toggle '''"Active"''' and '''"Scan"''' install a third button and rename '''"ButtonState"''' to '''"Next"''' and set its '''"ButtonStyle"''' to '''1'''.''
:Material=:Material :Volume=:Volume
:Index=(:Index+:Next)*(:Index<:ScanResults) :Next=0 goto 1

==Continuous Material Point Scanner Script==
''Note: This is a modified version of the above script''
:Material=:Material :Volume=:Volume
:Index=(:Index+:Next)*(:Index<:ScanResults) :Next=1
//pause
:Scan=1
goto 1

==Pulsed Mining Lasers==
Reduces power consumption by pulsing mining lasers on and off while a button is pressed. The duration of the on and off state are each configurable in number of ticks. (One tick is about 0.2 seconds)
on=1 off=2 :MiningLaserOn=:ButtonState*(t<on) t++ t*=t<(on+off) goto1

''This page is a WIP. Please contribute to it!''

YOLOL

2021-08-30T10:05:04Z

Vox Serico: Merged the content in the Related Pages subsection to the bottom header, matching the style of other pages.

{{Otherlang2
|de=YOLOL:de
|zh-cn=YOLOL语言
|ru=YOLOL:ru
|ua=YOLOL:ua
|jp=YOLOL:jp
}}
== Summary ==
YOLOL is a programming language used to control and manage electrical [[Devices and machines|devices]].<br>
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.<br>
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]].<br>
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.

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

== Command references ==

=== Case insensitive ===

The programming language is fully case '''insensitive'''.<br>
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.<br>
The variables hold decimal numbers up to three decimal accuracy.<br>
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.

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:<br>
* ''':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.<br>
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]].<br>
It can then modify and listen to any device fields it has access to.<br>

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.

== Operators and commands ==

Note that the available operators may be limited by the type of the programmable [[YOLOL Chip|chip]].<br>
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 || Runtime error. The rest of the line is skipped. || All
|-
| A / B || Division || Runtime error. The rest of the line is skipped. || 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 || Runtime error. The rest of the line is skipped. || Advanced, Professional
|-
| SQRT A || Square root of A || Runtime error. The rest of the line is skipped. || Advanced, Professional
|-
| SIN A || Sine of A (degrees) || Runtime error. The rest of the line is skipped. || Professional
|-
| COS A || Cosine of A (degrees) || Runtime error. The rest of the line is skipped. || Professional
|-
| TAN A || Tangent of A (degrees) || Runtime error. The rest of the line is skipped. || Professional
|-
| ASIN A || Inverse sine of A (degrees) || Runtime error. The rest of the line is skipped. || Professional
|-
| ACOS A || Inverse cosine of A (degrees) || Runtime error. The rest of the line is skipped. || Professional
|-
| ATAN A || Inverse tangent of A (degrees) || Runtime error. The rest of the line is skipped. || Professional
|}

=== Logical operators ===

Logical operators are checks that identify if the statement is true or false.<br>
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 || Less than || returns 1 if String A is first in alphabetical order, returns 0 if not. || All
|-
| 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.<br>
** 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.<br>
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.<br>
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.

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

* 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.<br>
'''Example:'''<br>
<font color="orangered">'''if'''</font> variable != 2 <font color="orangered">'''then'''</font> endResult = 3 <font color="orangered">'''end'''</font>
*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.<br>
Example:<br>
<font color="orangered">'''if'''</font> variable == 0 <font color="orangered">'''then'''</font> endResult = 1 <font color="orangered">'''else'''</font> <font color="cyan">'''if'''</font> variable == 1 <font color="cyan">'''then'''</font> endResult = 2 <font color="cyan">'''end'''</font> <font color="orangered">'''end'''</font>
* 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:<br>
<font color="orangered">'''if'''</font> variable == 0 <font color="orangered">'''then'''</font> <font color="cyan">'''if'''</font> endResult == 1 <font color="cyan">'''then'''</font> endResult = 2 <font color="cyan">'''end'''</font> <font color="orangered">'''else'''</font> endResult = 1 <font color="orangered">'''end'''</font>
* 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.<br>
Note that comments also use up space from the pre-determined 70 character line limit and are not excluded from it.<br>

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 precidence, left to right.<br>
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:<br>

* 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

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

[[Category:Networks|YOLOL]]

Ymrium

2021-08-23T06:23:18Z