Hard drives satisfactory3/23/2023 ![]() ![]() You will be logged in on the first virtual console as the root user, and presented with a Zsh shell prompt.See README.bootparams for a list of boot parameters. Tip: The installation image uses GRUB for UEFI and syslinux for BIOS booting. $ pacman-key -v archlinux- version-x86_64.iso.sig $ gpg -keyserver-options auto-key-retrieve -verify archlinux- version-x86_64.iso.sigĪlternatively, from an existing Arch Linux installation run: On a system with GnuPG installed, do this by downloading the ISO PGP signature ( under Checksums in the page Download) to the ISO directory, and verifying it with: It is recommended to verify the image signature before use, especially when downloading from an HTTP mirror, where downloads are generally prone to be intercepted to serve malicious images. Visit the Download page and, depending on how you want to boot, acquire the ISO file or a netboot image, and the respective GnuPG signature. Pre-installation Acquire an installation image As the installation process needs to retrieve packages from a remote repository, this guide assumes a working internet connection is available. A basic installation should take less than 2 GiB of disk space. ![]() For interactive help, the IRC channel and the forums are also available.Īrch Linux should run on any x86_64-compatible machine with a minimum of 512 MiB RAM, though more memory is needed to boot the live system for installation. ![]() In particular, code examples may contain placeholders (formatted in italics) that must be replaced manually.įor more detailed instructions, see the respective ArchWiki articles or the various programs' man pages, both linked from this guide. For conventions used in this document, see Help:Reading. For alternative means of installation, see Category:Installation process.īefore installing, it would be advised to view the FAQ. The installation medium provides accessibility features which are described on the page Install Arch Linux with accessibility options. If you need any more assistance then please do not hesitate to contact the LOW.This document is a guide for installing Arch Linux using the live system booted from an installation medium made from an official installation image. Now your server should be using mods after the next server restart/start up! FactoryGame/Mods (if the Mods folder does not exist you can create this) You will simply need to upload (excluding the folder in Mods called SML) these to the same folder on your server e.g. Now this is where you will need to upload the files to your server. Once you have found the Satisfactory folder on your client, you will need to go into FactoryGame > Mods Once you have chosen the mods you will now need to locate them on your hard-drive, if you're using Steam you will be about to Right Click > Manage > Browse local files Note: Even if the mod is stated to be compatible with the multiplayer, this is not a guarantee of it!Ī good way of finding mods is by using the Satisfactory Mod Manager you can download here: ĭownload the Satisfactory-Mod-Manager-Setup.exe if you're on Windows WARNING Not all mods are compatible with the multiplayer! If the mod is compatible with the multiplayer, this is usually always mentioned in the description of the mod. In the first step, the mods are compiled and installed on the client so that they can then be transferred to the server. The same mods must be installed 1:1 on the client (by all players!) and on the server so that the connection is possible and no crashes occur. We would recommend using FileZilla or any other appropriate FTP Client. Installing mods will currently require you have FTP so that you can upload them to your server. WARNING NOTICE: MODDING IS NOT CURRENTLY SUPPORTED FOR SATISFACTORY UNTIL SML WORKS FOR DEDICATED SERVERS. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |