Starbase wiki - User contributions [en]

Common YOLOL

2021-08-18T16:18:41Z

Kabeck515: added to Networks category

==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

===Namrog84's Alternative===

The above scripts suffer a weakness that some might have noticed, they attempt to scale the generator linearly between 0 and 10,000 battery to have generator match them from 0% to 100%. E.g. at 50%(5000) battery the generators go to 50% only to KEEP UP with the drain. But won't actually recharge them to max.
The below math might look at first glance to be the same. However, it is subtly different. If battery is at 9000, then generators will go to 100% (and will be at 100% for anything below 9000). However when batteries are at 9500 the generators will be at 50%. But then by 9950 batteries, generator will be 5% and will eventually hit 0 or near 0 when at full charge.

:FuelChamberUnitRateLimit=1000-:StoredBatteryPower/10 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 9

===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

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

[[Category:Networks|YOLOL]]

Data networks

2021-08-18T16:09:38Z

Kabeck515: minor typos

{{Otherlang2
|de=Data_networks:de
|fr=Data_networks/fr
|ru=Информационная_сеть
|zh-cn=数据网络
|ua=Інформаційна мережа
|jp=データネットワーク
}}

== Summary ==
Data networks enable the creation, maintenance and control of large number of [[Devices and machines|devices]]. [[Universal tool|Universal tool]] and [[Cable tool|cable tool]] are the tools generally used for managing data networks. 
Data networks enable designers and pioneers to create, modify and maintain devices, such as [[Generator (Assembly)|power generators]], programmable logic [[YOLOL Chip|chips]] and more mundane devices such as [[Hinges|doors]] and elevators. 
The signals are controlled with [[YOLOL|programming language YOLOL]] that is accessible to everyone.

== Terminology ==

Objects have physical '''sockets''' and virtual '''device fields''' inside them.
* '''Sockets''' are used to connect objects to data networks with cables or directly through other devices.
* '''[[Device fields]]''' are configured and accessed when objects share the same data network.
** A device field controls one specific attribute or feature within a [[Devices and machines|device]].
*** The device field can for example be the amount of generated heat within a [[Thrusters|thruster]], or a value that can be manually changed such as button states in [[Buttons|buttons]].
** These device field names can generally be configured by using the appropriate [[Universal tool|tool]].



== Data network resources ==

Data networks are connected together with cables. 
When devices are connected together, the data network can transfer two different resources. 
# '''Electricity'''
# '''Signals'''

'''Electricity: all objects within the data network share power'''
* A [[Generator (Assembly)|generator]] attached to a data network tries to supply power to multiple [[Devices and machines|devices or machines]].
** This is why it is important to have multiple generators if there are many devices connected to the data network that need power.

'''Signals: all objects within the data network are able to communicate with each other'''
* Cables can connect to each other directly.
* Sockets may have multiple connections and cables may branch.
* There are no limits to how many data networks can exist e.g. on one spaceship.
** A branched data network doesn't break as easily during combat.

=== Device fields ===

Each device can have a set of device fields. This fields constist of a name and a value and both is customizable. Any field on the network can have any name you wish, "conflicting" names are allowed too, in fact sometimes they are used to build a network. Renaming a device field does not changes how the device manages it, swapping the name of two device fields' name within the same device does '''not''' actually swaps the two field. The devices' manages their field by their '''position''', not by their name, e.g.: A box thruster's first field will be always the control field regardless of it's name, while the second field will always be the feedback.

=== Field type ===

These fields can be of 3 type: input, output or IO (input + output).

* '''Input''' fields are purely for controlling the device. The device itself does not changes the value of an input field but changes it's way of operation e.g.: ThrusterPowerLevel. The thruster increases or decreases it's current thrust based on what you set the ThrusterPowerLevel field to, but on it's own it will never change the value of the field.

* '''Output''' fields are the exact opposite. No matter what you write into these fields it will never affect how the device operates. Output fields are only for monitoring the devices' states. The devices periodically writes values into their output fields overwriting whatever was in there previously. An example is the "CurrentThrust" field of the thruster, you can not modify the thruster with that field, and whenever the thruster changes it's thrust level, it overwrites this field with the new value,.

* IO fields are the combination of both input and output. You can manually write a value in them and that will change the operation of the device but on the other hand some events within the device (e.g.: pulling a lever) will cause the device to also write a new value into the field.

=== Value propagation ===
Whenever a device changes its own fields' values, the change is propagated through the network. Every other device will update their fields of the same name to the new value. Updating the field through the Universal tool does not cause a change propagation but manual events (e.g.: pulling a lever) do. The propagation affects both the input and output fields of every device on the same network. Thus you don't need Yolol to connect 2 devices, just name one device's input or IO field to the same name as another device's output or IO field. Yolol chips cause value propagation when you set a global name (e.g.: '':GlobalName = value''), but keep in mind that if the name does not exist on the network then the yolol line will fail. The previous yolol code is valid if there is at least one device that has a field with the given name (without the ':' prefix) or if there is a yolol memory chip with an entry with the given name.




[[Category:Networks|Data network]]

Data networks

2021-08-18T16:05:27Z

Kabeck515: minor syntax improvements

{{Otherlang2
|de=Data_networks:de
|fr=Data_networks/fr
|ru=Информационная_сеть
|zh-cn=数据网络
|ua=Інформаційна мережа
|jp=データネットワーク
}}

== Summary ==
Data networks enable the creation, maintenance and control of large number of [[Devices and machines|devices]]. [[Universal tool|Universal tool]] and [[Cable tool|cable tool]] are the tools generally used for managing data networks. 
Data networks enable designers and pioneers to create, modify and maintain devices, such as [[Generator (Assembly)|power generators]], programmable logic [[YOLOL Chip|chips]] and more mundane devices such as [[Hinges|doors]] and elevators. 
The signals are controlled with [[YOLOL|programming language YOLOL]] that is accessible to everyone.

== Terminology ==

Objects have physical '''sockets''' and virtual '''device fields''' inside them.
* '''Sockets''' are used to connect objects to data networks with cables or directly through other devices.
* '''[[Device fields]]''' are configured and accessed when objects share the same data network.
** A device field controls one specific attribute or feature within a [[Devices and machines|device]].
*** The device field can for example be the amount of generated heat within a [[Thrusters|thruster]], or a value that can be manually changed such as button states in [[Buttons|buttons]].
** These device field names can generally be configured by using the appropriate [[Universal tool|tool]].



== Data network resources ==

Data networks are connected together with cables. 
When devices are connected together, the data network can transfer two different resources. 
# '''Electricity'''
# '''Signals'''

'''Electricity: all objects within the data network share power'''
* A [[Generator (Assembly)|generator]] attached to a data network tries to supply power to multiple [[Devices and machines|devices or machines]].
** This is why it is important to have multiple generators if there are many devices connected to the data network that need power.

'''Signals: all objects within the data network are able to communicate with each other'''
* Cables can connect to each other directly.
* Sockets may have multiple connections and cables may branch.
* There are no limits to how many data networks can exist e.g. on one spaceship.
** A branched data network doesn't break as easily during combat.

=== Device fields ===

Each device can have a set of device fields. This fields constist of a name and a value and both is customizable. Any field on the network can have any name you wish, "conflicting" names are allowed too, in fact sometimes they are used to build a network. Renaming a device field does not changes how the device manages it, swapping the name of two device fields' name within the same device does '''not''' actually swaps the two field. The devices' manages their field by their '''position''', not by their name, e.g.: A box thruster's first field will be always the control field regardless of it's name, while the second field will always be the feedback.

=== Field type ===

These fields can be of 3 type: input, output or IO (input + output).

* '''Input''' fields are purely for controlling the device. The device itself does not changes the value of an input field but changes it's way of operation e.g.: ThrusterPowerLevel. The thruster increases or decreases it's current thrust based on what you set the ThrusterPowerLevel field to, but on it's own it will never change the value of the field.

* '''Output''' fields are the exact opposite. No matter what you write into these fields it will never affect how the device operates. Output fields are only for monitoring the devices' states. The devices periodically writes values into their output fields overwriting whatever was in there previously. An example is the "CurrentThrust" field of the thruster, you can not modify the thruster with that field, and whenever the thruster changes it's thrust level, it overwrites this field with the new value,.

* IO fields are the combination of both input and output. You can manually write a value in them and that will change the operation of the device but on the other hand some events within the device (e.g.: pulling a lever) will cause the device to also write a new value into the field.

=== Value propagation ===
Whenever a device changes it's own field's value, the change is propagated through the network. Every other device will update their fields of the same name to the new value. Updating the field through the Universal tool does not cause a change propagation but manual events (e.g.: pulling a lever) does. The propagation affects both input and output fields of every device on the same network. Thus you don't need Yolol to connect 2 devices, just name one device's input or IO field to the same name as another device's output or IO field. Yolol chips cause value propagation when you set a global name (e.g.: '':GlobalName = value''), but keep in mind that if the name does not exist on the network then the yolol line will fail. The previous yolol code is valid if there is at least one device that has a field with the given name (without the ':' prefix) or if there is a yolol memory chip with an entry with the given name.




[[Category:Networks|Data network]]

Cutting tool

2021-08-14T14:41:42Z

Kabeck515:

{{SB Infobox Begin
|{{SB Infobox Header
|image=[[Image:Cutting tool.png]]
|previewImage=[[Image:Cutting tool preview.png]]
|name=
|border=none
}}
|{{SB Infobox Equipment General Information
|equipmentFunction=Deconstruction and salvaging
|availability=[[Bolt]]
|marketPrice=15,727
}}
|{{SB Infobox Equipment Specifications
|damage=
|projectile=Laser
|projectileMass=
|suppressUnitsPM=
|velocity=
|rateOfFire=
|bulletSpread=
|magazineCapacity=1,000
|reloadTime=3.2
}}
}}<section begin=summary/>The cutting tool is a projected energy tool that can cut an object by causing pin-point voxel damage, as opposed to the more brutish fracture damage that the [[Buzzsaw|buzz-saw]] causes. Like the buzz-saw, the cutting tool requires electricity to function and sources its power from power packs.<section end=summary/>

[[Category:Hand tools]]

Station Building Guide

2021-08-11T14:37:16Z

Kabeck515: Kabeck515 moved page Station Building Guide to Station Building Guide (Obsolete)

#REDIRECT [[Station Building Guide (Obsolete)]]

Station Building Guide (Obsolete)

2021-08-11T14:37:16Z

Kabeck515: Kabeck515 moved page Station Building Guide to Station Building Guide (Obsolete)

= Summary =
Guide for Starbase Station building.

== Access ==

=== Enter the game ===

'''Step I'''

Start the game and choose "ENTER UNIVERSE" from the Main Menu.

[[File:2020-12-07_15_30_43-Starbase.png|600px]]

'''Step II'''

This takes you to the character selection menu. Create a character if you don't have one. If you do, just select Enter Universe.

[[File:2020-12-07_15_30_58-Starbase.png|600px]]

=== Buy Station Foundation Blueprint Projector ===
When you have entered the game look for the Marketplace.

[[File:2020-12-04_15_51_55-Starbase.png|600px]]

'''Step I'''

Find the shop called "Constructs".

[[File:2020-12-07_15_32_22-Starbase.png|600px]]

'''Step II'''

Buy the Station Foundation Blueprint Projector and make sure it is in your inventory when leaving the station.

[[File:2020-12-04_16_02_20-Starbase.png|600px]]

[[File:2020-12-07_15_44_00-Starbase.png|600px]]

=== Create your station ===

Find an empty spot in the universe and press the button on the Station Foundation Blueprint Projector.
* You cannot create your station too close to other stations
* You cannot create your station in restricted areas
* If you try to create your station but the area is restricted, pick up the projector and find a more suitable place

[[File:2020-12-07_15_56_23-Starbase.png|600px]]

[[File:2020-12-07_15_56_45-Starbase.png|600px]]

=== Build station foundation ===

Build the Station Foundation Blueprint. You can build it in three different ways:

1. By using a building tool and having the correct materials in your inventory or station storage.
* You can see which materials are required for each part by accessing the Universal Tool and choosing the Materials tab

[[File:2020-12-07_16_34_32-Starbase.png|600px]]

2. Automated building; you have correct pieces in your inventory or station storage and they automatically go to the blueprint at the rate of one piece in one second.
* You can change the automated building settings by pressing I and navigating to Stations tab, and choosing Building page

3. Manually snapping the correct piece into place (press C to toggle snapping on/off) and weld with M1 (and unweld with M2 if needed) using the welding tool.

[[File:2020-12-07_16_50_48-Starbase.png|600px]]

[[File:2020-12-07_16_51_02-Starbase.png|600px]]

=== Add modules to your station ===

Once the station foundation is finished, the Station Designer can be accessed from the terminal inside it!

[[File:2020-12-08_13_08_34-Starbase.png|600px]]

==== Warning! ====
Your Station will not work properly if the modules are not fully attached to the Foundation. The Landing Pad does not snap to it, only lot modules. Use the '''"Show detached Station parts"''' button in the station desinger to highlight faulty modules before saving.

=== Resigning and claiming a station ===

* You can resign a station from the terminal inside the station foundation at any time
* You can also resign the station by pressing the button on Station Foundation Blueprint Projector, if nothing has been built yet
* Once you resign your station, anyone can claim it, becoming the new owner

== Videos ==
=== Placing 45 degree corners ===
<youtube width="200" height="120">53QrbA0LWGg</youtube>

=== Placing 90 degree corners ===
<youtube width="200" height="120">n2_XVZxwbbk</youtube>

=== Placing vertical bridges ===
<youtube width="200" height="120">wSX-TgiuqW0</youtube>

=== Stacking vertical bridges ===
<youtube width="200" height="120">WCl0UFyXt50</youtube>

[[Category:Building]] [[Category:Stations]] [[Category:Guides]]

YSuite

2021-08-03T17:37:24Z

Kabeck515:

{| class="infobox" style="float: right; clear: right; margin: 0 0 1em 1em; width: 400px;"
|-
| style="text-align: center; font-size: 90%;" |[[Image:YSuite Logo.png|400px]]
|-
|
{| style="background: none; width: 400px; margin: 0 auto;"
|-
! colspan="2" style="background-color: #5794D5; font-size: 120%; text-align: center;" align="center" | YSuite
|- style="vertical-align: top;"
|'''Dev'''||[[User:Senkii|Senkii]]
|- style="vertical-align: top;"
|'''Website'''||[http://ysuite.senkii.space YSuite homepage]
|}
|}

[http://ysuite.senkii.space/ YSuite website]

OBSOLETE

YSuite is a series of YOLOL-based products, focused on making life easier for shipbuilders, be they new to the game, or advanced builders who would like to save some time. YSuite is focused on easy installation, with every module being freely downloadable, while instructions for manual installation are also available.

== Modules ==

=== YS.pos ===

[[File:discord_YSpos.png|400px]]

YS.pos is a YOLOL-based GPS and velocity indication system.

YS.pos uses a single-receiver, single-chip setup, and has relatively accurate position and velocity indications while moving.

The module download and installation instructions for YS.pos are available on the [http://ysuite.senkii.space/pos/ YS.pos product page].