{{Otherlang2
|en=spaceship assembly guide
|fr=spaceship assembly guide:fr
|ru=Гайд по созданию кораблей
|ua=Гайд по будівництву кораблів
}}

== Summary ==

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

This guide is an introduction to spaceship building in Starbase. It will introduce the basics of spaceship hull structure, and basic devices and machinery needed for a working spaceship.

== Good To Know Before Starting ==
*You should have basic knowledge of device configurations and YOLOL in Starbase, as this guide includes machinery and devices.
*You should have basic knowledge of the Spaceship Designer before attempting spaceship assembly.
*Spaceship Designer: Pre-made blueprints/Tutorials/Tutorial Starter Spaceship
*In [[Spaceship_resources|Spaceship resources]] you will find information about different resources that spaceships will use.

== Spaceship Requirements ==
Each spaceship requires the following things to fly:

*Valid Frame/Hull
*Thrusters
*Powersource: Generator or Batteries
*Propellant for thrusters
*Data Network
*Pipe network for propellant
*Ship controls and basic configuration

== Valid Frame And Hull Structure ==
*All spaceships need to be built according to the durability rules in order to be able to fly without breaking.
**Foundation of the durability rules is the frame of beams which forms the ship’s hull, and to which everything else is attached to.

*A valid ship frame consists of beams connected to each other with attachment plates and bolts, and a valid thruster base (Device hardpoint) is connected to the beams directly.
**The hardpoint is connected to beams with at least two bolts, and an actual thruster is in contact with the hardpoint.
**The thruster has to be properly positioned (forming a data connection with the base) and connected to the same frame as the base.

*Ship frame must be consistent, there can't be two different frames that are not connected to each other.
**If there are two separate frames, the bigger one will be used as there can be only one frame.
<gallery widths=500px heights=400px mode="nolines">
File:Frame_example.jpg
</gallery>

=== Beam Frame ===
<gallery widths=500px heights=400px mode="nolines">
File:Attachment_plate_beam_example.jpg
</gallery>

=== Plates ===
====Outer Plates====
*Outer plating protects the ship from weapon fire, collisions and radiation during warp travel.
*There should not be any gaps on the exterior plating of the ship, otherwise radiation gets through during warp travel. Beams and plates withstand normal flying and there can be exposed beams if the ship is not meant for warp travel.
*Plates are connected to the frame with bolts.

====Inner Plates====
*The main difference between inner and outer plates is the material.
*Inner plating is not necessary regarding the ship's durability and ability fly, but makes it easier to walk inside the ship, and helps with weapon damage.
*It is recommended to have at least some interior plating to make character movement smoother and make the ship interior more aesthetic.
*Interior plating also helps when placing machinery, devices, cables and piping.
<gallery widths=300px heights=300px mode="nolines">
File:Outer_inner_plates_example.jpg
</gallery>

=== Hardpoints ===
*Thrusters and other machinery outside the ship’s hull have to be connected to the ship’s '''data network'''.
*Thrusters also need to be connected to the ship’s '''propellant gas network.'''
*Connecting thrusters and machinery to the spaceship networks is done with '''hardpoints'''.
*Hardpoints have pipe and cable slots for connecting pipes and cables. This means hardpoints need to be placed on the frame so that cabling and piping can be done.

*As thrusters need hardpoints to work, it is important to pay attention to where to place the hardpoints. Thruster locations greatly affect how the ship flies and how easily the ship can be maneuvered.
<gallery widths=400px heights=400px mode="nolines">
File:Hardpoint_example_.jpg
</gallery>

=== Modules ===

*Modules are plates, beams, etc. which are grouped together. The purpose of the modules is to make constructing spaceships faster and easier than using single parts.

*Every module has at least one Parent Object (Green Sphere) that ties the objects in the module together. Modules can be moved and rotated as a whole by having green sphere selected (module icon).

*'''It is highly recommended that beginners start building with modules.'''
**Using modules should automatically ensure that the spaceship structure is correct.
**Modules are the best way to learn the building grid and good building patterns.
**There is a lot of different building parts in the game and this can be overwhelming at first. Using modules reduces the number of building parts you need to remember.
**The building process will be faster and the progress is easier to notice.
**Basic modules for smaller and medium sized ships are introduced in: Premade blueprints/Tutorials/Tutorial Starter Spaceship
**The basic modules are for building 90 degree angles. This means the hull will have box-like appearance at first. The hull can be decorated with decoration parts and normal plates later on. 
<gallery widths=800px heights=900px mode="nolines">
File:Basic_starter_set_modules_guide_picture.jpg
</gallery>

=== The Grid ===
*Spaceship modules use a 48 cm grid. This is because the basic hull thickness is 48 cm.
*Outer plating (12 cm) + beam frame (24 cm) + inner plating (12 cm) = 48 cm
*Keeping the hull structure in the grid ensures that beams connect easily.
<gallery widths=400px heights=400px mode="nolines">
File:Grid_example.jpg
</gallery>

=== Bolting And Durability ===
*Each part of the ship has its own mass. In durability calculations, the mass of different parts is transferred towards the frame via connections (bolts) and other parts. This means parts close to the frame need to support all the parts further away from the frame.

*When building your first spaceship, it is good to do test bolting and durability checks in the middle of the building process. This way you can avoid unnecessary extra work and keep the hull structure consistent all the time.

*Durability Tool will report '''No ship frame''' when there are no thruster bases with connected thrusters connected to the frame. When there is at least one thruster properly connected to the thruster base and both are connected to the frame with bolts, Durability Tool will show '''Ship Warp Class X'''. If the ship warp class is lower than one, it means there are parts which are poorly connected to the frame.

*When the Durability Tool shows warp class for the ship, it also means that '''a frame integrity check''' can be done. (Durability tool→ Right mouse button). The frame integrity check basically studies how solidly each frame beam (and whatever it supports) is connected to the frame-attached thrusters.

<gallery widths=400px heights=400px mode="nolines">
File:Frame_integrity_check_SSC.jpg|If the frame design is not balanced enough, certain sections may encounter too much stress. This creates a durability error for the frame beam.
File:Frame_integrity_check_SSC_2.jpg|This is the same spot but some attachment plates and bolts have been removed between beams. Notice the color change which means those beams are about to fail.
</gallery>

== Thrusters ==
A spaceship needs thrusters to be able to fly and thrusters need to be bolted to the hull.

*Thrusters can be divided to two types: '''main thrusters''' and '''maneuver thrusters'''. Main thrusters generate forward movement and maneuver thrusters enable yaw, pitch and roll for example. Each thruster model can act as a main thruster or a maneuver thruster. To which movement the thruster will contribute, the defining factor is position and orientation of the thruster.

*Location of thrusters greatly affects how easy the ship is to maneuver. For example if your ship is missing forward facing thrusters, your ship won’t be able to fly backwards.

*Mass is also a factor when placing thrusters to your spaceship. Each beam, plate and machinery you have placed on your ship has mass. The bigger your ship is, more thrust it will need.

*Thrusters need '''electricity''' and '''propellant''' to work. Thrusters consume more propellant than power. This means civilian ships without weaponry can have smaller generators and mainly focus on propellant containers.

'''Maneuver thrusters'''
*Maneuver thrusters are usually smaller and don’t need to provide much thrust.
*There are three sizes of thrusters in Starbase: box thruster, triangle thruster and maneuver thruster. Each thruster can be used as a maneuver thruster even thought only one is named a ”maneuver thruster”.

'''Main thrusters'''
*Main thrusters are usually the thrusters that are facing backwards as this enables forward movement for the ship.

Maneuver thruster
*Max thrust: 50 000
*The small maneuver thruster is placed on a hardpoint

Box thruster
*Max thrust: 500 000
*The box thruster is connected to a hardpoint from the side and this thruster can’t be stacked

Triangle thruster
*Max thrust: 300 000
*The biggest difference the triangle thruster has compared to the other two thrusters is that it can be stacked. Only one triangle thruster needs connection with a hardpoint and more triangle thrusters can be connected to that thruster. Stacked triangle thrusters share same device field name which is linked to MFC and operate as a whole.

== Power Source ==
Machines and devices need power in spaceships. Power can be provided with generator or batteries

=== Generator ===
Generator pieces are modular and can be used to build bigger and smaller generators. 
Working generator will need at least one '''generator fuel chamber''', one '''small fuelrod,''' one '''generator unit''', one '''generator socket board''', one '''generator cooling rack''' and one '''small cooling cell'''.
*Place the generator in a way that there is enough room to pull out the fuel rod
*Also make sure there is an easy access to the socket board and to the coolant cells.
*The generator parts need to be bolted together and the generator needs to be bolted to the ship.
*Generator cooling can also provided by using Radiator

<gallery widths=400px heights=400px mode="nolines">
File:Generator_example.jpg
</gallery>

== Propellant ==
Thrusters need and consume propellant to work. Propellant is stored in propellant containers. The amount of containers spaceship will need depends on how many thrusters it has.
*There are three sizes of propellant containers: small, medium and large.
*While placing the propellant containers make sure there is an access to at least two of the sockets found in the tank support.
*The propellant container needs to be bolted to the ship.

== Data Network ==
The spaceship needs a cable network to transfer electricity to all the machinery and data between all the devices.
*Use the cabling tool to connect all the machinery and devices to the same network.
*Make sure that all the devices and machinery: thrusters, doors, MCU, FCU, levers, lamps and buttons are connected to the network.
<gallery widths=800px heights=800px mode="nolines">
File:Data_network_example.jpg
</gallery>
<gallery widths=400px heights=400px mode="nolines">
File:Data_network_example_02.jpg
</gallery>

== Pipe Network For Propellant ==
The spaceship needs a pipe network to transfer propellant to all thrusters from propellant containers.
*Use [[Pipe tool]] to connect all propellant containers and hardpoints with thrusters.
*To get information from propellant network, containers also need to be in electricity network. Connecting one propellant container support to electricity network can be used to show the total amount of propellant in the pipe network.
<gallery widths=800px heights=800px mode="nolines">
File:Pipe_network_example.jpg
</gallery>
<gallery widths=400px heights=400px mode="nolines">
File:Cable_piping_example.jpg
</gallery>

== Ship Controls And Basic Configuration ==
Spaceship thrusters can be controlled directly with levers, buttons and YOLOL. However YOLOL-configured thruster balance settings and flying are very ship specific configurations. The following guide explains how to use and configure Flight Control Unit (FCU) and Main Flight Computer (MFC) to do thruster balance calculations and settings for you.
*If you are interested about YOLOL configured thruster balance settings and flying you can examine Spaceship Vasama in the Spaceship Designer.

===Flight Control Unit (FCU)===

*'''The FCU''' gets input from control devices (levers and buttons) and sends it to the '''Main Flight Computer''', which forwards it to the thrusters.
*The arrows on top of the FCU define the ”forward” direction of the ship.
*There can be more than one FCU connected to one Main Flight Computer.
*There are currently three FCU models in Starbase: Basic, Advanced and Premium model. Each model has a different set of ship movements available.

'''Basic model''':
* FcuMfcIO (for connecting the MFC)
* FcuInputRange (Lever input range)
* FcuGeneralMultiplier (a "soft power switch", scales all output)
* FcuForward (moves the ship straight forward or combines FcuFwdBwd rotations with the forward movement)
* FcuBackward (moves the ship straight backward or combines FcuFwdBwd rotations with the backward movement)
* FcuRotationalPitch (in-place pitch rotation)
* FcuRotationalYaw (in-place yaw rotation)
* FcuRotationalRoll (in-place roll rotation)

'''Advanced model''' (in addition to the Basic controls):
* FcuUpDown (moves the ship straight up or down)
* FcuRightLeft (moves the ship straight right or left)

'''Premium model''' (in addition to the Advanced controls):
* FcuFwdBwdPitch (rotation combined to forward/backward movement)
* FcuFwdBwdYaw (rotation combined to forward/backward movement)
* FcuFwdBwdRoll (rotation combined to forward/backward movement)

[[File:FCU_and_MFC_assembly_guide.jpg|400px]]

===Main Flight Computer (MFC)===

*'''MFC''' is placed in the same data network with a '''Flight Control Unit''' and '''thrusters'''. The MFC and FCU share one identical device field name.
*MFC gets input from the Flight Control Unit and sends this data to the thrusters, telling them what to do. For example "pilot interacts with yaw lever". The FCU receives the information and sends it to the Main Flight Computer. The MFC then automatically decides which thursters are used to make the ship yaw.
*Each thruster group is controlled by exactly one MFC. There can be several MFCs in one ship.

===Levers===

The Flight Control Unit (FCU) gets input from control devices like levers and buttons. To get the levers to work with an FCU you need to configure the lever device fields to match with the FCU device fields (see picture below).

<gallery widths=600px heights=600px mode="nolines">
File:Lever_fcu_assembly_example.jpg|Examine '''FCU''' device fields and levers. Also notice matching device fields in the '''MFC''' and the '''FCU'''
</gallery>

====Lever Examples====

'''Note!''' These are examples for a ship that has an FCU and an MFC. Also the FCU input Range is set to 100.

<gallery widths=500px heights=500px mode="nolines">

File:Lever_assembly_example_1.jpg|Lever settings for '''forward thrust'''. If the FCU input range would be 1000, then LeverMaxOutput would be 1000 and LeverBindsMoveSpeed would be also higher
File:Lever_assembly_example_2.jpg|Centered lever settings for yaw. Notice LeverCenteringSpeed.

</gallery>

===Thruster configuration===

The Main Flight Computer controls the thrusters. One MFC can handle 50 thrusters, which means there are 50 device fields for thrusters in an MFC (thrusterPowerLevelXX). These field names are set for ship's thrusters. Field names can be renamed but each thruster should have a unique device field name (excluding stacked triangle thrusters).

<gallery widths=800px heights=600px mode="nolines">
File:data_network_example.jpg| Examine the '''MFC''' device fields (thrusterpowerlevel...) and thruster device field names set to thrusters throughout the data network
</gallery>
<gallery widths=500px heights=600px mode="nolines">
File:Thruster_device_field_example_01.jpg|A configured thruster: When a thruster is connected to same data network with an MFC and is given matching field name with the MFC thruster list, the values should automatically update and be the same. Also in this case '''ThrusterCurrentThrust''' field name has been changed to '''T07''' ( This can be linked to Progress Bar)
</gallery>

==Troubleshooting==

'''Checklist'''

Each spaceship needs the following things to fly:
*Valid frame/Hull
*Thrusters
*Powersource
*Propellant for thrusters
*Data Network
*Pipe network for propellant
*Ship controls and basic configuration

'''My ship is not moving?'''
# Check durability and bolting→ Thruster hardpoints are bolted to the frame and thrusters are bolted to the hardpoints/ hull. The ship frame is consistent and bolted.
# Thrusters need electricity and propellant → Check cabling and piping (all thruster hardpoints are connected to the electricity network and to the propellant pipe network.
# Electricity network (cable) is connected to the generator. Check that the generator has all the necessary parts → see 3. Powersource/generator
# Pipe network is connected to the propellant containers → see Pipe network for propellant
# Check the thruster configuration → see thruster configuration (matching device field names and values in MFC and in thrusters '''(If the ship is using an MFC)'''
# Check matching device field names in the MFC and FCU → see picture in Levers section
# Check matching device field names in the levers and in the FCU → see picture in Levers section

'''When I start flying my ship, some pieces of the ship detach?'''
*Use the Durability Tool. Check that everything is green and bolted.
'''My ship is almost symmetrical but still doesn’t fly straight/ turns easier to one direction?'''
*Some thrusters might not be working → Check : 1 , 2, 3, 4 ,5
'''All thrusters seem to working but ship yaw/pitch/roll is slow?'''
*In some cases you might need re-position thrusters or add more thrusters. Upgrading FCU to premium model which has combined movements possibilities can also be helpful in some cases.

[[Category:Guides]] [[Category:Spaceships]]

YOLOL/fr

2022-04-08T00:59:56Z

Danthbyrth: /* Les Opérateurs */ Traduction partielle

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

==Introduction==

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

le YOLOL est un langage de programmation spécifique à Starbase qui est utilisé en parallèle du l'[[Universal tool:fr|outil universel]] pour contrôler et gérer les [[Devices_and_machines:fr|appareils]]. 
Le code est écrit ligne par ligne sur une [[YOLOL Chip:fr|puce YOLOL]] qui est ensuite insérée dans un [[Chip socket:fr|socle à puce]] connecté au [[Data networks:fr|réseau de données]] du vaisseau afin d'accéder aux [[Device fields:fr|champs de périphérique]]. 
Le langage YOLOL est compatible avec presque tous les équipements et engins de l'univers connu.

===Comment ça marche?===
Le YOLOL fonctionne par cycle: Les lignes de code sont exécutées les unes après les autres du haut vers le bas, puis la séquence reprend une fois la dernière ligne passée. Chaque ligne est lue dans un intervalle de temps constant de 0.2 secondes, quelque soit sa longueur et le nombre d'instructions qui y sont contenues.

Pour faire simple:
# Le code se lance en commençant par la ligne 1
# La ligne en cours est exécutée, puis le programme passe à la suivante après un intervalle de temps de 0.2 secondes
# L'étape 2 est répétée pour les lignes 2, 3, 4... jusqu'à la dernière
# La puce se réinitialise à l'étape 1 une fois le processus terminé

===Limites===
* Chaque puce YOLOL contient 20 lignes de code. Ni plus, ni moins. L'exécution d'un cycle complet prend donc 20 * 0.2 = 4 secondes si il est mené à son terme.
* Chaque lignes peut contenir un maximum de 70 caractères (symboles et espaces inclus).

===Remarques===
* Les puces YOLOL possèdent une fonction de mise en pause, qui fige l'exécution du code à la ligne en cours.
* Les lignes blanches nécessitent tout de même l'intervalle de temps des 0.2 secondes pour être passées, provoquant de courts délais d'exécution (il en va de même pour les lignes ne contenant que des commentaires).
* Une seule ligne de code peut contenir plusieurs instructions à la fois, autant que peut le supporter la limite maximale de caractères.
* Certaines instructions permettent de passer à une ligne spécifique, ce qui rend le code plus modulable.

== Les Variables ==
Les variables permettent d'associer un '''nom''' à une '''valeur''' pour faciliter l'acquisition ultérieure de cette dernière. Dès lors, à chaque fois que le '''nom''' de la variable sera appelé, c'est sa '''valeur''' qui sera demandée et/ou modifiée suivant l'instruction utilisée.

* Exemple:
ButtonState = 1
* Dans ce script, on attribue à la variable nommée '''ButtonState''' la valeur numérique '''1'''.
if ButtonState >= 1 then DoorState = 1 end
* Maintenant, on vérifie si la valeur de la variable '''ButtonState''' est supérieure ou égale à '''1''', auquel cas la variable '''DoorState''' se voit elle aussi associée à '''1'''.

===Les Noms de Variables===
====Sensibilité à la casse====
Le langage YOLOL est dit "insensible à la casse", ce qui signifie que les noms des variables peuvent contenir des majuscules et des minuscules sans différencier les deux. Ainsi '''ButtonState''' et '''buttonstate''' désignent indistinctement la même variable. C'est une fonctionnalité très pratique pour rendre le code plus lisible.

====Les variables internes et externes====
Il existe deux genre de variables: les '''variables internes''' qui ne peuvent être utilisées qu'au sein de la puce YOLOL où elles ont été initiées et les '''variables externes''' qui font appel aux [[device fields:fr|champs de périphérique]] des appareils branchés sur le même [[data networks:fr|réseau de données]] pour en demander ou modifier les valeurs. 
Pour les différencier, les variables externes sont précédées d'un double-point (''':''').

* Exemple:
if :ButtonState >= 1 then :DoorState = 1 end
* Comme vu précédemment, ce script évalue la valeur de '''ButtonState''' et, si elle est supérieure ou égale à '''1''', associe '''DoorState''' à '''1'''. Les deux variables seront cependant ici appelées sur l'ensemble des équipements présents sur le réseau de données, par exemple pour ouvrir une porte si un bouton est appuyé. 

====Remarques====
* Les champs ayant le même nom au sein du réseau de données sont liées et ont presque toujours la même valeur. Ainsi, une variable externe qui en modifie la valeur le fera sur tout les appareils associés.
* Il n'est actuellement pas possible d'appeler une variable initiée sur un puce YOLOL depuis une autre puce YOLOL.

===Les Valeurs de Variables===
====Typage====
Le langage YOLOL supporte deux types de valeurs pour les variables: Les '''valeurs numériques''' et les '''chaînes de caractères''' (ou "string"). Cette différence est importante car en fonction du type de variable, le résultat d'une même instruction sera différente.

* Exemple:
Addition = 3 + 5
* Cette instruction conduit à additionner les deux valeurs numériques '''3''' et '''5'''. Le résultat sera donc '''8'''.
Addition = "3" + "5"
* Cette instruction conduit à associer les chaînes de caractères '''"3"''' et '''"5"'''. Le résultat sera donc '''"35"'''.

Les variables sont dites à "faible typage", c'est-à-dire qu'elles ne sont pas restreintes à un seul type. Elles se convertissent systématiquement aux valeurs qui leur sont assignées. Ainsi, une variable associée à une valeur numérique peut la remplacer par une chaîne de caractères et inversement sans provoquer d'erreur dans le code.

* Exemple:
AutoPilot = 128.643
* cette première instruction associe la variable '''AutoPilot''' à la valeur numérique '''128.643'''.
AutoPilot= "Erreur détectée"
* La variable '''AutoPilot''' se convertit en s'associant à la chaîne de caractères '''"Erreur détectée"''' et la valeur numérique '''128.643''' est effacée.

====Les valeurs numériques====
Les valeurs numérique dans le langage YOLOL sont des décimales à point fixe. La précision est de un millième: Jusqu'à trois nombre sous la décimale sont acceptés. Fournir une valeur plus précise fonctionne, mais n'affecte pas le résultat final. 

* Exemple:
Pi = 3,14159265
* Le script ci-dessus tente d'associer la variable '''Pi''' à la valeur numérique '''3,14159265'''. Le résultat final sera cependant '''Pi = 3.141''', coupant la précision à trois nombre sous la décimale.

La taille maximale d'une valeur numérique est de 64-bit. De ce fait, la portée maximale (même après opération) est de [-9223372036854775.808, 9223372036854775.807]. Toutes valeurs supérieures ou inférieures seront ramenées aux limites de la portée.

* Exemple:
StarTrek = 9999999999999999.999
* Ici, on tente d'associer la variable '''StarTrek''' à la valeur numérique '''9999999999999999.999'''. Celle-ci est cependant supérieure à la portée maximale et le résultat final sera '''StarTrek = 9223372036854775.807'''.

====Les chaînes de caractères====
Pour signaler une chaîne de caractères au langage YOLOL, celle-ci doit être entourée de double-guillemets ('''" "''').

BadRobots= "Saltberia"
* Ce script associe la variable '''BadRobot''' à la chaîne de caractères '''"Saltberia"'''.
Comme pour les valeurs numériques, la taille maximale d'une chaîne de caractères est de 64-bit.

====Remarques====
* Chaque variable ne peut être que d'un type à la fois, bien que celui-ci puisse être converti au besoin.
* Les valeurs "False" et "True" sont de type numérique: Elles correspondent respectivement à "0" et "non-0".
* Une variable non définie préalablement a par défaut la valeur numérique "0". L'absence de valeur ("null") n'est pas reconnue.

==Les Opérations==
A noter que si les opérations les plus basiques peuvent être utilisées par n'importe quelle [[YOLOL Chip:fr|puce YOLOL]], certaines plus complexes en nécessite des plus avancées, voire de qualité professionelle. 

=== Les opérateurs arythmétiques ===

{| class="wikitable"
|-
! Opération || Valeurs numériques || Chaînes de caractères || Puce nécessaire
|-
| A + B || Addition || "B" est ajouté à la suite de "A" || Basique
|-
| A - B || Soustraction || La dernière occurence de "B" dans "A" est supprimée || Basique
|-
| A * B || Multiplication || Erreur d'exécution. Le reste de la ligne est passé || Basique
|-
| A / B || Division || Erreur d'exécution. Le reste de la ligne est passé || Basique
|-
| A ^ B || Exponentielle || Erreur d'exécution. Le reste de la ligne est passé || Avancée
|-
| A % B || Modulo || Erreur d'exécution. Le reste de la ligne est passé || Avancée
|-
| ABS A || Absolue || Erreur d'exécution. Le reste de la ligne est passé || Avancée
|-
| A! || Factorielle || Erreur d'exécution. Le reste de la ligne est passé || Avancée
|-
| SQRT A || Racine carrée || Erreur d'exécution. Le reste de la ligne est passé || Avancée
|-
| SIN A || Sinus (degrés) || Erreur d'exécution. Le reste de la ligne est passé || Professionnelle
|-
| COS A || Cosinus (degrés) || Erreur d'exécution. Le reste de la ligne est passé || Professionnelle
|-
| TAN A || Tangente (degrés) || Erreur d'exécution. Le reste de la ligne est passé || Professionnelle
|-
| ASIN A || Sinus inversé (degrés) || Erreur d'exécution. Le reste de la ligne est passé || Professionnelle
|-
| ACOS A || Cosinus inversé (degrés) || Erreur d'exécution. Le reste de la ligne est passé || Professionnelle
|-
| ATAN A || Tangente inversée (degrés) || Erreur d'exécution. Le reste de la ligne est passé || Professionnelle
|}

===Les opérateurs d'assignation===

{| class="wikitable"
|-
! Operation || Valeurs numériques || Chaînes de caractères || Puce nécessaire
|-
| A = B || Assignation || Assignation || Basique
|-
| A += B || Addition-assignation (A=A+B) || Addition-assignation (A=A+B) || Basique
|-
| ++ A || Pré-incrémentation (A=A+1) || Ajoute un espace à la suite de "A". Evalué sur la valeur modifiée || Basique
|-
| A ++ || Post-incrémentation (A=A+1) || Ajoute un espace à la suite de "A". Evalué sur la valeur d'origine || Basique
|-
| A -= B || Soustraction-assignation (A=A-B) || Soustraction-assignation (A=A-B) || Basique
|-
| -- A || Pré-décrémentation (A=A-1) || Retire le dernier caractère de la chaîne. Erreur d'éxecution si la chaîne est vide. Evalué sur la valeur modifiée || Basique
|-
| A -- || Post-décrémentation (A=A-1) || Retire le dernier caractère de la chaîne. Erreur d'éxecution si la chaîne est vide. Evalué sur la valeur d'origine || Basique
|-
| A *= B || Multiplication-assignation (A=A*B) || Erreur d'exécution. Le reste de la ligne est passé || Basique
|-
| A /= B || Division-assignation (A=A/B) || Erreur d'exécution. Le reste de la ligne est passé || Basique
|-
| A ^= B || Exponentielle-assignation (A=A^B) || Erreur d'exécution. Le reste de la ligne est passé || Avancée
|-
| A %= B || Modulo-assignation (A=A%B) || Erreur d'exécution. Le reste de la ligne est passé || Avancée
|-
|}

=== Les opérateurs logiques ===

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 || A est plus grand que B || "A" est après "B" dans l'ordre alphabétique || Basique
|-
| A == B || A est égal à B || "A" est égale à "B" || Basique
|-
| A <= B || < ou == || < ou == || Basique
|-
| A >= B || > ou == || > ou == || Basique
|-
| A != B || A n'est pas égal à B || "A" n'est pas égale à "B" || Basique
|-
| NOT A || A est égal à 0 || "A" est 0 || Basique
|-
| A AND B || A et B ne sont pas égaux à 0 || "A" et "B" ne sont pas 0 || Basique
|-
| A OR B || A ou B n'est pas égal à 0 || "A" ou "B" n'est pas 0 || Basique
|}

=== Opérations sur des variables mixtes ===

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.

=== Ordre des opérations ===

Operations are conducted in the following order, when operators have the same precidence, left to right. 
Where a line has multiple statements, they are executed left to right.

{| class="wikitable"
|-
! Operateurs
|-
| Incrémentation (++), décrémentation (--)
|-
| Factorielle (!)
|-
| Racine carrée (sqrt), modulo (%), absolue (abs), sinus (sin), cosinus (cos), tangente (tan)
|-
| Négatif arythmétique (-)
|-
| Exponentielle (^)
|-
| Multiplication (*), division (/)
|-
| <, >, ==, !=, <=, >=
|-
| Addition (+), soustraction (-)
|-
| Négation logique (not)
|-
| "Ou" logique (or)
|-
| "Et" logique (and)
|-
|}

==Les Commandes==

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

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

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

== Les erreurs ==

Il y a deux types d'erreurs qui peuvent survenir pendant l'éxecution d'une séquence YOLOL:
# '''Les erreurs de syntaxe ("syntax errors")''': elles résultent d'un script invalide et empêchent l'interprétation de la ligne toute entière, qui est donc ignorée pour passer directement à la suivante.
# '''Les erreurs d'exécution ("runtime errors")''': elles ne sont détectées que pendant l'éxecution du script et provoquent l'arrêt de l'interprétation de la ligne en cours pour passer à la suivante. Elles n'impactent donc pas les instructions antérieures.

== Bugs connus/Comportements indésirables==
Voici une liste des problèmes relevés avec l'utilisation du langage YOLOL: 
* Les noms de variables contenant les mots-clé "if", "else" et "end" sont mal interprétés par le langage et provoquent une erreur de syntaxe. Les noms tels que '''life''' ou '''endurance''' sont donc à éviter.
*

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

== Pages associées ==
* [[Data networks:fr|Réseaux de données]]
* [[Devices and machines:fr|Appareils et machines]]
* [[Device fields:fr|Champs de périphérique ]]
* [[Universal tool:fr|Outil universel]]
* [[YOLOL Chip:fr|Puce YOLOL]]
* [[Chip socket:fr|Socle à puce]]

[[Category:Networks|YOLOL:fr]]

Spaceship assembly guide/fr

2022-04-07T22:51:01Z

Danthbyrth: Errata

Spaceship assembly guide/fr

2022-04-07T22:50:32Z

Danthbyrth: Ajout d'un lien vers la video Youtube

{{Otherlang2
|en=spaceship assembly guide
|fr=spaceship assembly guide:fr
|ru=Гайд по созданию кораблей
|ua=Гайд по будівництву кораблів
}}

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

== Summary ==
This guide is an introduction to spaceship building in Starbase. It will introduce the basics of spaceship hull structure, and basic devices and machinery needed for a working spaceship.

== Good To Know Before Starting ==
*You should have basic knowledge of device configurations and YOLOL in Starbase, as this guide includes machinery and devices.
*You should have basic knowledge of the Spaceship Designer before attempting spaceship assembly.
*Spaceship Designer: Pre-made blueprints/Tutorials/Tutorial Starter Spaceship
*In [[Spaceship_resources|Spaceship resources]] you will find information about different resources that spaceships will use.

== Spaceship Requirements ==
Each spaceship requires the following things to fly:

*Valid Frame/Hull
*Thrusters
*Powersource: Generator or Batteries
*Propellant for thrusters
*Data Network
*Pipe network for propellant
*Ship controls and basic configuration

== Valid Frame And Hull Structure ==
*All spaceships need to be built according to the durability rules in order to be able to fly without breaking.
**Foundation of the durability rules is the frame of beams which forms the ship’s hull, and to which everything else is attached to.

*A valid ship frame consists of beams connected to each other with attachment plates and bolts, and a valid thruster base (Device hardpoint) is connected to the beams directly.
**The hardpoint is connected to beams with at least two bolts, and an actual thruster is in contact with the hardpoint.
**The thruster has to be properly positioned (forming a data connection with the base) and connected to the same frame as the base.

*Ship frame must be consistent, there can't be two different frames that are not connected to each other.
**If there are two separate frames, the bigger one will be used as there can be only one frame.
<gallery widths=500px heights=400px mode="nolines">
File:Frame_example.jpg
</gallery>

=== Beam Frame ===
<gallery widths=500px heights=400px mode="nolines">
File:Attachment_plate_beam_example.jpg
</gallery>

=== Plates ===
====Outer Plates====
*Outer plating protects the ship from weapon fire, collisions and radiation during warp travel.
*There should not be any gaps on the exterior plating of the ship, otherwise radiation gets through during warp travel. Beams and plates withstand normal flying and there can be exposed beams if the ship is not meant for warp travel.
*Plates are connected to the frame with bolts.

====Inner Plates====
*The main difference between inner and outer plates is the material.
*Inner plating is not necessary regarding the ship's durability and ability fly, but makes it easier to walk inside the ship, and helps with weapon damage.
*It is recommended to have at least some interior plating to make character movement smoother and make the ship interior more aesthetic.
*Interior plating also helps when placing machinery, devices, cables and piping.
<gallery widths=300px heights=300px mode="nolines">
File:Outer_inner_plates_example.jpg
</gallery>

=== Hardpoints ===
*Thrusters and other machinery outside the ship’s hull have to be connected to the ship’s '''data network'''.
*Thrusters also need to be connected to the ship’s '''propellant gas network.'''
*Connecting thrusters and machinery to the spaceship networks is done with '''hardpoints'''.
*Hardpoints have pipe and cable slots for connecting pipes and cables. This means hardpoints need to be placed on the frame so that cabling and piping can be done.

*As thrusters need hardpoints to work, it is important to pay attention to where to place the hardpoints. Thruster locations greatly affect how the ship flies and how easily the ship can be maneuvered.
<gallery widths=400px heights=400px mode="nolines">
File:Hardpoint_example_.jpg
</gallery>

=== Modules ===

*Modules are plates, beams, etc. which are grouped together. The purpose of the modules is to make constructing spaceships faster and easier than using single parts.

*Every module has at least one Parent Object (Green Sphere) that ties the objects in the module together. Modules can be moved and rotated as a whole by having green sphere selected (module icon).

*'''It is highly recommended that beginners start building with modules.'''
**Using modules should automatically ensure that the spaceship structure is correct.
**Modules are the best way to learn the building grid and good building patterns.
**There is a lot of different building parts in the game and this can be overwhelming at first. Using modules reduces the number of building parts you need to remember.
**The building process will be faster and the progress is easier to notice.
**Basic modules for smaller and medium sized ships are introduced in: Premade blueprints/Tutorials/Tutorial Starter Spaceship
**The basic modules are for building 90 degree angles. This means the hull will have box-like appearance at first. The hull can be decorated with decoration parts and normal plates later on. 
<gallery widths=800px heights=900px mode="nolines">
File:Basic_starter_set_modules_guide_picture.jpg
</gallery>

=== The Grid ===
*Spaceship modules use a 48 cm grid. This is because the basic hull thickness is 48 cm.
*Outer plating (12 cm) + beam frame (24 cm) + inner plating (12 cm) = 48 cm
*Keeping the hull structure in the grid ensures that beams connect easily.
<gallery widths=400px heights=400px mode="nolines">
File:Grid_example.jpg
</gallery>

=== Bolting And Durability ===
*Each part of the ship has its own mass. In durability calculations, the mass of different parts is transferred towards the frame via connections (bolts) and other parts. This means parts close to the frame need to support all the parts further away from the frame.

*When building your first spaceship, it is good to do test bolting and durability checks in the middle of the building process. This way you can avoid unnecessary extra work and keep the hull structure consistent all the time.

*Durability Tool will report '''No ship frame''' when there are no thruster bases with connected thrusters connected to the frame. When there is at least one thruster properly connected to the thruster base and both are connected to the frame with bolts, Durability Tool will show '''Ship Warp Class X'''. If the ship warp class is lower than one, it means there are parts which are poorly connected to the frame.

*When the Durability Tool shows warp class for the ship, it also means that '''a frame integrity check''' can be done. (Durability tool→ Right mouse button). The frame integrity check basically studies how solidly each frame beam (and whatever it supports) is connected to the frame-attached thrusters.

<gallery widths=400px heights=400px mode="nolines">
File:Frame_integrity_check_SSC.jpg|If the frame design is not balanced enough, certain sections may encounter too much stress. This creates a durability error for the frame beam.
File:Frame_integrity_check_SSC_2.jpg|This is the same spot but some attachment plates and bolts have been removed between beams. Notice the color change which means those beams are about to fail.
</gallery>

== Thrusters ==
A spaceship needs thrusters to be able to fly and thrusters need to be bolted to the hull.

*Thrusters can be divided to two types: '''main thrusters''' and '''maneuver thrusters'''. Main thrusters generate forward movement and maneuver thrusters enable yaw, pitch and roll for example. Each thruster model can act as a main thruster or a maneuver thruster. To which movement the thruster will contribute, the defining factor is position and orientation of the thruster.

*Location of thrusters greatly affects how easy the ship is to maneuver. For example if your ship is missing forward facing thrusters, your ship won’t be able to fly backwards.

*Mass is also a factor when placing thrusters to your spaceship. Each beam, plate and machinery you have placed on your ship has mass. The bigger your ship is, more thrust it will need.

*Thrusters need '''electricity''' and '''propellant''' to work. Thrusters consume more propellant than power. This means civilian ships without weaponry can have smaller generators and mainly focus on propellant containers.

'''Maneuver thrusters'''
*Maneuver thrusters are usually smaller and don’t need to provide much thrust.
*There are three sizes of thrusters in Starbase: box thruster, triangle thruster and maneuver thruster. Each thruster can be used as a maneuver thruster even thought only one is named a ”maneuver thruster”.

'''Main thrusters'''
*Main thrusters are usually the thrusters that are facing backwards as this enables forward movement for the ship.

Maneuver thruster
*Max thrust: 50 000
*The small maneuver thruster is placed on a hardpoint

Box thruster
*Max thrust: 500 000
*The box thruster is connected to a hardpoint from the side and this thruster can’t be stacked

Triangle thruster
*Max thrust: 300 000
*The biggest difference the triangle thruster has compared to the other two thrusters is that it can be stacked. Only one triangle thruster needs connection with a hardpoint and more triangle thrusters can be connected to that thruster. Stacked triangle thrusters share same device field name which is linked to MFC and operate as a whole.

== Power Source ==
Machines and devices need power in spaceships. Power can be provided with generator or batteries

=== Generator ===
Generator pieces are modular and can be used to build bigger and smaller generators. 
Working generator will need at least one '''generator fuel chamber''', one '''small fuelrod,''' one '''generator unit''', one '''generator socket board''', one '''generator cooling rack''' and one '''small cooling cell'''.
*Place the generator in a way that there is enough room to pull out the fuel rod
*Also make sure there is an easy access to the socket board and to the coolant cells.
*The generator parts need to be bolted together and the generator needs to be bolted to the ship.
*Generator cooling can also provided by using Radiator

<gallery widths=400px heights=400px mode="nolines">
File:Generator_example.jpg
</gallery>

== Propellant ==
Thrusters need and consume propellant to work. Propellant is stored in propellant containers. The amount of containers spaceship will need depends on how many thrusters it has.
*There are three sizes of propellant containers: small, medium and large.
*While placing the propellant containers make sure there is an access to at least two of the sockets found in the tank support.
*The propellant container needs to be bolted to the ship.

== Data Network ==
The spaceship needs a cable network to transfer electricity to all the machinery and data between all the devices.
*Use the cabling tool to connect all the machinery and devices to the same network.
*Make sure that all the devices and machinery: thrusters, doors, MCU, FCU, levers, lamps and buttons are connected to the network.
<gallery widths=800px heights=800px mode="nolines">
File:Data_network_example.jpg
</gallery>
<gallery widths=400px heights=400px mode="nolines">
File:Data_network_example_02.jpg
</gallery>

== Pipe Network For Propellant ==
The spaceship needs a pipe network to transfer propellant to all thrusters from propellant containers.
*Use [[Pipe tool]] to connect all propellant containers and hardpoints with thrusters.
*To get information from propellant network, containers also need to be in electricity network. Connecting one propellant container support to electricity network can be used to show the total amount of propellant in the pipe network.
<gallery widths=800px heights=800px mode="nolines">
File:Pipe_network_example.jpg
</gallery>
<gallery widths=400px heights=400px mode="nolines">
File:Cable_piping_example.jpg
</gallery>

== Ship Controls And Basic Configuration ==
Spaceship thrusters can be controlled directly with levers, buttons and YOLOL. However YOLOL-configured thruster balance settings and flying are very ship specific configurations. The following guide explains how to use and configure Flight Control Unit (FCU) and Main Flight Computer (MFC) to do thruster balance calculations and settings for you.
*If you are interested about YOLOL configured thruster balance settings and flying you can examine Spaceship Vasama in the Spaceship Designer.

===Flight Control Unit (FCU)===

*'''The FCU''' gets input from control devices (levers and buttons) and sends it to the '''Main Flight Computer''', which forwards it to the thrusters.
*The arrows on top of the FCU define the ”forward” direction of the ship.
*There can be more than one FCU connected to one Main Flight Computer.
*There are currently three FCU models in Starbase: Basic, Advanced and Premium model. Each model has a different set of ship movements available.

'''Basic model''':
* FcuMfcIO (for connecting the MFC)
* FcuInputRange (Lever input range)
* FcuGeneralMultiplier (a "soft power switch", scales all output)
* FcuForward (moves the ship straight forward or combines FcuFwdBwd rotations with the forward movement)
* FcuBackward (moves the ship straight backward or combines FcuFwdBwd rotations with the backward movement)
* FcuRotationalPitch (in-place pitch rotation)
* FcuRotationalYaw (in-place yaw rotation)
* FcuRotationalRoll (in-place roll rotation)

'''Advanced model''' (in addition to the Basic controls):
* FcuUpDown (moves the ship straight up or down)
* FcuRightLeft (moves the ship straight right or left)

'''Premium model''' (in addition to the Advanced controls):
* FcuFwdBwdPitch (rotation combined to forward/backward movement)
* FcuFwdBwdYaw (rotation combined to forward/backward movement)
* FcuFwdBwdRoll (rotation combined to forward/backward movement)

[[File:FCU_and_MFC_assembly_guide.jpg|400px]]

===Main Flight Computer (MFC)===

*'''MFC''' is placed in the same data network with a '''Flight Control Unit''' and '''thrusters'''. The MFC and FCU share one identical device field name.
*MFC gets input from the Flight Control Unit and sends this data to the thrusters, telling them what to do. For example "pilot interacts with yaw lever". The FCU receives the information and sends it to the Main Flight Computer. The MFC then automatically decides which thursters are used to make the ship yaw.
*Each thruster group is controlled by exactly one MFC. There can be several MFCs in one ship.

===Levers===

The Flight Control Unit (FCU) gets input from control devices like levers and buttons. To get the levers to work with an FCU you need to configure the lever device fields to match with the FCU device fields (see picture below).

<gallery widths=600px heights=600px mode="nolines">
File:Lever_fcu_assembly_example.jpg|Examine '''FCU''' device fields and levers. Also notice matching device fields in the '''MFC''' and the '''FCU'''
</gallery>

====Lever Examples====

'''Note!''' These are examples for a ship that has an FCU and an MFC. Also the FCU input Range is set to 100.

<gallery widths=500px heights=500px mode="nolines">

File:Lever_assembly_example_1.jpg|Lever settings for '''forward thrust'''. If the FCU input range would be 1000, then LeverMaxOutput would be 1000 and LeverBindsMoveSpeed would be also higher
File:Lever_assembly_example_2.jpg|Centered lever settings for yaw. Notice LeverCenteringSpeed.

</gallery>

===Thruster configuration===

The Main Flight Computer controls the thrusters. One MFC can handle 50 thrusters, which means there are 50 device fields for thrusters in an MFC (thrusterPowerLevelXX). These field names are set for ship's thrusters. Field names can be renamed but each thruster should have a unique device field name (excluding stacked triangle thrusters).

<gallery widths=800px heights=600px mode="nolines">
File:data_network_example.jpg| Examine the '''MFC''' device fields (thrusterpowerlevel...) and thruster device field names set to thrusters throughout the data network
</gallery>
<gallery widths=500px heights=600px mode="nolines">
File:Thruster_device_field_example_01.jpg|A configured thruster: When a thruster is connected to same data network with an MFC and is given matching field name with the MFC thruster list, the values should automatically update and be the same. Also in this case '''ThrusterCurrentThrust''' field name has been changed to '''T07''' ( This can be linked to Progress Bar)
</gallery>

==Troubleshooting==

'''Checklist'''

Each spaceship needs the following things to fly:
*Valid frame/Hull
*Thrusters
*Powersource
*Propellant for thrusters
*Data Network
*Pipe network for propellant
*Ship controls and basic configuration

'''My ship is not moving?'''
# Check durability and bolting→ Thruster hardpoints are bolted to the frame and thrusters are bolted to the hardpoints/ hull. The ship frame is consistent and bolted.
# Thrusters need electricity and propellant → Check cabling and piping (all thruster hardpoints are connected to the electricity network and to the propellant pipe network.
# Electricity network (cable) is connected to the generator. Check that the generator has all the necessary parts → see 3. Powersource/generator
# Pipe network is connected to the propellant containers → see Pipe network for propellant
# Check the thruster configuration → see thruster configuration (matching device field names and values in MFC and in thrusters '''(If the ship is using an MFC)'''
# Check matching device field names in the MFC and FCU → see picture in Levers section
# Check matching device field names in the levers and in the FCU → see picture in Levers section

'''When I start flying my ship, some pieces of the ship detach?'''
*Use the Durability Tool. Check that everything is green and bolted.
'''My ship is almost symmetrical but still doesn’t fly straight/ turns easier to one direction?'''
*Some thrusters might not be working → Check : 1 , 2, 3, 4 ,5
'''All thrusters seem to working but ship yaw/pitch/roll is slow?'''
*In some cases you might need re-position thrusters or add more thrusters. Upgrading FCU to premium model which has combined movements possibilities can also be helpful in some cases.

[[Category:Guides]] [[Category:Spaceships]]

Spaceship assembly guide/fr

2022-04-07T22:46:33Z

Danthbyrth: Mise en place de la structure de base

{{Otherlang2
|ru=Гайд по созданию кораблей |ua=Гайд по будівництву кораблів
}}
== Summary ==
This guide is an introduction to spaceship building in Starbase. It will introduce the basics of spaceship hull structure, and basic devices and machinery needed for a working spaceship.

== Good To Know Before Starting ==
*You should have basic knowledge of device configurations and YOLOL in Starbase, as this guide includes machinery and devices.
*You should have basic knowledge of the Spaceship Designer before attempting spaceship assembly.
*Spaceship Designer: Pre-made blueprints/Tutorials/Tutorial Starter Spaceship
*In [[Spaceship_resources|Spaceship resources]] you will find information about different resources that spaceships will use.

== Spaceship Requirements ==
Each spaceship requires the following things to fly:

*Valid Frame/Hull
*Thrusters
*Powersource: Generator or Batteries
*Propellant for thrusters
*Data Network
*Pipe network for propellant
*Ship controls and basic configuration

== Valid Frame And Hull Structure ==
*All spaceships need to be built according to the durability rules in order to be able to fly without breaking.
**Foundation of the durability rules is the frame of beams which forms the ship’s hull, and to which everything else is attached to.

*A valid ship frame consists of beams connected to each other with attachment plates and bolts, and a valid thruster base (Device hardpoint) is connected to the beams directly.
**The hardpoint is connected to beams with at least two bolts, and an actual thruster is in contact with the hardpoint.
**The thruster has to be properly positioned (forming a data connection with the base) and connected to the same frame as the base.

*Ship frame must be consistent, there can't be two different frames that are not connected to each other.
**If there are two separate frames, the bigger one will be used as there can be only one frame.
<gallery widths=500px heights=400px mode="nolines">
File:Frame_example.jpg
</gallery>

=== Beam Frame ===
<gallery widths=500px heights=400px mode="nolines">
File:Attachment_plate_beam_example.jpg
</gallery>

=== Plates ===
====Outer Plates====
*Outer plating protects the ship from weapon fire, collisions and radiation during warp travel.
*There should not be any gaps on the exterior plating of the ship, otherwise radiation gets through during warp travel. Beams and plates withstand normal flying and there can be exposed beams if the ship is not meant for warp travel.
*Plates are connected to the frame with bolts.

====Inner Plates====
*The main difference between inner and outer plates is the material.
*Inner plating is not necessary regarding the ship's durability and ability fly, but makes it easier to walk inside the ship, and helps with weapon damage.
*It is recommended to have at least some interior plating to make character movement smoother and make the ship interior more aesthetic.
*Interior plating also helps when placing machinery, devices, cables and piping.
<gallery widths=300px heights=300px mode="nolines">
File:Outer_inner_plates_example.jpg
</gallery>

=== Hardpoints ===
*Thrusters and other machinery outside the ship’s hull have to be connected to the ship’s '''data network'''.
*Thrusters also need to be connected to the ship’s '''propellant gas network.'''
*Connecting thrusters and machinery to the spaceship networks is done with '''hardpoints'''.
*Hardpoints have pipe and cable slots for connecting pipes and cables. This means hardpoints need to be placed on the frame so that cabling and piping can be done.

*As thrusters need hardpoints to work, it is important to pay attention to where to place the hardpoints. Thruster locations greatly affect how the ship flies and how easily the ship can be maneuvered.
<gallery widths=400px heights=400px mode="nolines">
File:Hardpoint_example_.jpg
</gallery>

=== Modules ===

*Modules are plates, beams, etc. which are grouped together. The purpose of the modules is to make constructing spaceships faster and easier than using single parts.

*Every module has at least one Parent Object (Green Sphere) that ties the objects in the module together. Modules can be moved and rotated as a whole by having green sphere selected (module icon).

*'''It is highly recommended that beginners start building with modules.'''
**Using modules should automatically ensure that the spaceship structure is correct.
**Modules are the best way to learn the building grid and good building patterns.
**There is a lot of different building parts in the game and this can be overwhelming at first. Using modules reduces the number of building parts you need to remember.
**The building process will be faster and the progress is easier to notice.
**Basic modules for smaller and medium sized ships are introduced in: Premade blueprints/Tutorials/Tutorial Starter Spaceship
**The basic modules are for building 90 degree angles. This means the hull will have box-like appearance at first. The hull can be decorated with decoration parts and normal plates later on. 
<gallery widths=800px heights=900px mode="nolines">
File:Basic_starter_set_modules_guide_picture.jpg
</gallery>

=== The Grid ===
*Spaceship modules use a 48 cm grid. This is because the basic hull thickness is 48 cm.
*Outer plating (12 cm) + beam frame (24 cm) + inner plating (12 cm) = 48 cm
*Keeping the hull structure in the grid ensures that beams connect easily.
<gallery widths=400px heights=400px mode="nolines">
File:Grid_example.jpg
</gallery>

=== Bolting And Durability ===
*Each part of the ship has its own mass. In durability calculations, the mass of different parts is transferred towards the frame via connections (bolts) and other parts. This means parts close to the frame need to support all the parts further away from the frame.

*When building your first spaceship, it is good to do test bolting and durability checks in the middle of the building process. This way you can avoid unnecessary extra work and keep the hull structure consistent all the time.

*Durability Tool will report '''No ship frame''' when there are no thruster bases with connected thrusters connected to the frame. When there is at least one thruster properly connected to the thruster base and both are connected to the frame with bolts, Durability Tool will show '''Ship Warp Class X'''. If the ship warp class is lower than one, it means there are parts which are poorly connected to the frame.

*When the Durability Tool shows warp class for the ship, it also means that '''a frame integrity check''' can be done. (Durability tool→ Right mouse button). The frame integrity check basically studies how solidly each frame beam (and whatever it supports) is connected to the frame-attached thrusters.

<gallery widths=400px heights=400px mode="nolines">
File:Frame_integrity_check_SSC.jpg|If the frame design is not balanced enough, certain sections may encounter too much stress. This creates a durability error for the frame beam.
File:Frame_integrity_check_SSC_2.jpg|This is the same spot but some attachment plates and bolts have been removed between beams. Notice the color change which means those beams are about to fail.
</gallery>

== Thrusters ==
A spaceship needs thrusters to be able to fly and thrusters need to be bolted to the hull.

*Thrusters can be divided to two types: '''main thrusters''' and '''maneuver thrusters'''. Main thrusters generate forward movement and maneuver thrusters enable yaw, pitch and roll for example. Each thruster model can act as a main thruster or a maneuver thruster. To which movement the thruster will contribute, the defining factor is position and orientation of the thruster.

*Location of thrusters greatly affects how easy the ship is to maneuver. For example if your ship is missing forward facing thrusters, your ship won’t be able to fly backwards.

*Mass is also a factor when placing thrusters to your spaceship. Each beam, plate and machinery you have placed on your ship has mass. The bigger your ship is, more thrust it will need.

*Thrusters need '''electricity''' and '''propellant''' to work. Thrusters consume more propellant than power. This means civilian ships without weaponry can have smaller generators and mainly focus on propellant containers.

'''Maneuver thrusters'''
*Maneuver thrusters are usually smaller and don’t need to provide much thrust.
*There are three sizes of thrusters in Starbase: box thruster, triangle thruster and maneuver thruster. Each thruster can be used as a maneuver thruster even thought only one is named a ”maneuver thruster”.

'''Main thrusters'''
*Main thrusters are usually the thrusters that are facing backwards as this enables forward movement for the ship.

Maneuver thruster
*Max thrust: 50 000
*The small maneuver thruster is placed on a hardpoint

Box thruster
*Max thrust: 500 000
*The box thruster is connected to a hardpoint from the side and this thruster can’t be stacked

Triangle thruster
*Max thrust: 300 000
*The biggest difference the triangle thruster has compared to the other two thrusters is that it can be stacked. Only one triangle thruster needs connection with a hardpoint and more triangle thrusters can be connected to that thruster. Stacked triangle thrusters share same device field name which is linked to MFC and operate as a whole.

== Power Source ==
Machines and devices need power in spaceships. Power can be provided with generator or batteries

=== Generator ===
Generator pieces are modular and can be used to build bigger and smaller generators. 
Working generator will need at least one '''generator fuel chamber''', one '''small fuelrod,''' one '''generator unit''', one '''generator socket board''', one '''generator cooling rack''' and one '''small cooling cell'''.
*Place the generator in a way that there is enough room to pull out the fuel rod
*Also make sure there is an easy access to the socket board and to the coolant cells.
*The generator parts need to be bolted together and the generator needs to be bolted to the ship.
*Generator cooling can also provided by using Radiator

<gallery widths=400px heights=400px mode="nolines">
File:Generator_example.jpg
</gallery>

== Propellant ==
Thrusters need and consume propellant to work. Propellant is stored in propellant containers. The amount of containers spaceship will need depends on how many thrusters it has.
*There are three sizes of propellant containers: small, medium and large.
*While placing the propellant containers make sure there is an access to at least two of the sockets found in the tank support.
*The propellant container needs to be bolted to the ship.

== Data Network ==
The spaceship needs a cable network to transfer electricity to all the machinery and data between all the devices.
*Use the cabling tool to connect all the machinery and devices to the same network.
*Make sure that all the devices and machinery: thrusters, doors, MCU, FCU, levers, lamps and buttons are connected to the network.
<gallery widths=800px heights=800px mode="nolines">
File:Data_network_example.jpg
</gallery>
<gallery widths=400px heights=400px mode="nolines">
File:Data_network_example_02.jpg
</gallery>

== Pipe Network For Propellant ==
The spaceship needs a pipe network to transfer propellant to all thrusters from propellant containers.
*Use [[Pipe tool]] to connect all propellant containers and hardpoints with thrusters.
*To get information from propellant network, containers also need to be in electricity network. Connecting one propellant container support to electricity network can be used to show the total amount of propellant in the pipe network.
<gallery widths=800px heights=800px mode="nolines">
File:Pipe_network_example.jpg
</gallery>
<gallery widths=400px heights=400px mode="nolines">
File:Cable_piping_example.jpg
</gallery>

== Ship Controls And Basic Configuration ==
Spaceship thrusters can be controlled directly with levers, buttons and YOLOL. However YOLOL-configured thruster balance settings and flying are very ship specific configurations. The following guide explains how to use and configure Flight Control Unit (FCU) and Main Flight Computer (MFC) to do thruster balance calculations and settings for you.
*If you are interested about YOLOL configured thruster balance settings and flying you can examine Spaceship Vasama in the Spaceship Designer.

===Flight Control Unit (FCU)===

*'''The FCU''' gets input from control devices (levers and buttons) and sends it to the '''Main Flight Computer''', which forwards it to the thrusters.
*The arrows on top of the FCU define the ”forward” direction of the ship.
*There can be more than one FCU connected to one Main Flight Computer.
*There are currently three FCU models in Starbase: Basic, Advanced and Premium model. Each model has a different set of ship movements available.

'''Basic model''':
* FcuMfcIO (for connecting the MFC)
* FcuInputRange (Lever input range)
* FcuGeneralMultiplier (a "soft power switch", scales all output)
* FcuForward (moves the ship straight forward or combines FcuFwdBwd rotations with the forward movement)
* FcuBackward (moves the ship straight backward or combines FcuFwdBwd rotations with the backward movement)
* FcuRotationalPitch (in-place pitch rotation)
* FcuRotationalYaw (in-place yaw rotation)
* FcuRotationalRoll (in-place roll rotation)

'''Advanced model''' (in addition to the Basic controls):
* FcuUpDown (moves the ship straight up or down)
* FcuRightLeft (moves the ship straight right or left)

'''Premium model''' (in addition to the Advanced controls):
* FcuFwdBwdPitch (rotation combined to forward/backward movement)
* FcuFwdBwdYaw (rotation combined to forward/backward movement)
* FcuFwdBwdRoll (rotation combined to forward/backward movement)

[[File:FCU_and_MFC_assembly_guide.jpg|400px]]

===Main Flight Computer (MFC)===

*'''MFC''' is placed in the same data network with a '''Flight Control Unit''' and '''thrusters'''. The MFC and FCU share one identical device field name.
*MFC gets input from the Flight Control Unit and sends this data to the thrusters, telling them what to do. For example "pilot interacts with yaw lever". The FCU receives the information and sends it to the Main Flight Computer. The MFC then automatically decides which thursters are used to make the ship yaw.
*Each thruster group is controlled by exactly one MFC. There can be several MFCs in one ship.

===Levers===

The Flight Control Unit (FCU) gets input from control devices like levers and buttons. To get the levers to work with an FCU you need to configure the lever device fields to match with the FCU device fields (see picture below).

<gallery widths=600px heights=600px mode="nolines">
File:Lever_fcu_assembly_example.jpg|Examine '''FCU''' device fields and levers. Also notice matching device fields in the '''MFC''' and the '''FCU'''
</gallery>

====Lever Examples====

'''Note!''' These are examples for a ship that has an FCU and an MFC. Also the FCU input Range is set to 100.

<gallery widths=500px heights=500px mode="nolines">

File:Lever_assembly_example_1.jpg|Lever settings for '''forward thrust'''. If the FCU input range would be 1000, then LeverMaxOutput would be 1000 and LeverBindsMoveSpeed would be also higher
File:Lever_assembly_example_2.jpg|Centered lever settings for yaw. Notice LeverCenteringSpeed.

</gallery>

===Thruster configuration===

The Main Flight Computer controls the thrusters. One MFC can handle 50 thrusters, which means there are 50 device fields for thrusters in an MFC (thrusterPowerLevelXX). These field names are set for ship's thrusters. Field names can be renamed but each thruster should have a unique device field name (excluding stacked triangle thrusters).

<gallery widths=800px heights=600px mode="nolines">
File:data_network_example.jpg| Examine the '''MFC''' device fields (thrusterpowerlevel...) and thruster device field names set to thrusters throughout the data network
</gallery>
<gallery widths=500px heights=600px mode="nolines">
File:Thruster_device_field_example_01.jpg|A configured thruster: When a thruster is connected to same data network with an MFC and is given matching field name with the MFC thruster list, the values should automatically update and be the same. Also in this case '''ThrusterCurrentThrust''' field name has been changed to '''T07''' ( This can be linked to Progress Bar)
</gallery>

==Troubleshooting==

'''Checklist'''

Each spaceship needs the following things to fly:
*Valid frame/Hull
*Thrusters
*Powersource
*Propellant for thrusters
*Data Network
*Pipe network for propellant
*Ship controls and basic configuration

'''My ship is not moving?'''
# Check durability and bolting→ Thruster hardpoints are bolted to the frame and thrusters are bolted to the hardpoints/ hull. The ship frame is consistent and bolted.
# Thrusters need electricity and propellant → Check cabling and piping (all thruster hardpoints are connected to the electricity network and to the propellant pipe network.
# Electricity network (cable) is connected to the generator. Check that the generator has all the necessary parts → see 3. Powersource/generator
# Pipe network is connected to the propellant containers → see Pipe network for propellant
# Check the thruster configuration → see thruster configuration (matching device field names and values in MFC and in thrusters '''(If the ship is using an MFC)'''
# Check matching device field names in the MFC and FCU → see picture in Levers section
# Check matching device field names in the levers and in the FCU → see picture in Levers section

'''When I start flying my ship, some pieces of the ship detach?'''
*Use the Durability Tool. Check that everything is green and bolted.
'''My ship is almost symmetrical but still doesn’t fly straight/ turns easier to one direction?'''
*Some thrusters might not be working → Check : 1 , 2, 3, 4 ,5
'''All thrusters seem to working but ship yaw/pitch/roll is slow?'''
*In some cases you might need re-position thrusters or add more thrusters. Upgrading FCU to premium model which has combined movements possibilities can also be helpful in some cases.

[[Category:Guides]] [[Category:Spaceships]]

Page d’accueil

2022-04-07T22:45:51Z

Danthbyrth: errata

{{OtherlangMP
|en=Main_Page
|de=Main_Page:de
|ru=Главная_страница
|zh-cn=主页
|pl=Main_Page:pl
|nl=Main_Page:nl
}}
__NOTOC__
{{#css:
span.approvedAndLatestMsg {
display: none;
}
span.approvingUser {
display: none;
}
h1 {
display: none;
}
}}
<div class="mpRow">
<div id="mpLeftPadding"> 
{| class="wikitableNoGrid" style="border: 0px !important; margin: -10px; width: calc(100% + 20px);"
!colspan="1"|À propos de Starbase
|}
[[File:AboutStarbaseRobot.png|150px|right]]
 
Dans l'univers de Starbase tout le monde contrôle un [[Endoskeleton/fr|endosquelette]] robotique, un corps assez durable étant idéal pour l'exploration spatiale et la colonisation. La société, formée de ces robotiques endosquelettes est actuellement concentrée sur de gigantesques [[Capital_Mega_Station/fr|Super Stations]] et de plus petites Mini Stations, les "banlieues" dans l'espace. Les stations fournissent sécurité, [[jobs/fr|travail]], point de rencontre et possibilités d'échange pour leurs habitants, faisant d'elles des bases idéales où commencer la colonisation de la galaxie.

Dans la galaxie, les deux principales factions sont deux factions rivales, le [[Kingdom/fr|Royaume]] et l'[[Empire/fr|Empire]], l'Empire ayant le contrôle de la majorité des stations centrales. Les autres factions peuvent tout de même espérer ce placer à coté de ces deux géants un jour, avec l'évolution et la progression la société. 

La [[News Broadcasts/fr|vie]] dans l'[[Space/fr|espace]] étant actuellement centrée sur l'orbite céleste d'une planète gazeuse, les courageux aventuriers devront constamment explorer les limites du voyage spatial et d'autres technologies afin de pouvoir, un jour atteindre les coins les plus reculés de la galaxie.

{| class="wikitableNoGrid" style="border: 0px !important; margin: -10px; width: calc(100% + 20px);"
!colspan="1"|Menu
|}

[[Main_Page/fr|Menu principal]]

[[Special:AllPages|Toutes les pages]]

[[Special:RecentChanges|Changement récent]]

[[Special:SpecialPages|Page spécial]]

[[News Broadcasts/fr|Diffusions de nouvelles]]

[[Special:Random|Page aléatoire]]

[[Rules/fr|Règlement]]

[[Jobs/fr|Carrière]]

[[Endoskeleton CV/fr|Curriculum vitæ]]

[[Emotes/fr|Emotes]]

[[Endoskeleton/fr|Endosquelette]]

[[Insurance/fr|Assurance]]

[[Data networks/fr|Réseaux de données]]

[[Pipe networks/fr|Réseaux de canalisation]]

[[Resource networks/fr|Réseau de ressources]]

[[YOLOL:fr|Langage YOLOL]]

[[FAQ/fr|Foire au questions]]

[[Spaceship assembly guide:fr|Guide d'assemblage du vaisseau spatial]]

</div>
<div id="mpMiddle"> 
{| class="wikitableTransparent" style="margin-right: auto; margin-left: auto; border: none; margin-top: -3px;
|-

| Armes[[File:Combat_simulations_notext.png|175px|link=Weapons/fr|center]]
| Équipements[[File:Devices_notext.png|175px|link=Devices_and_machines/fr|center]]
| Matériaux[[File:Materials_notext.png|175px|link=Materials/fr|center]]
|-

| Vaisseaux[[File:Spaceships_notext.png|175px|link=Spaceships/fr|center]]
| Stations[[File:Stations_Table_Test_notext.png|175px|link=Stations/fr|center]]
| Outils[[File:Tools_notext.png|175px|link=Tools/fr|center]]
|-

| Univers[[File:Space_category.png|175px|link=Space/fr|center]]
| Politiques[[File:Factions_notext.png|175px|link=Factions/fr|center]]
| Construction[[File:Sb_building_feature_block.png|175px|link=Building/fr|center]]
|-

|}

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

 
{| class="wikitableTransparent" style="margin-right: auto; margin-left: auto; border: none
!colspan="6"|Galerie de Fonctionnalités
|-
|rowspan="2"|[[File:Starbase_marketing_screenshot_derelict_1080p.png|214px]]
|[[File:Screnshot_several_spaceships.png |96px]]
|rowspan="2"|[[File:Screenshot_Bolt_tool.png|214px]]
|-

| [[File:Screenshot_megastation_1080p.png|96px]]
|-
|}

</div>
<div id="mpRight"> 
{| class="wikitableNoGrid" style="margin: auto; border: none"
!colspan="4"|[[Weapons/fr|Armes]]
|-

| [[File:Assault rifle thumb.png|120px|link=Assault_rifle/fr|thumb|center|Fusil d’assaut]]
| [[File:Antigel thumb.png|120px|link=Antigel_rifle/fr|thumb|center|Fusil antigel]]
| [[File:Battle rifle thumb.png|120px|link=Battle_rifle/fr|thumb|center|Fusil de combat]]
| [[File:Bolter thumb.png|120px|link=Bolter/fr|thumb|center|Fusil à arc électrique]]
|-

| [[File:Flamer thumb.png|120px|link=Flamethrower/fr|thumb|center|Lance-flamme]]
| [[File:Gauss rifle thumb.png|120px|link=Gauss_rifle/fr|thumb|center|Fusil magnétique]]
| [[File:Laser rifle thumb.png|120px|link=Laser_rifle/fr|thumb|center|Fusil laser]]
| [[File:Long rifle thumb.png|120px|link=Long_rifle/fr|thumb|center|Fusil à longue portée]]
|-

| [[File:Pistol thumb.png|120px|link=Pistol/fr|thumb|center|Pistolet]]
| [[File:Repeater thumb.png|120px|link=Repeater_pistol/fr|thumb|center|Pistolet-mitrailleur]]
| [[File:Revolver thumb.png|120px|link=Revolver/fr|thumb|center|Revolver]]
| [[File:Shotgun thumb.png|120px|link=Shotgun/fr|thumb|center|Fusil à pompe]]
|-

|}
 

{| class="wikitableNoGrid" style="margin: auto; border: none;"
!colspan="4"|[[Mounted weapons/fr|Armes Montées]]
|-

| [[File:Autocannon.png|120px|link=Autocannon/fr|thumb|center|Auto-canon]]
| [[File:Laser weapon.png|120px|link=Laser cannon/fr|thumb|center|Canon laser]]
| [[File:Plasma cannon.png|120px|link=Plasma thrower/fr|thumb|center|Lance-plasma]]
| [[File:Rail weapon.png|120px|link=Rail cannon/fr|thumb|center|Canon à rail]]
|-

|}
 

{| class="wikitableNoGrid" style="margin: auto;" border: none
!colspan="4"|[[Spaceships/fr|Vaisseaux]]
|-

| [[File:Spaceship hedron decal.jpg|120px|link=Hedron/fr|thumb|center|Hedron]]
| [[File:Spaceship Ithaca.jpg|120px|link=Ithaca/fr|thumb|center|Ithaca]]
| [[File:Spaceship remus.jpg|120px|link=Remus/fr|thumb|center|Remus]]
| [[File:Spaceship urchin decal.jpg|120px|link=Urchin/fr|thumb|center|Urchin]]
|-

| [[File:Spaceship Empire Lictor.JPG|120px|link=Lictor/fr|thumb|center|Lictor]]
| [[File:Empire_spatha.jpg|120px|link=Spatha/fr|thumb|center|Spatha]]
| [[File:Kingdom_knight.jpg|120px|link=Knight/fr|thumb|center|Knight]]
| [[File:Kingdom_lancer.jpg|120px|link=Lancer/fr|thumb|center|Lancer]]
|-

|}

Page d’accueil

2022-04-07T22:44:46Z

Danthbyrth: ajout d'un lien vers "spaceship assembly guide:fr"

{{OtherlangMP
|en=Main_Page
|de=Main_Page:de
|ru=Главная_страница
|zh-cn=主页
|pl=Main_Page:pl
|nl=Main_Page:nl
}}
__NOTOC__
{{#css:
span.approvedAndLatestMsg {
display: none;
}
span.approvingUser {
display: none;
}
h1 {
display: none;
}
}}
<div class="mpRow">
<div id="mpLeftPadding"> 
{| class="wikitableNoGrid" style="border: 0px !important; margin: -10px; width: calc(100% + 20px);"
!colspan="1"|À propos de Starbase
|}
[[File:AboutStarbaseRobot.png|150px|right]]
 
Dans l'univers de Starbase tout le monde contrôle un [[Endoskeleton/fr|endosquelette]] robotique, un corps assez durable étant idéal pour l'exploration spatiale et la colonisation. La société, formée de ces robotiques endosquelettes est actuellement concentrée sur de gigantesques [[Capital_Mega_Station/fr|Super Stations]] et de plus petites Mini Stations, les "banlieues" dans l'espace. Les stations fournissent sécurité, [[jobs/fr|travail]], point de rencontre et possibilités d'échange pour leurs habitants, faisant d'elles des bases idéales où commencer la colonisation de la galaxie.

Dans la galaxie, les deux principales factions sont deux factions rivales, le [[Kingdom/fr|Royaume]] et l'[[Empire/fr|Empire]], l'Empire ayant le contrôle de la majorité des stations centrales. Les autres factions peuvent tout de même espérer ce placer à coté de ces deux géants un jour, avec l'évolution et la progression la société. 

La [[News Broadcasts/fr|vie]] dans l'[[Space/fr|espace]] étant actuellement centrée sur l'orbite céleste d'une planète gazeuse, les courageux aventuriers devront constamment explorer les limites du voyage spatial et d'autres technologies afin de pouvoir, un jour atteindre les coins les plus reculés de la galaxie.

{| class="wikitableNoGrid" style="border: 0px !important; margin: -10px; width: calc(100% + 20px);"
!colspan="1"|Menu
|}

[[Main_Page/fr|Menu principal]]

[[Special:AllPages|Toutes les pages]]

[[Special:RecentChanges|Changement récent]]

[[Special:SpecialPages|Page spécial]]

[[News Broadcasts/fr|Diffusions de nouvelles]]

[[Special:Random|Page aléatoire]]

[[Rules/fr|Règlement]]

[[Jobs/fr|Carrière]]

[[Endoskeleton CV/fr|Curriculum vitæ]]

[[Emotes/fr|Emotes]]

[[Endoskeleton/fr|Endosquelette]]

[[Insurance/fr|Assurance]]

[[Data networks/fr|Réseaux de données]]

[[Pipe networks/fr|Réseaux de canalisation]]

[[Resource networks/fr|Réseau de ressources]]

[[YOLOL:fr|Langage YOLOL]]

[[FAQ/fr|Foire au questions]]

[[Spaceship_Assembly_Guide:fr|Guide d'assemblage du vaisseau spatial]]

</div>
<div id="mpMiddle"> 
{| class="wikitableTransparent" style="margin-right: auto; margin-left: auto; border: none; margin-top: -3px;
|-

| Armes[[File:Combat_simulations_notext.png|175px|link=Weapons/fr|center]]
| Équipements[[File:Devices_notext.png|175px|link=Devices_and_machines/fr|center]]
| Matériaux[[File:Materials_notext.png|175px|link=Materials/fr|center]]
|-

| Vaisseaux[[File:Spaceships_notext.png|175px|link=Spaceships/fr|center]]
| Stations[[File:Stations_Table_Test_notext.png|175px|link=Stations/fr|center]]
| Outils[[File:Tools_notext.png|175px|link=Tools/fr|center]]
|-

| Univers[[File:Space_category.png|175px|link=Space/fr|center]]
| Politiques[[File:Factions_notext.png|175px|link=Factions/fr|center]]
| Construction[[File:Sb_building_feature_block.png|175px|link=Building/fr|center]]
|-

|}

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

 
{| class="wikitableTransparent" style="margin-right: auto; margin-left: auto; border: none
!colspan="6"|Galerie de Fonctionnalités
|-
|rowspan="2"|[[File:Starbase_marketing_screenshot_derelict_1080p.png|214px]]
|[[File:Screnshot_several_spaceships.png |96px]]
|rowspan="2"|[[File:Screenshot_Bolt_tool.png|214px]]
|-

| [[File:Screenshot_megastation_1080p.png|96px]]
|-
|}

</div>
<div id="mpRight"> 
{| class="wikitableNoGrid" style="margin: auto; border: none"
!colspan="4"|[[Weapons/fr|Armes]]
|-

| [[File:Assault rifle thumb.png|120px|link=Assault_rifle/fr|thumb|center|Fusil d’assaut]]
| [[File:Antigel thumb.png|120px|link=Antigel_rifle/fr|thumb|center|Fusil antigel]]
| [[File:Battle rifle thumb.png|120px|link=Battle_rifle/fr|thumb|center|Fusil de combat]]
| [[File:Bolter thumb.png|120px|link=Bolter/fr|thumb|center|Fusil à arc électrique]]
|-

| [[File:Flamer thumb.png|120px|link=Flamethrower/fr|thumb|center|Lance-flamme]]
| [[File:Gauss rifle thumb.png|120px|link=Gauss_rifle/fr|thumb|center|Fusil magnétique]]
| [[File:Laser rifle thumb.png|120px|link=Laser_rifle/fr|thumb|center|Fusil laser]]
| [[File:Long rifle thumb.png|120px|link=Long_rifle/fr|thumb|center|Fusil à longue portée]]
|-

| [[File:Pistol thumb.png|120px|link=Pistol/fr|thumb|center|Pistolet]]
| [[File:Repeater thumb.png|120px|link=Repeater_pistol/fr|thumb|center|Pistolet-mitrailleur]]
| [[File:Revolver thumb.png|120px|link=Revolver/fr|thumb|center|Revolver]]
| [[File:Shotgun thumb.png|120px|link=Shotgun/fr|thumb|center|Fusil à pompe]]
|-

|}
 

{| class="wikitableNoGrid" style="margin: auto; border: none;"
!colspan="4"|[[Mounted weapons/fr|Armes Montées]]
|-

| [[File:Autocannon.png|120px|link=Autocannon/fr|thumb|center|Auto-canon]]
| [[File:Laser weapon.png|120px|link=Laser cannon/fr|thumb|center|Canon laser]]
| [[File:Plasma cannon.png|120px|link=Plasma thrower/fr|thumb|center|Lance-plasma]]
| [[File:Rail weapon.png|120px|link=Rail cannon/fr|thumb|center|Canon à rail]]
|-

|}
 

{| class="wikitableNoGrid" style="margin: auto;" border: none
!colspan="4"|[[Spaceships/fr|Vaisseaux]]
|-

| [[File:Spaceship hedron decal.jpg|120px|link=Hedron/fr|thumb|center|Hedron]]
| [[File:Spaceship Ithaca.jpg|120px|link=Ithaca/fr|thumb|center|Ithaca]]
| [[File:Spaceship remus.jpg|120px|link=Remus/fr|thumb|center|Remus]]
| [[File:Spaceship urchin decal.jpg|120px|link=Urchin/fr|thumb|center|Urchin]]
|-

| [[File:Spaceship Empire Lictor.JPG|120px|link=Lictor/fr|thumb|center|Lictor]]
| [[File:Empire_spatha.jpg|120px|link=Spatha/fr|thumb|center|Spatha]]
| [[File:Kingdom_knight.jpg|120px|link=Knight/fr|thumb|center|Knight]]
| [[File:Kingdom_lancer.jpg|120px|link=Lancer/fr|thumb|center|Lancer]]
|-

|}

2022-02-15T18:32:40Z

Danthbyrth: Increasing overall readability for future modifications

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.''

: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

==[[Fuel chamber|Fuel Chamber]]==

The following scripts are made to be used with the ship "[[Laborer module|Laborer Module]]" rewarded during the tutorials. To make it compatible with other prebuilt or own-made ships, refer to the table below for the corresponding modifications in the [[Device fields|device fields]].

{| class="wikitable"
! Ship Part !! Default Field Name !! Laborer Module Field Name
|-
| Fuel Chamber || FuelChamberUnitRateLimit || Generator
|-
| First Battery || StoredBatteryPower || Battery_1
|-
| Second Battery || StoredBatteryPower || Battery_2
|}

Also, ships will require enough batteries to act as buffers during the generator spool up time. ''Note: When in use, all batteries discharge at the same rate. The more batteries you have, the slower the discharge is.''

==="Standard" Generator 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, this script 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 22% (just enough to supply 2 box thrusters) if the charge level of the batteries is between 5000 (start-charging level) and 9999 (stop-charging level). 0.001% is enough fuel rate to let the generator "sleep" when the ship is not moving.

:Generator=22*(:Battery_1>5000)*(:Battery_1<9999)+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 2 displays for '''"Material"''' and '''"Volume"''', 2 buttons to toggle '''"Active"''' and '''"Scan"''' and a third one 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]]==

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

Common YOLOL

2022-02-15T18:21:42Z

Danthbyrth: /* Fuel Chamber */ Making all scripts compatible with laborer module, adding a comparison table at the beginning for fields. Overall reformulation.

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

''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 variable 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.''
: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

==[[Fuel chamber|Fuel Chamber]]==

The following scripts are made to be used with the ship "[[Laborer module|Laborer Module]]" rewarded during the tutorials. To make it compatible with other prebuilt or own-made ships, refer to the table below for the corresponding modifications in the [[Device fields|device fields]].

{| class="wikitable"
! Ship Part !! Default Field Name !! Laborer Module Field Name
|-
| Fuel Chamber || FuelChamberUnitRateLimit || Generator
|-
| First Battery || StoredBatteryPower || Battery_1
|-
| Second Battery || StoredBatteryPower || Battery_2
|}

Also, ships will require enough batteries to act as buffers during the generator spool up time. ''Note: When in use, all batteries discharge at the same rate. The more batteries you have, the slower the discharge is.''

==="Standard" Generator 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, this script 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 22% (just enough to supply 2 box thrusters) if the charge level of the batteries is between 5000 (start-charging level) and 9999 (stop-charging level). 0.001% is enough fuel rate to let the generator "sleep" when the ship is not moving.

:Generator=22*(:Battery_1>5000)*(:Battery_1<9999)+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 2 displays for '''"Material"''' and '''"Volume"''', 2 buttons to toggle '''"Active"''' and '''"Scan"''' and a third one 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]]==

===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 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 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 Switching===
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 On 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]]