Jump to content

Search the Community

Showing results for tags 'guide'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • The Dry Dock
  • Navigator's Tools
  • The Tavern
  • Poseidon's General
  • Seismic Gaming's Topics
  • |☩|KNIGHTS TEMPLAR|☩| EU's Recruitment Section
  • |☩|KNIGHTS TEMPLAR|☩| EU's Ranks
  • Knights of the Morning Wood's Topics
  • Black Sails's Información
  • GypSeas's Recruitment
  • Poseidon's Chosen's Topics
  • Devils Brigade's Topics
  • The Saviors's Sanctuary
  • Trinity Trading Company | 18+ |'s Topics
  • The Flying Dutchman's Topics
  • East India Company's Welcome to The East India Company
  • Black Flag's Topics
  • The Ferrous Legion Mariners's Applications
  • Discovery's Topics
  • VORT3X gaming's Recruiting Members
  • The Captain's Plunder's General Chat
  • QUEBEC GOLD TEAM's Starting Zone
  • Lapu-Lapu's Company
  • ATLAS Sverige's Topics
  • ATLAS Sverige's ATLAS Sverige
  • The Castaways's Topics
  • Missits's Talk
  • [RU]Чистое Небо's Вся важная информация | Info
  • Verlorene Seelen's Logbuch
  • The Saviours's Topics
  • Los Corsarios del Leviatan's Temas
  • Debauchery Tea Party's Topics
  • Socaire Latino's Foro
  • Fallen Angels's Foro
  • Abusement Park's Topics
  • Noldorin Trading Company's Captain's Cabin
  • Noldorin Trading Company's Officer's Quarters
  • Noldorin Trading Company's Crow's Nest
  • Noldorin Trading Company's Crew's Quarters
  • Noldorin Trading Company's The Brig
  • PLAGUE COMPANY's Recruitment
  • Murder Mittens LLC's ARR BE GENERAL CHAT!
  • Black Market's baZZar
  • South Africa Main PvP Group's Welcome
  • The Harbormen's Recruitment Info
  • The Harbormen's Early Access Goals
  • Cuervos de la Tormenta's Asuntos
  • The Brethren's Court's Topics
  • The Radiant Sun Mercenary Co.'s Letter of Brotherhood
  • TÜV {EU/DE Community}'s Forum
  • The High Council's Discord links
  • Junk Army's Topics
  • [GER] Noskillz-Legacy's Beiträge
  • Sky Captains's Goals!
  • East Atlas Trading Company's Joining the East Atlas Trading Company
  • Savage Vikings's Topics
  • The Red Hair Pirates [NA] [PvP]'s Recruitment
  • The Red Hair Pirates [NA] [PvP]'s General discussion
  • Straw Hat Pirates's Dungeons
  • Cerberus's Recruitment
  • The Devil Dogs's Topics
  • Azeroth's Test Topic
  • Atlas Free Trade Company's company discussions
  • Free Men of Tortuga [cz/sk]'s News from Tortuga [cz/sk]
  • Super Tofu Fighting Umbrellas's Topics
  • Looking for Company's Recruitment
  • Holland - Nederland's Elkaar joinen
  • KoS's Topics
  • Duke Trading Company's Recruitment
  • Coalition Of Pirates's Voice Of Coalition
  • The Jolly Rodgers's We Be sailing for land to conquer !
  • Les Pygmées's Fresh Start
  • Unicorn company's Recrutement
  • The Fourth Skin's Recruitment
  • Marins D'Eau Douce's recrutement
  • d's BTJ
  • The Sea Dogs's Alliances
  • srGT's Topics
  • srGT's Wir suchen weitere Mitstreiter!
  • ODICHALIE's Topics
  • Shadowgarde's Topics
  • El ArKanToS's Tenemos una pequeña isla
  • Obsidian Fleet's Discord Name
  • Obsidian Fleet's Topics
  • Ghosts of Utopia's Now Hiring Recruits
  • Red's Great Company's Discord
  • Limitless's General
  • Sons of the Seven's Recruitment
  • Shinra's Recruitment
  • CORE's Topics
  • Darksea Dawgs's Darksea Holdings and Trade Co. now hiring!
  • The Red Panda Trading Company's Captains and Crew
  • The Red Panda Trading Company's Red Pandas are Recruiting!
  • Rectal Touch's recrutement
  • Salty Seagulls's Recruitment
  • Salty Seagulls's General
  • Kingdom of Naples's Topics
  • Ostindiska Kompaniet's Topics
  • (NA-PVP) They Flying Dutchmen's Recruitment
  • (NA-PVP) They Flying Dutchmen's Trade
  • The Community's Add me on Discord to Contact Us
  • The Habs's Topics
  • REVENANT BASTION's Rekrutacja otwarta szukamy ludzi
  • Expendables's Anvil
  • The Empire's Recruitment is going on right now
  • The Empire's Growing in Numbers
  • La Guilde's la guilde recrute
  • SouL SanD's Topics
  • Lords Of Blackwater's Join Us
  • ADHD gaming's Join us
  • The Crimson Watch [NA]'s Joining up
  • Maitres Des Océans's Discord
  • PvP Ravangers!'s Now recruiting
  • Friends's Info am Rande
  • The Alliance's Topics
  • Neptune's Carnival's Recruiting
  • Black Rebels's Topics
  • Black Rebels's Topics
  • Bad Company's How to Join Us!
  • Bad Company's Pictures and Stuff
  • Black Raven Shipping CO.'s Recruiting new members
  • EU PVP- Wolfpack's Discord
  • EU PVP- Wolfpack's ranks
  • Black Beard's ANIMAL TRADING
  • Blackstorm Raiders's Recruitment
  • [EU PVP] Polska Banda " Laughing Coffin "'s Topics
  • 4L Gang's Recruiting
  • La GreenLion Compagnie's Recrutement
  • The Dutch Kraken [PVE]'s The Dutch Kraken recruits
  • Die Germanen's Rekrutierung neuer Mitglieder
  • Winter Irondrake Company's Topics
  • zzzz delete mee's Questions
  • [NA-PVP] Friendlies - Recruiting's Recruitment
  • PuhlegGamingCompany's Anmeldung
  • [EU] Queen Anne's Empire's Rekrytering
  • Raiders (Dwarves of Ironforge)'s Topics
  • Saviors's Recruiting
  • White Ghost's Company information
  • White Ghost's Recruitment
  • Rum & Ehre's Topics
  • "RED STAR"'s Topics
  • United We Stand's Topics
  • Endless Storm's Topics
  • Dead Man's Soul's Set Sail.
  • Dead Man's Soul's Join Us
  • Dead Man's Soul's Company Market
  • The Lone Seaman US PVP's Members
  • playatlas.de - inoffizielle deutschsprachige Community's Forum / Discord
  • Dwarves of Ironforge's Topics
  • Complexity's Topics
  • Purgatore's Reclutamiento ABIERTO
  • Talos's Topics
  • Highwind's Topics
  • New Providence , NA PVE's Screenshots
  • Neue Mitspieler Gesucht EU PVP's Neue Mitspieler Gesucht EU PVP
  • Sail (f)or Fail! [GER]'s Topics
  • Pirate Hunter's Recruiting sailors
  • Ardus Industries's Recruiting!
  • ...'s Topics
  • ...'s Topics
  • Knights Of The Coconut's CUSTOMER SERVICE
  • Tradingport Gravelton's Wir rekrutieren
  • Shipshape & Bristol Fashion's Ahoy There!
  • Sunder Military Gaming's Recruiting Ad
  • E.B.L.A.N inc's Topics
  • E.B.L.A.N inc's Topics
  • Scales & Sails's Recruitment Statement
  • Scales & Sails's Chit-Chat
  • Lazy explorers's набор
  • Isla tortuga's Topics
  • Candy and Things's Topics
  • Einherjer's Na pvp Recruitment
  • Our Grid Atlas's Our Grid Getting Ship Shape
  • The Dark Brotherhood's Come join the fun!
  • Vieja Guardia's Reclutamiento
  • StS Gaming's StS Gaming sucht noch neue, freundliche Mitstreiter
  • V.O.C's Topics
  • To delete's News
  • To delete's Ressources
  • To delete's Tutorials
  • To delete's Help
  • To delete's General
  • ODIOSOS's Topics
  • [EU] Looking for Co-Founders's Looking for Co-Founder for new Company after Wipe
  • Deadlysins's Topics
  • experienced players looking for you! EU PVP's Topics
  • North Wind's Recruitment EU-PVE
  • Fractured Fury's We are now recruiting!
  • Odder Clan's Finding your Sea Legs
  • The Call's Forum
  • Grundlers's Now Recruiting US - NA PVP COLONIES!
  • Fake News Recruitment - NA PVP's Recruitment Information
  • See & Raub GmbH's Krakenkampf
  • Hurricane Force's Topics
  • Whitebeard's Pirates's Topics
  • Noxx Aeterna's Gold und Rum
  • Dam Beavers's Anamals for sale
  • The Frozen Fist | NA PVP's Discord
  • Les Gaulois du Sud-Ouest's Recrutement
  • Old Legs's Looking for friendly neighbours and people to play with :D
  • Los Ultimos de Filipinas's Reclutamiento - Recruitment
  • Sunken Reapers (Xbox NA PvP)'s Wanna Join?
  • 1st ATLAS Navy's Topics
  • Figaro Buckaneer Company's Recruitment
  • Figaro Buckaneer Company's Alliances
  • The Blackfish Trading Co.'s Topics
  • The Slipp'ry Sloopes's Pirate Info
  • The Slipp'ry Sloopes's General Company Talk
  • Pirates With Attitude's Recruitment NA PvP
  • TBA's Recruitment
  • TBA's General
  • Strength in numbers's Questing
  • Holland's xbox community build company or one with a xbox community
  • The Winchesters's The Winchester Island
  • Spartan Syndicate's Join the spartans!
  • The Alibaba's New Islands Purchased
  • SeaWolves's About us
  • Kornwhole Plantation's General
  • Kornwhole Plantation's Crew Recruitment
  • [PL] Peaky Fookin Blinders's Screenshots
  • Dragonborn's General Chat
  • Dragonborn's Join Dragonborn!
  • Ruthless Dar Company's Recruiting
  • Asgards Erben's Wer sind wir? Was machen wir?
  • KNOTNOX Suomi/Finland company's Otahan yhteyttä
  • Saltfang Hyenas's Topics
  • The Merchant Navy's General Discussion
  • One Plank Short - PVE Official - D10's Discord
  • Alisization's Прихожка
  • Alisization's Чат
  • Alisization's Ютуб Канал
  • Rungholdt's Schiffswerft
  • KRAKEN's revenge vi's WAR
  • KRAKEN's revenge vi's Discord
  • Genghis Kahn Empire's Recruitment
  • Templars's Recruitment

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

Found 22 results

  1. Updated 12/30/18 Okay, so I have done my setup from scratch and I'm going to provide a step by step walk-through. I believe this is a good starting point for any new server owner looking to get up and running for the first time, or someone looking to play "Singleplayer" (Note: From my testing, the server needs to interact with Steam bi-directionally even for LAN/SP- some ISP's such as cellular hot-spots or NAT conditions may not work!). While this guide can be applied to all server types, the examples are geared towards a 1x1 grid. This can also be used as a debug process for advanced server owners to test things: _________________________________________________________________________________________________________________________________________________________ Downloads: BAT Files & 1x1 Map Grid Template: https://drive.google.com/open?id=1MQ-8-WTta10p-TbAmnJ3DbfmNsDjaLsD (AtlasSrvBats.zip) ServerGridEditor: https://github.com/GrapeshotGames/ServerGridEditor (Hit "Clone or Download" then "Download Zip") steamcmd: http://media.steampowered.com/installer/steamcmd.zip NOTE: Make sure you update ServerGridEditor when changes are made to the git! Or even better- setup GIT and have it pull updates for you! _________________________________________________________________________________________________________________________________________________________ Server Setup: 0) Create a directory where you will put the server files (Eg. X:\AtlasSrv) 0a) Open "AtlasSrv" and create "steamcmd" and "AtlasTools" 0b) Extract steamcmd.zip into "steamcmd" and run "steamcmd.exe" 1 time to set it up. When the prompt shows "Steam>" with an OK message above you can close this window. "steamcmd" folder should look like this now: 0c) Go back to "AtlasSrv". Open "AtlasSrvBats.zip". Extract the "LAUNCH_ATLAS_00.bat" and "ATLAS STEAMCMD.BAT" to this folder. 0d) Right-Click "ATLAS STEAMCMD.bat" and click Edit. Replace the contents of this file with (Change "X:\AtlasSrv" in both entries with the directory you are using): start /wait /high X:\AtlasSrv\steamcmd\steamcmd.exe ^ +login anonymous ^ +force_install_dir X:\AtlasSrv\ ^ +app_update 1006030 validate ^ +quit 0e) Save & Close. Run "ATLAS STEAMCMD.bat. You may be prompted with firewall permissions, you must "Allow Access". (This process will take some time) 1) Your Atlas server directory should look like this upon completion: Congrats! Your server files are now downloaded and on the latest version. You can use ATLAS STEAMCMD.bat at any time to validate and upgrade the server. Now onto the map! _________________________________________________________________________________________________________________________________________________________ Map: 1) Extract "ServerGrid1x1" folder from "AtlasSrvBats.zip" to the "AtlasTools" folder 2) Extract the ServerGridEditor zip to the "AtlasTools" folder. Open "ServerGridEditor.exe" within the "SeverGridEditor-master" folder 2a) Open the "Island Editor" (ServerGridEditor.exe), "Open project" and navigate to the ServerGrid.json file we extracted into "AtlasTools" 2b) Click "Project > Create" in the top left. Copy the "Atlas ID" and CANCEL. 3) Click "Project > Edit": 4) Paste the "Atlas ID" you have on your clipboard into the "Atlas ID" of this window. 5) Change "Friendly Name" to your Server Name. Change "Atlas Password" if you want a password on the server (This will be needed to keep people out for singleplayer!) 6) Click "Edit" at the bottom. 7) Ctrl+Left Click on the map: 7a) Set "Name" to what you want for name of your Freeport (Grid) 7b) Set "IP" to your Server external IP (whatismyip.com). Server internal IP (192.168.x.x) can be used, but this will disable public access! 7c) Hit "Save" at the bottom (You can make more changes later but in first-time situation, it's nominally best to use default settings). 7d) Back in Island Editor (ServerGridEditor), Click Export > Local Export ALL. Click ok to the default location. Popup should say "Success". 7e) Click Project > Save. Navigate to the "AtlasTools" folder, create a new folder "Live project", use the file name "ServerGrid" and "Save". (This way you can edit more later and keep the template untouched!) 7f) Close Island Editor. Open "AtlasTools/ServerGridEditor-master/Export/" folder. Cut/Copy the "ServerGrid" folder and 2 JSON files: 7g) Navigate to "AtlasSrv/ShooterGame" and paste: 7h) So close! Navigate back to "AtlasSrv" and Right-Click "LAUNCH_ATLAS_00.bat" and Edit. Replace the contents with (Replacing "X:\AtlasSrv" with your directory, and "SeamlessIP" with External IP) start /high X:\AtlasSrv\ShooterGame\Binaries\Win64\ShooterGameServer.exe Ocean?ServerX=0?ServerY=0?AltSaveDirectoryName=00?ServerAdminPassword=123?MaxPlayers=30?ReservedPlayerSlots=25?QueryPort=57561?Port=5761?SeamlessIP= -log -server -NoBattlEye exit @Firedragon's Command line if the above does not work for you: 7i) Save & Close. Navigate to "AtlasTools/redis-server". Run "redis-server_start.bat". Wait for the command line to say ready to accept connections. 7j) Configure port forwarding with these ports on your router. Change the IP to match the one you put on the Map file: 7k) The moment you've been waiting for; Navigate back to "AtlasSrv" and Run "LAUNCH_ATLAS_00.bat". When the command prompt displays how many cores it is running on, your server is up! OPTIONALS redis-server: redis-server.conf has options to change your database password and how much RAM (maxmemory in the conf) the database will use in bytes. I personally set the maxmemory to 1GB (1073741824) for my 1x1 testbed. I don't play often locally so I dont know the impact other than a possible crash if the DB runs out of memory (redis does require a pagefile, so I think it will start writing to the disk if it runs out of memory? not 100%) . The DB file is saved on the disk in the same folder so you can track it's size over time and adjust accordingly. I'm not sure on the specifics, but I would say it's safe to keep the max memory 2.5x higher than the database size AT MINIMUM (to account things like the database copying itself and swap space). For sake of argument me playing by myself without doing much the database was about 90MB, so 1GB RAM allocation should be plenty of breathing room for the forseen future. If you change your password in the redis-conf (for added security), you must also update your passwords in the map file under Project > Edit (You can see the old password "foobared" in one of the images above. These should reflect your conf file). AtlasSrvBats.zip also comes with an undocumented, but included "LAUNCH ATLAS ALL.bat". This file can be placed in "X:AtlasSrv" (Your server's root directory with the other bats) and be used to start redis-server and server/s in one shot. It is currently setup to launch redis-server and the first grid server. Additional grids can be launched by un-commenting (removing the #) from the corresponding lines, and making a copy of "LAUNCH_ATLAS_00.bat" for each additional grid (LAUNCH_ATLAS_01.bat, etc), and editing their launch strings accordingly (Correct X/Y, ports, etc). TROUBLESHOOTING Still can't connect to server after following guide? There are many different networking situations based on individual setup and ISP that no 1 guide can account for all. Most issues connecting beyond following this guide come from user error, improper hardware configuration (PC/Router/Modem), or Local/ISP NAT restrictions (Some net providers and most cellular hot-spot providers, see CGN https://en.wikipedia.org/wiki/Carrier-grade_NAT). Some users have reported finding "NAT Acceleration" or similar options in their routers and disabling them has allowed them to connect. Double-check port settings on router and for Windows Firewall IN & OUT. Sometimes 1 digit missing or out of place is the simplest error. Make sure your launch bat parameters and map file details match your port settings in your router & firewall. Check within router (and modem, if accessible) for options to allow "Open" NAT (Sometimes set to secure by default) Make sure there is no "NAT Acceleration" taking place If you router has no buried NAT features, you can attempt this workaround: A NAT Loopback workaround method for some newer routers and ISP modem/router combos that do not support NAT Loopback: https://forum.sector3studios.com/index.php?threads/workaround-if-you-cannot-join-your-own-dedi-server.4672/ You -CANNOT- ever connect directly to the internal IP of the server. You must connect from your External IP (forming a hairpin): If your client PC IP is and your server PC IP is You share a WAN/Internet IP (whatismyip.com) that you use to connect as if you were an external client: -> WAN IP -> steam://connect/WAN IP:Port (Replace WAN IP and Port with corresponding numbers) -> direct connect will never resolve (UNABLE TO QUERY INVITE) with current method used by Grapeshot to force steam usage. If all else fails, like some cellular mobile hotspots, your ISP may be using a CGN (Carrier-Grade NAT). You can read more on CGN here: https://en.wikipedia.org/wiki/Carrier-grade_NAT If you have a CGN'd IP from your ISP, you will not be able to host a server until things can be run completely local, or your ISP can move you to an IP pool that is not governed by their CGN implementation. As a very last resort, if your dedicated server is online and visible to others, but you cannot connect to your own local server, and the NAT Loopback fix does not work- Consider using a VPN like Windscribe (free 10/20GB month with tweet/voucher promo). http://windscribe.com - You want to use the VPN on the PC you are playing on, NOT the server. Doing this will give you a virtual hairpin where you can connect to your own external IP. If you are playing on the same computer as the server, you will need to use a VPN program that is application specific (Proxifier), and point it towards AtlasGame.exe. This way, the VPN becomes your hairpin back to your external/WAN IP only for ATLAS, while the server continues to do it's thing unaffected by the VPN. UPDATES 12/30/18 - Updated download links, cleaned up guide to reflect changes Good luck , Sailors! -Teach
  2. Kein DOWNLOAD notwendig, no DOWNLOADS required !!! GERMAN: Für alle die eine bessere Font haben wollen, sollten folgendes machen: Erstellt den Ordner "global" in "Steam\steamapps\common\ATLAS\ShooterGame\Content\Localization\Game\" Wechselt in den Spielpfad Für größeren Menü/System Font: "Steam\steamapps\common\ATLAS\ShooterGame\Content\Localization\Game\ka" Für kleinere Menü/System Font: "Steam\steamapps\common\ATLAS\ShooterGame\Content\Localization\Game\ko" Kopiert alles AUSSER "ShooterGame.archive" und "ShooterGame.locres" nach "Steam\steamapps\common\ATLAS\ShooterGame\Content\Localization\Game\global" Öffnet Steam und drückt mit der rechten Maustaste auf "ATLAS" in der Bibliothek und öffnet die Eigenschaften Legt als Startoption "-culture=global" (ohne die " ) fest Bestätigt dies mit OK und schließt das Fenster Font tauschen für die Texte (chat etc.) im Spiel: Sollte euch die beigelegte Font aus dem ka / ko Ordner nicht gefallen, kann man die mit einer beliebigen .ttf tauschen. Zum Beispiel mit einer Font die im Windows mitgeliefert wird (Windows\Fonts). Wechselt in den Pfad wo eure Fonts liegen im .ttf Format Wählt eine Font aus die Ihr im Spiel verwenden wollt (z.B. calibri.ttf) Kopiert die Datei nach "Steam\steamapps\common\ATLAS\ShooterGame\Content\Localization\Game\global" Folgende Dateien müssen mit dieser ersetzt werden: DefaultFont.ttf / DroidSansFallback.ttf / DroidSansMono.ttf / LastResort.ttf / NanumGothic.ttf / Roboto-Bold.ttf / Roboto-Light.ttf / Roboto-Regular.ttf Als Beispiel: "copy <deine ausgewählte Font für das Spiel>.ttf DefaultFont.ttf" und ersetze so alle Dateien! Startet das Spiel und prüft ob euch diese Font für die Texte gefallen, ansonsten wählt eine andere (Für das Spiel Menü / System wird eine .uasset benötigt) Wenn Ihr jetzt das Spiel startet, habt ihr normale Fonts die nicht verschnörkelt sind. PS: Sprachübersetzungen sind in "ShooterGame.archive" und "ShooterGame.locres" bereits halb fertig in diversen Sprachen vorhanden. ENGLISH: For everyone who wants better fonts: Create folder "global" in "Steam\steamapps\common\ATLAS\ShooterGame\Content\Localization\Game\" Change to the path For bigger menu / system Font "Steam\steamapps\common\ATLAS\ShooterGame\Content\Localization\Game\ka" For smaller menu / system Font "Steam\steamapps\common\ATLAS\ShooterGame\Content\Localization\Game\ko" Copy everything EXCEPT "ShooterGame.archive" and "ShooterGame.locres" to "Steam\steamapps\common\ATLAS\ShooterGame\Content\Localization\Game\global" Open up steam and click with the right mousebutton on "ATLAS" in your library and choose propertys Set as starting option "-culture=global" (without " ) Click on OK and close the window Replace font for ingame Text (chat etc.): If you dislike the font from ka / ko Folder, you can replace it with your desired .ttf. For ex. replace it with a font that comes with Windows (Windows\Fonts). Change to the path where you store your fonts in .ttf format Take a font you like and wish to use inside the game (ex. calibri.ttf) Copy the file to "Steam\steamapps\common\ATLAS\ShooterGame\Content\Localization\Game\global" You need to replace all of the following files with it: DefaultFont.ttf / DroidSansFallback.ttf / DroidSansMono.ttf / LastResort.ttf / NanumGothic.ttf / Roboto-Bold.ttf / Roboto-Light.ttf / Roboto-Regular.ttf For example: "copy <your desired font for the game>.ttf DefaultFont.ttf" and repeat this with the others. Start the game and check if you like the font, otherways replace it with another like explained above (For the games Menu / System font style is a .uasset needed) When you start the game now, you have READABLE fonts. PS: Translations are done in "ShooterGame.archive" und "ShooterGame.locres" and half ready for many languages. ROT = Font aus den .uasset Dateien || ORANGE = Font aus der .ttf Datei RED = Font from .uasset files || ORANGE = Font from .ttf file
  3. EDIT: Floatsam / Flotsam. Floatsam is the archaic variant of Flotsam according to Merriam-Webster. Be careful with the ini and settings below, because both Flotsam and Floatsam are used in different places within Atlas, and using float instead of flot (or vice versa) in the wrong place will cause errors I searched a good bit but was never able to find a solid answer. So I played around with the ini config we use in Ark. Searched through many uasset files in the primalearth content folder. And was finally able to figure it out after a lot of test and fail. It's pretty much the exact same as Ark, but I had to figure out the exact itemstring for flotsam. I'll break down the code and explain each part for those who never did this on Ark. At the end I'll post the complete code I use for my play server First: You have to tell it which loot table you're overriding. This will completely override it, so anything that normally spawns in that piece will no longer. SupplyCrateClassString is the item that you're overriding the loot table for. It can be anything from animal loot drop, boss drop, flotsam, sunken treasure, etc etc. Anything that can drop loot. For this, we're using PrimalInventoryBP_SupplyCrate_Floatsam_C, the loot inventory for flotsam. Later, we're going to add in itemsets. Sets are like categories. If you want to keep it simple and easy, you can put only 1 itemset and include everything in that set. Then the loot table will randomly choose X amount of items from that set. That could be a problem if you wanted, let's say, to always have an amount of gold in the loot, but also have a chance to give a piece of armor, weapon or tool. In that case, you would end up making 2 itemsets to be included in this single suuplycrateclassstring. But we'll go over adding item sets later. For now, let's continue to look through this one line. MinItemSets and MaxItemSets are exactly what they sound like. When we list out itemsets later, this is the part that determines how many different sets will be included in the loot. This one currently shows a MinItemSet of 2 and a MaxItemSet of 2. That's because in this example, I only have 2 itemsets that will be shown later. And I want to make sure each set will always be in the loot. Why I want that will be explained later when we talk about adding itemsets. NumItemSetsPower is the power of the items. It's ideal to leave this as 1, because it can be multiplied using a different ini config setting: SupplyCrateLootQualityMultiplier bSetsRandomWithoutReplacement=true means that each set can only appear once per loot. As we know, we'll be adding 2 itemsets later. And because our MinItemSet and MaxItemSet are 2, if this was false, there's a chance the 1st set would appear twice, meaning the 2nd set wouldn't be in that loot drop. We don't want that. So setting this to true, each set can only appear once in that loot, ItemSets= is where we list our item sets. For this example, the 1st itemset is a single item. Gold. And the 2nd itemset is full of each type of armor, weapon and tool. The reason for this is that you saw above, each itemset will be in the loot. And since the 1st is only gold and nothing else, it can't randomly select anything from that list except for gold, and so gold will always be in the loot. And the 2nd itemset being armor, weapons and tools. It will randomly pick X amount of items from that list (Which we'll go over how to set that amount later). And include those in the loot in addition to the gold. Now for the ItemSets= You'll notice some similarities to the part above. MinNumItems and MaxNumItems are for this single itemset. This is the 1st one, which will only have gold in it. So there only needs to be 1 for both min and max. NumItemsPower is the same as above, ideal to leave it at one. But if you want to really customize this particular set instead of all loot across the board, raising this would increase the quality of all items in this list. SetWeight in this example is pretty useless because both sets will always be included in the loot. But lets say you end up having 5 different sets of items, and you want the loot to only include 2 random sets. The weight is the chance this set would be included. The higher the value, the more likely it is to be included in the loot. You could also keep it simple and use percentage. 1.0 would be 100% chance this is included of the other sets. Or 0.5 would be there's a 50% chance it'll be selected over the other sets. The value in this example doesn't matter since both sets will be included regardless. bItemsRandomWithoutReplacement=true is the same as above. It means that if we had a bunch of items listed in this set. But only allowed the loot to pick 3 of them. It will make sure the same item couldn't be picked more than once. Or setting it to false means there's a chance the same item can be randomly picked multiple times. ItemEntries= is where we'll list our items to be picked. Ok, this is where EntryWeight will become important. This 1st set only has gold, so it doesn't matter here. But the next set has a bunch of items listed. And EntryWeight will allow us to give certain items a higher chance of being included. ItemClassStrings= is the item we want to include. For this line, we're including gold, PrimalItemResource_GoldCoin_C. I'm not entirely sure the different in entryweight and itemweight, since every item listed will have both. So in lists that have multiple items, I keep the entryweight and itemweight the same. Perhaps someone more knowledgeable on that could explain the difference. MinQuantity and MaxQuantity are what they sound like. How much you want it to randomly include. For gold, I have it set to randomly have between 10 and 50 per flotsam. But you can set that to your liking. If you were listing an item such as armor or a tool. You would want both those to be 1. You don't want to open a loot and see 50 hatchets lol MinQuality and MaxQuality are also how they sound. The quality of the item. Gold doesn't have a quality, so it's set to 0. But the higher you increase it, the higher quality the item will be (Fine, Mastercraft, Legendary, Mythical, etc). bForceBlueprint=false is whether or not you want this to always be a blueprint. Gold has no blueprint, so false here. But let's say you want loot that only gives blueprints, this would be set to true for each item listed. Even though it's false, you can still have it randomly choose to make it a blueprint or the actual item with the next setting. ChanceToBeBlueprintOverride=0 If bForceBlueprint is set to false, you can change this value to a percentage. If we change it to 0.5, then there's a 50% chance the item will be a blueprint in the flotsam and 50% chance it'll be the already crafted version of that item. And that includes that itemset. The ))), at the end is how you know that set is done and the next set is about to be listed. Here is the next set: And you were suddenly critically hit by walloftext. But don't be intimidated. It's actually pretty simple. There's alot in that section because it has all the loot that COULD be in the flotsam. This is just multiple copies of the same line. So this is the 2nd set. You can look over it line by line and see everything that was explained in the 1st set. In this one, you'll notice that we have MinNumItems=1,MaxNumItems=3. Which means that of everything listed here, there's a chance that 1-3 of them will be included in the flotsam. All the entryweight/itemweights are the same, so every item has an equal chance of being picked for those 1 to 3 items. All of the quotes above are for reference and explanation. You don't want to try and copy and paste to piece it all together. Because a single space, comma or parenthesis out of place will cause errors on server boot. So here is the entire line to add to your config.ini The entire code to copy/paste into your game.ini file. You must include it in the game.ini for every region of your server if you're running a grid ConfigOverrideSupplyCrateItems=(SupplyCrateClassString="PrimalInventoryBP_SupplyCrate_Floatsam_C",MinItemSets=2,MaxItemSets=2,NumItemSetsPower=1,bSetsRandomWithoutReplacement=true,ItemSets=((MinNumItems=1,MaxNumItems=1,NumItemsPower=1,SetWeight=100,bItemsRandomWithoutReplacement=true,ItemEntries=((EntryWeight=100.0,ItemClassStrings=("PrimalItemResource_GoldCoin_C"),ItemsWeights=(1.0),MinQuantity=50,MaxQuantity=500,MinQuality=0,MaxQuality=0,bForceBlueprint=false,ChanceToBeBlueprintOverride=0))),(MinNumItems=1,MaxNumItems=3,NumItemsPower=1,SetWeight=100,bItemsRandomWithoutReplacement=false,ItemEntries=((EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_ClothBoots_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_ClothGloves_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_ClothHelmet_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_ClothPants_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_ClothShirt_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_FurBoots_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_FurShirt_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_FurGloves_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_FurHelmet_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_FurPants_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_HideBoots_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_HideGloves_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_HideHelmet_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_HidePants_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_HideShirt_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_HeavyShirt_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_HeavyPants_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_HeavyHelmet_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_HeavyGloves_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItemArmor_HeavyBoots_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItem_WeaponPistol_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItem_WeaponSniperRifle_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItem_WeaponBlunderbuss_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItem_WeaponCrossbow_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItem_WeaponMetalHatchet_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItem_WeaponBow_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItem_WeaponMetalPick_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItem_WeaponSickle_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4),(EntryWeight=1.0,ItemClassStrings=("PrimalItem_WeaponSword_C"),ItemsWeights=(1.0),MinQuantity=1,MaxQuantity=1,MinQuality=1,MaxQuality=4,bForceBlueprint=false,ChanceToBeBlueprintOverride=0.4))))) As I said at the start, this will completely override the loot. I currently don't have music included in the itemsets (Because I plan to add a 3rd item set for music later). But for now, if you do an exact copy/paste, you will no longer get music sheets from the flotsam loot
  4. First up, this is not a new idea to have a tutorial for: There's a great primer here by @Din Narcotic that's gotten a lot of attention. It's a wonderful intro to painting, and I'm going to assume that you've read that post before starting here. This post tries to explain the template creation process. Several other painting tutorials that I'm not going to list, because it goes on and on However, I think each guide on this topic is missing some crucial step, so some newer players are confused by the actual process of painting in-game, from start to finish. In this post, I'm going to attempt to give a complete tutorial on how to paint in-game. This covers the following topics: Basic understanding of files needed for painting Creating templates for different sails/signs/etc Using templates to create an interesting graphic Converting back to a game-readable format Required software: ATLASPntConverter (You can use the ARK PNT converter, but it's missing some features and ATLAS-specific colors) image editing software (I use the free program paint.net, because it has a layers feature which is VERY useful) Of course, ATLAS! Currently, you can only do this on PC - sorry Xbox players File formats/graphics intro Creating graphics to use in-game requires a little bit of file manipulation: the game uses .pnt files to store the graphics, which are unreadable by typical image editing software. You have to use the .pnt converter above (we'll explain thoroughly later) to convert the images to a .png format, which is readable and editable. The only other tricky part is knowing which pixels in the image go to which parts of the in-game item (for those that are interested, this is known as UV mapping). We'll need to make templates for each and every item you want to make a graphic for - that includes player tattoos, each animal you may want to paint, each size and type of sail (including cosmetic designs), signs, billboards, and canvases. Each will need their own template! After that, the only limit is your own creativity. Creating Templates Creating a rough outline Find something you want a template for - if you're lucky, you may be able to find a template online. If not, continue... Gather a paintbrush and a lot of dye. TIP: You can do this in singleplayer, so you can cheat in everything you need with cheat gfi colorbox 1 0 0. Left-click with a paintbrush on the animal/object you want to paint - I'm going to paint a billboard for this tutorial. Paint an outline around each part of the object/animal if possible. For animals, just painting a solid color works better than trying to find the "borders". Some tips: Shift+clicking makes it easier to make the border, since it draws a thicker line. The border doesn't have to be neat - we'll clean it up later. Some regions cannot be painted manually - these can only have a solid color using a paintbrush in-game. On a billboard, only the face of the billboard can have a graphic applied. You may want to draw a square somewhere on each part, as well - sometimes the game will stretch/squish graphics, and drawing a square will show you if that happens. Right-clicking and dragging will just move the object around, which can make it easier to get a good outline. Now click the "Save Paint" button at the top of the screen and name the painting something memorable - I'm naming mine "BillboardTemp" (Your name can only be up to 15 characters). Finding the file and converting to a .png The template is now saved on your computer, in the folder named <Steam_Folder>\SteamApps\common\ATLAS\ShooterGame\Saved\MyPaintings\. The <Steam_Folder> location depends on where you have steam installed on your computer and if you told steam to install it somewhere non-standard. Usually, it's in program files. Find this folder, and in it you should see a file with a name that resembles what you named your painting in-game but it will not match exactly. My billboard template is called BillboardTemp_Sign_Large_Wood_C_1.pnt. Don't change this filename, since everything in the name (other than the part you chose) tells the game what object/animal this painting is for. Open the ATLAS pnt converter, and click the "Open" button at the bottom right - navigate to and select the file in the previous step. You should now see 2 copies of your outline image/template at the top of the screen, like in the image on the right. Now just click save, and change "save as type" to .png. Click save, and now you have a template in an editable format! Cleaning up the template Open your template .png file in an image editing software of your choice. Images below will use paint.net, as I mentioned at the beginning. Check the square that you drew to see if the image has been stretched/squished at all. Animals will typically have lots of stretching, so your square may not even have straight edges. Other objects my scale it, so your square looks more like a rectangle. Keep this in mind while making your graphics. You can start making your graphics right now, but I like to do the following to clean up the template: Fill in each part instead of just having an outline. Add some basic text with the right stretching (based on the square) to remind you in the future how it gets stretched. Remove any extra/stray pixels - I had just 1 pixel to remove. I'm not sure how they get there, but they don't affect the painting so I remove them. Now just save it, and you can use the template to make an interesting graphic! Creating a graphic Using a template to create graphics (using layers) With the template open, save as a new file - paint.net has their own file format (.pdn) that you can use, or you can just save it as a .png. To keep things simple, keep the extra text at the end of the filename, and just change the part of the name that you chose when making the template. I'm naming mine "NyanCat_Sign_Large_Wood_C_1.png". Before making any changes, create a new layer by clicking the Layers menu at the top of the screen, and select "Add New Layer". If you have the layers panel open, you can see all of the layers on the right side of the screen - if you don't have it open, you can open it with F7. Select this new layer, and start adding in changes or pasting in images! Your changes will go on top of the template image, so you know what parts of the image you can use. I'm going to just paste in an image of the Nyan cat. Tips: If your image completely covers the template, you can double-click the "layer 2" on the layers panel, and change the opacity. This lets you see through your image to the template beneath. Just remember to set the opacity back to 255 when you're done. To clean up stray marks outside of the template: Select "layer 1" (the template layer). Then use the "magic wand" tool to select the transparent background outside of the template. Select "layer 2" again and press delete. To finish the painting, uncheck the box next to "layer 1" in the layers panel to make it go invisible. Set the opacity for "layer 2" back to 255 if you messed with that. Finally, save as a .png! It will have a warning about flattening the image - this is fine, it just gets rid of the template layer since it's invisible. Converting back to .pnt and loading into the game Everything up until this point should be in your "My painting folder", although you can do your image editing anywhere you like. Now we have to get the image back into the .pnt format, and loaded back into the game. Open the ATLAS pnt editor and open the image you just made. 2 copies of your image will appear at the top of the screen. The left copy is the actual image on your PC, and the right image is close to what it will look like in-game. SIDEBAR: ATLAS doesn't have every possible color of dye, so it will ALWAYS approximate the look of your image. You have several settings that you can choose between at this point, to change how it looks. These can be found at the bottom left of the screen: YUV/RGB: This changes how the image is interpreted. One option may be closer to the original than the other, so always check both options. Dithering: This causes the streaky, colored lines that try to mix colors together to approximate a color in-between the two options. In my case, the pink of the Nyan Cat isn't available in-game, so it tries to mix a darker pink with white. These are very apparent in gradients, but you may want to turn these off (set to 0) or enhance them (set to 1+) depending on your image. Color palette: By default, all atlas dyes can be used in the painting. If you want to limit these, you can select each color individually across the bottom of the window. But the best solution in most cases is just to press the "Reduce" button which reduces the number of dyes a few at a time without changing the image very much. NOTE: White dyes are transparent in-game. The top-right image above is the one I use for my final painting below, and you can see that the frosting has pink and brown (wood color) since the white is invisible. Once you have the settings the way you like in the pnt converter, click save, and change "save as type" to .pnt. Make sure you're saving in the "My Paintings" folder where you originally found the template file, and that the extra parts of the name are still there - if you miss either of these, you won't be able to see it in-game! Now just hit the object/animal with a paintbrush in game and click "Load paints from this type" at the top left. Select the name you saved the .pnt as, and it will preview on your screen, showing you what it will look like and what dyes you need. Go ahead and get those, and click "Load painting" at the top left. It'll start painting! Down below is my finished painting: If you found any part of this tutorial confusing, please let me know in the comments, and I'll clarify any of the steps Also, please share your templates in the comments - that's the most tedious part of painting, and I know people have some templates for others to use out there - if you have a good stash of templates in one place, let me know and I'll add a link to the top of the post!
  5. Hello everyone. I've gotten some questions about overriding creature spawns on islands, so we've added a guide to the devkit site (Though the devkit is not explicitly required) You can find it here: http://devkit.playatlas.com/en/latest/Guides/OverridingSpawns.html
  6. Introduction Looking around, I have found a need for a comprehensive guide on the most efficient use of speed sails, cargo racks, and long-distance resource hauling. Especially now that singleplayer mode allows for quick and easy testing, we need to get more factual information about ATLAS out to the public. For simplicity's sake, I will avoid discussing weight sails, handling sails, and item quality (maybe you can look forward to a guide on those subjects from me in the future). Outline: TL;DR results Answering individual questions Quick summary of results Explanation of singleplayer testing Summary As a TL;DR, here are the questions I will be answering today and a quick summary of the answer: How do ship speed, sails, and weight work behind-the-scenes? Every ship has a max speed, if it theoretically weighed 0 lbs. Each sail you add contributes to the max speed, linearly. The speed is related to the square root of the percentage of your ship weight that is not filled. The following table has a few notable percentages (the speed % is compared to the max speed). For each type of ship, what speed sail configuration (small/medium/large) gives the fastest ship? sloop: 1 medium and 1 small speed sail schooner: 1 large and one small speed sail brig: 3 large speed sails galleon: 6 large speed sails What ship is the fastest? Contrary to popular belief, with optimal sails, galleons are the fastest, followed closely by schooners, and then brigantines and finally sloops (rafts aren't real ships :P). How many cargo racks should I put on my ship to get the fastest ship? This is a very complex question that depends on your ship type, the total weight you want to carry, your max weight, and the "empty" weight of your ship. As a rule of thumb, add a cargo rack if you have another 4,000 lbs in resources to put in one, and make sure you fill existing cargo racks as much as possible before adding more. What is the optimal way to haul resources long distances in as little time as possible? Once again, this depends largely on the factors in the previous answer. As a rule of thumb, load up your ship to around 50% weight when you are hauling resources. Here are some related questions that I Won't be answering today, but I will include some links to people that have answered them in the past (to varying degrees of thoroughness and accuracy - be your own judge on the matter): How accurate is the in-game depiction of knots (speed)? Do higher-quality (fine/journeyman/etc.) sails actually give any benefit? For a more in-depth discussion on each of these questions, keep reading! I will lead you through the testing I have done in singleplayer mode, and we will discuss factors that I had to ignore while testing, etc. Onward to information! IMPORTANT NOTE BEFORE WE BEGIN: I am going to use the terms "maximum speed" and "speed" throughout this guide, and these each refer to a different concept. The maximum speed of a ship is the theoretical maximum speed it could go if it weighed 0 lbs. The speed of a ship is the actual speed of the ship, with whatever weight it currently has on it. Most of the math is done with the maximum speed, not the current speed. I will start by talking about how to use the speed and weight of a ship to compute the maximum speed. How do speed, sails, and weight calculations work behind-the-scenes? Ship speed depends on the type of ship you are sailing, the number and type of sails your ship is equipped with, the number of cargo racks on board, and the weight percentage. We will discuss all of these things here. I will lead you through the testing I did and try to explain some of the nuances that I had to think about First - The effect of weight on ships: My results: Ship speed is related to the weight of the ship according to the following equation: speed = speed_max * sqrt(1-weight/max_weight) NOTE: This does not take into account cargo racks - see the equation below for a more complete equation. This results in a graph like the following: The maximum speed depends on the ship you are in and the sails you use - we will discuss this more in a bit. Since the speed changes as the square root of the remaining weight, you can see that the weight drops off really quickly as you get closer to 100% full. Thus, any weight above around 80% starts to really slow the ship down, and for that reason, I suggest never sailing above 85% capacity, since you just travel too slow. My testing method: I spawned each ship in using ssf <sloop, schooner, brigantine, galleon> (pick one of the arguments in the <>). I set up the wind using the commands setwind 100 and setignorewind true (both are necessary for consistency). Then I opened the sails to full and marked down the current weight of the ship and the speed, once it stabilized. Using this method, the ship speed is very stable, unlike in the actual servers, where the speed bounces all over the place. Now, I used the admin command gfi gem_base 500 0 0 to get 500 gems, and I recorded the weight and speed - rinse and repeat until the ship stops moving. We now have a data for ship speed versus weight. Plotting the speed of the ship versus the square root part of the equation above, I got a straight line with the slope equal to the maximum velocity for that sail arrangement: NOTE: Keep in mind that this method will spawn a schooner with 2 medium speed sails and a galleon with 5 large speeds sails, both of which are not the optimal sail arrangement. The max speed I got from these tests just correspond to a sub-optimal layout of sails. The important part here is how straight these lines are, which proves that this equation is correct. This is a great fit, so I am pretty confident about the equation and the max speeds we get from this method. From now on, we can just manipulate the speed equation to solve for speed_max if we know the weight and speed of the ship. This will be useful in the next section. Second - The effect of sails on the speed of a ship: My results: Sails add linearly to the max speed of a ship. That means that half as many sails will push the ship half as fast. However, I found it surprising that each type of sail increases the max speed differently for each ship. The following table summarizes my results. If you can find any patterns in that data, please let me know - I couldn't find anything. The main thing to note with this table is the speed per sail point. Remember that small sails cost 1 sail point, mediums cost 1.7, and larges cost 2.66 (ATLAS rounds this to 2.7, but it actually is 2.66 when you add multiple). The sails get more speed per point the larger you get (looking at a single ship). This means that it is always beneficial to use as large of sails as possible, and fill in any remaining points with smaller sails. This leads to the following optimal configurations: Sloop: 1 medium speed sail (max speed is 16.03 knots) Schooner: 1 large and 1 small speed sail (max speed is 21.05 + 4.55 = 25.6 knots) Brigantine: 3 large speed sails (max speed is 23.79) Galleon: 6 large speed sails (max speed is 26.88) NOTE: I discuss the optimal sail configuration more in the next section. This means that galleons are the fastest ship, followed closely by schooners, and then by brigs and sloops are the slowest. This is important, since many people tend to believe that schooners are the fastest ship, but this data shows that they are actually over a full knot slower on average. My testing method: I spawned the ships as I did above. This time, I removed all sails and set up the configuration I wanted to look at (for example, 16 small speed sails on a galleon). I marked the weight and speed while slowly removing sails. Plotting the maximum speed (calculated as mentioned above) versus number of sails gave a line, and fitting a linear trendline in excel gave a slope that you see in the table above. If you want to compute the max speed of a ship, just add together the values for each sail from the table above. Third - How do cargo racks affect speed? My results: A full set of cargo racks (2 for a schooner, 4 for a brig, and 6 for a galleon) will reduce your maximum speed by 40%. This means that each cargo rack reduces your speed by the following amounts: Schooner: 20% per cargo rack Brigantine: 10% per cargo rack Galleon: 6.67% per cargo rack If you only have some of the cargo racks, it affects your speed linearly (for example, 2 racks on a galleon reduces your speed by 40% * 2/6 = 13.3%). However, the racks also reduce the weight of anything inside of them by 80%, up to 8,000 lbs pre-reduction. This means that a full cargo rack reduces your ship weight by a total of 6400 lbs (80% of 8,000). The weight reduction will make your ship go faster, but it must counteract the speed reduction just for having the rack on the ship to be beneficial. This is complicated enough that I gave it its own section toward the end of this post. In general, always drop empty racks, and fill up your existing racks before you add another. My testing method: In singleplayer, spawn in ships as mentioned above. Get the ship up to speed and start adding empty cargo racks. Make sure to take note of the weight each time you add a cargo rack (they weigh 50 lbs each). You can then compute the maximum speed as mentioned above, and the plot of maximum speed versus number of cargo racks gives a straight line. The slope of this line is the maximum speed decrease per cargo rack. This will vary based on your sail configuration, but the percentage speed decrease (speed decrease / maximum speed) will be the same for every ship. Assuming you read the section above about maximum speed, we can update our equation to include the number of cargo racks: speed = speed_max * (1 - 0.40 * num_racks/max_racks) * sqrt(1-weight/max_weight) In addition, I added weight to the cargo racks to verify that the rest of the equation still holds with cargo racks. Indeed, you see the same square root behavior. This means that the cargo rack has only the two effects listed above: max speed decrease, and weight decrease. What speed sail configuration makes the fastest ship/ what type of ship is the fastest? My results: The table in the previous section summarizes my results about the how each sail type affects the maximum speed of a ship. Using this data, you can see that larger sails are generally more efficient than smaller sails. For example, look at a brigantine: Large speed sail adds 7.93 knots to your max speed, whereas the medium sails add 4.24 to the max speed. This means that the large speed sails add 2.94 knots per sail point, and mediums speed sails only add 2.49 knots per sail point. This is the reason that you should always use larger sails first, then fill in any remaining points with smaller sails. Using the table on the left, you can see that galleons are the fastest ship in the game, when used with 6 large speed sails. This is followed by a schooner with 1 large and 1 small speed sail, and then by a brig with 3 large speed sails, and finally the sloop with 1 medium speed sail. My testing method: I mentioned it above, but once again, briefly - spawn in each type of ship and mark down the weight of the ship, the speed you travel, and the number of sails as you vary the number and type of sails on the ship. The plot of maximum speed versus number of sails is a line, and the slope is equal to the max speed increase per sail. As for the optimal sail configuration, I did not test every combination of sails possible for each ship. Although we previously discussed why larger sails are more efficient, this does not automatically mean that using only the largest sails is always going to be the most efficient, since there are some leftover points that could, in theory, be used more effectively. I set up an excel spreadsheet (on the left) with all possible combinations of sails for which you cannot add another sail. Some of these use all of the sail points, and some do not. I then computed the maximum speed with each configuration and looked for the maximum speed out of all combinations. This just so happened to be the result where the largest sails are used first, as mentioned above (and everywhere else). This just proves definitively that there is no odd combination of sails that uses sail points more effectively that beats the tactic above. How many cargo racks should I add to my ship to maximize speed? Another way to phrase this question would be - how much cargo would I have to put into a new cargo rack to justify the additional speed decrease? This depends on the ship max carry weight, your ship's "empty" weight, and the number of cargo racks already on your ship. First, let's categorize the weight into "free" and "fixed" weight, by whether or not you can put it into a cargo rack. Fixed weight includes plank weight, repair materials, and crafting stations, to name a few examples. Free weight can include whatever cargo you have on board, armor or tools, or even blueprints (although you shouldn't store blueprints in cargo racks - there are only 100 slots to fill up with 8,000 lbs to be the most efficient). The reason we want to categorize the weight is because the fixed weight is just dead weight, there is nothing we can do to reduce it. However, it will affect when we should add racks, since the speed is not linear with respect to weight. This means that we should add a rack when the amount of free weight we can store increases the speed of the ship (by reducing the weight) more than the extra cargo rack would decrease the speed. Mathematically, this gives us the equation (where x is the free weight and n is the number of cargo racks currently on the ship) Obviously, this gets complicated fast, since we want to solve for x... Well, I did that for you, and here is the equation for the amount of free weight you need to store when adding a cargo rack: where the empty weight is your fixed weight, and f(n) is listed below: ok, this is still quite complex (we haven't even touched what to do when the free weight is outside of the range between 0 and 8,000, for example), let's unpack this a little. Unpacking the results: If the math makes you queasy, that's fine. I assume most people don't want the math, just the rule they should follow. Unfortunately, there is no simple rule, because the math is so complicated. But, we can get a few interesting tidbits from it: The heavier your ship is without any cargo (the fixed weight), the earlier you should be adding cargo racks If your galleon is very light (no fixed weight), the you should add a rack if you have 15.6% of your weight capacity in free weight. For a stock ship with 30k lbs capacity, this would be about 4,700 lbs of cargo. Of course, this assumes you have all your other racks filled already. Here is a graph comparing the speed of a ship with optimal use of cargo racks versus no use of cargo racks. The flatter sections show where racks are added (for a default galleon with no fixed weight): This may feel a little underwhelming, but you can get much more accurate numbers if you actually compute the free weight from the equation above. As a note, the amount of free weight needed changes with the number of racks on your ship, so it will change as you add more and more cargo. I suggest you add a sign on your ship, noting the ship capacity and fixed weight right after you make it, and then keep track of when you should add each of the 6 boxes on another sign. What is the optimal way to haul resources long distances in as little time as possible? This is another very complicated question. In addition to the problem of the cargo racks (addressed thoroughly above), you now have the added complexity of changing your goal. There are (as far as I can see) 2 main goals when it comes to hauling resources: Haul as many resources as possible in a given amount of time. This usually occurs when you have a supply route and you will keep making return trips indefinitely. Haul a given number of resources in the shortest time possible. This usually happens when you are trading or want to go on a relatively small-scale resource expedition. For the first goal, you want to minimize the time spent on each pound of resource, so you can move as much as possible with the time you have. For the second goal, you are trying to minimize the total time spent, which is not always accomplished by moving the fastest at any given time. This is more complex. Let's look at each one individually: Hauling indefinite resources in a given amount of time: If you haul more at once, you move slower but get more across in one trip. If you haul less, you move faster but get fewer resources in one trip. We also have to consider that half of the time you are sailing, you are just bringing the empty ship back to the resource location. This means that the fixed weight of your ship makes a big difference in the optimal strategy. If your fixed weight is high, you should haul more cargo to avoid making many trips. If your fixed weight is low, you should haul less and move faster, since the wasted time on the return trip is quite small. Working through some of the math, I made some plots for the item transfer rate versus the loaded ship weight (with optimal cargo racks). Here they are, and we will discuss them after: It turns out that for 0 fixed weight, you should carry 12,530 lbs to be most efficient, and for 10,000 fixed weight, you should load up to 19,600 lbs. However, you can see from the 10k fixed weight graph that it may be possible to improve the efficiency further, since the cargo racks are optimized for speed, not item transfer rate. Specifically, adding the last cargo rack earlier would translate into extending the rightmost section of the graph further to the left, where it looks like it may reach a higher rate than this optimization allows. This is an area that can certainly be improved in the future. More unpacking: In general, you should load your ship up to about 50% of the way between the empty weight and the full weight to get the most efficient run. It can get better than that, but this will get you a majority of the way there, if you use your cargo racks optimally. Not much else to say here, that is the main rule-of-thumb of this section. Hauling a fixed amount of resources as quickly as possible: The goal here is just to minimize the time taken to get the resources back. Since speed drops off quickly as your ship fills up, the strategy will be to split the load up into equal-sized portions and take the same amount of weight each trip, so you avoid a few heavy/slow loads. Then, since every trip takes the same amount of time, we can just optimize each trip. However, the optimal weight HEAVILY depends on the amount of cargo you want to haul back. Look at the next graph (of optimal haul weights versus the target weight you wish to carry back), and let me know if you can make any sense of the chaos: One bit of information to be gleaned from this mess is what happens when you need to haul a LOT of cargo. The chaotic mess converges to the same number that we got for the case where we wanted to haul an indefinite amount of cargo at as fast a rate as possible. Here is a zoomed-out image of the same graph I just showed. Obviously this behavior is much more complex than the behavior when you just want to maximize the rate. Therefore, I suggest that you just follow the advice there and let this section be more of a curiosity than actual advice. I mean, if you want to calculate the optimal carry weight every time you want to haul cargo, be my guest Summary Here, I will just list a bunch of bullet points that summarize the findings throughout the rest of the guide: As weight increases, your ship speed will fall faster and faster. Therefore, you should aim to keep your ship at around 50% capacity as a rule of thumb. This balances the amount of cargo you are hauling with the speed decrease from the additional weight. Galleons are the fastest ship in the game, followed by schooners, and then brigantines, and sloops are the slowest. When you are putting sails on these ships, start with the largest possible sail and fill in smaller sails afterward, to get the fastest sail configuration. As a rule of thumb, add a cargo rack when you have 4,000 pounds of resources available to store in it, and always fill up any existing cargo racks as much as possible. The heavier your ship is without any cargo on board, the earlier you want to add cargo racks when filling up your ship. The perfectly optimal weight arrangement is very complicated, and depends on many factors. You can look through the rest of this post for more info, but just know that these rules-of-thumb may not always be suitable for your exact scenario, and you'll need to use a bit of common sense. Thank you for reading through this quite long guide. If you didn't understand a part of it (or any of it), I will be keeping up-to-date with the comments, so feel free to ask any questions there. If you have any ideas you want me to look into further, I am open to suggestions for another guide. If you liked this extremely thorough type of guide, please let me know, so I can be motivated to make more in the future.
  7. Hey, I see a lot of people having issues to set up their server so i will try to provide the best tutorial to build your own dedicated server. This tutorial will be on a 3x3 grids and based on this server from OVH : https://www.ovh.com/fr/serveurs_dedies/game/1901mc03.xml I will also provide ALL powershell script that you need to run your servers. Before, you will need the Server Grid Editor : - https://github.com/GrapeshotGames/ServerGridEditor/archive/master.zip Extract it on your desktop for example. - My own map : https://www.fichier-rar.fr/2019/01/26/map-3x3-by-zoro/map-3x3-by-zoro.rar - Config files : https://www.fichier-rar.fr/2019/01/26/saved-1/saved.rar 1. Windows Configuration - The first thing you will need to do is to setup a new partition, around 400 GO and call this partition with the letter A and the name Atlas (on a new disk or not, it's like you want). - The second thing to do is to setup another partition, but this one will be a bit bigger like 1To or more if you can and call it with the letter S and the name Save (it's better to do it on a new disk). So if your Windows has a problem, all your saves and your servers won't be lost. I know most of you don't care about that , but it's very important. You should have something like that now : In the A: Atlas partition, you will create an architecture (folders) like that: - AtlasServer - Launcher - Logs - McRCON - SteamCMD 2. SteamCMD and Atlas Server Installation Now, you will download this file called Installation_SteamCMD_and_AtlasServer.ps1 and put it in the Launcher folder : https://pastebin.com/SUqNtCrw (Don't forget to RENAME IT to Installation_SteamCMD_and_AtlasServer.ps1 without the .txt at the end.) Now, you can do a right click and select Execute with Powershell. For your information, you should be verycarfull when you download and execute powershell/bash code from internet because it can't completly break your Windows. This script will donwload and install Steamcmd in the folder SteamCMD and also donwload and install the Atlas dedicated server in the folder AtlasServer. 3. Map Creation This is a big part of the tutorial and probably one of the most important. So be carefull about what you will do and be sure to do step by step. 3.1 Project Creation Open ServerGridEditor (You previously extracted it on your desktop) and select Create Project. Complete like this : Atlas ID : Let the software handle it, don't touch this. Friendly Name : The name that will be display in the Atlas servers list. Cells : - X : 3 - Y : 3 CellSize : 1400000 IMPORTANT : Do not put more than this number or your map will be completely bugged. This is a Unreal Engine problem not an Atlas problem. Column UTC Offset : 0,0 New Database Settings : - Change the default password foobared by another password (put the same password everywhere) and also note it on a bloc note, you will need it later. - Do not change the Port, the URL and the name of any Entry. For all others parameters, let them empty. Then press Create. 3.2 Islands Creation To help you, there're some shortcut : To add an island, just drag and drop the island from the list on the right to the correct grid. As you can imagine, you have many island and their name are not chinese name but it's a convention. Island Naming Convention ISLANDTYPE_ISLANDSHAPE_CLIMATE_VARIANT Example Mnt_E_ET_B There you will find each type of island with their Climate Type and also the island reserved for FreePorts. You will also find 9 island called XXXX_PVE, those island are also called Golden Age Ruin where there're boss on it (Dragon, Hydra) and also Fountain of Yourth. Free Ports Cay_H_WR_E Cay_K_TR_E Cay_J_EE_E Mnt_A_WU_E Mnt_F_ET_E Mnt_J_WT_E Mnt_L_CH_E Mnt_O_CL Climate Code Climate Type CH High Desert CL Low Desert CP Polar EE Equatorial ET Eastern Temperate PO Polar TR Tropical WF West Temperate WR West Tropical WT West Temperate WU West Tundra ER East Tropical Map Lettering Designators Polar PO CP Tundra WU Temperate WF WT ET Tropic WR TR ER Desert CH CL Equatorial EE Polar West Tundra West Temperate East Temperate Tropical West Tropical East Tropical Equatorial High Desert Low Desert CP WU WF ET TR WR ER EE CH CL PO WT # By Type 1 21 20 16 37 14 41 18 19 19 33 # By Type 2 5 5 Total 26 20 21 37 14 41 18 19 19 33 248 MNT_E_CP MNT_A_WU MNT_A_WF CAY_E_ET CAY_A_TR CAY_A_WR CAY_L_ER CAY_A_EE MNT_A_CH CAY_E_CL MNT_E_CP_B MNT_A_WU_B MNT_B_WF CAY_F_ET CAY_F_TR CAY_E_WR CAY_N_ER CAY_A_EE_B MNT_A_CH_B CAY_G_CL MNT_E_CP_C MNT_A_WU_C MNT_C_WF CAY_H_ET CAY_G_TR CAY_E_WR_B CAY_O_ER CAY_C_EE_PVE MNT_C_CH CAY_G_CL_B MNT_E_CP_D MNT_A_WU_E MNT_D_WF CAY_N_ET CAY_GB_TR CAY_F_WR ISLET_A_ER CAY_E_EE MNT_C_CH_B CAY_G_CL_C MNT_H_CP MNT_C_WU MNT_E_WF MNT_A_ET CAY_H_TR CAY_G_WR ISLET_A_ER_B CAY_E_EE_B MNT_D_CH CAY_H_CL MNT_H_CP_B MNT_D_WU MNT_I_WF MNT_B_ET CAY_I_TR CAY_H_WR ISLET_A_ER_C CAY_F_EE MNT_E_CH CAY_H_CL_B MNT_H_CP_C MNT_E_WU MNT_J_WF MNT_C_ET CAY_J_TR CAY_H_WR_E MNT_D_ER CAY_F_EE_B MNT_F_CH CAY_I_CL MNT_H_CP_D MNT_F_WU MNT_JB_WF MNT_C_ET_B CAY_JB_TR CAY_I_WR MNT_E_ER CAY_G_EE Mnt_G_CH CAY_I_CL_B MNT_I_CP MNT_J_WU MNT_K_WF MNT_C_ET_C CAY_K_TR_E Cay_I_WR_B MNT_F_ER CAY_H_EE MNT_I_CH CAY_I_CL_C MNT_J_CP MNT_J_WU_B MNT_L_WF MNT_C_ET_D MNT_A_TR CAY_J_WR MNT_I_ER CAY_I_EE MNT_J_CH CAY_J_CL MNT_J_CP_B MNT_J_WU_C MNT_LB_WF MNT_D_ET MNT_C_TR CAY_K_WR MNT_K_ER CAY_I_EE_B MNT_J_CH_B CAY_K_CL MNT_J_CP_C MNT_R_WU MNT_N_WF MNT_D_ET_B MNT_H_TR CAY_K_WR_B MNT_M_ER CAY_J_EE MNT_K_CH CAY_L_CL MNT_J_CP_D MNT_R_WU_B MNT_NB_WF MNT_E_ET MNT_JR_TR CAY_L_WR MNT_N_ER CAY_J_EE_E MNT_L_CH_B CAY_L_CL_B MNT_T_CP MNT_R_WU_C MNT_O_WF MNT_E_ET_B MNT_L_TR CAY_L_WR_B MNT_N_ER_B CAY_K_EE MNT_L_CH_E CAY_M_CL MNT_T_CP_B MNT_R_WU_D MNT_OB_WF MNT_E_ET_C CAY_M_WR MNT_O_ER CAY_K_EE_B MNT_M_CH CAY_M_CL_B MNT_T_CP_C MNT_T_WU MNT_P_WF MNT_E_ET_D CAY_N_WR MNT_O_ER_B CAY_L_EE MNT_N_CH CAY_N_CL MNT_T_CP_D MNT_W_WU MNT_F_ET CAY_O_WR MNT_Q_ER CAY_N_EE MNT_O_CH CAY_O_CL MNT_Y_CP MNT_W_WU_B MNT_F_ET_B MNT_A_WR MNT_U_ER_PVE CAY_O_EE MNT_R_CH_PVE MNT_A_CL MNT_Y_CP_B MNT_X_WU MNT_F_ET_C MNT_B_WR MNT_C_EE MNT_Z_CH MNT_B_CL MNT_Y_CP_C MNT_Y_WU_PVE MNT_F_ET_D MNT_C_WR MNT_C_CL MNT_Y_CP_D MNT_F_ET_E MNT_C_WR_B MNT_C_CL_B Mnt_G_ET MNT_C_WR_C MNT_D_CL ICE_A_PO ISLET_A_WT Mnt_G_ET_PVE MNT_D_WR MNT_E_CL ICE_B_PO ISLET_A_WT_B MNT_H_ET MNT_D_WR_B MNT_F_CL ICE_C_PO ISLET_A_WT_C MNT_J_ET MNT_E_WR MNT_F_CL_B ICE_D_PO MNT_J_WT_E MNT_J_ET_B MNT_F_WR Mnt_H_CL ICE_E_PO MNT_S_WT_PVE MNT_K_ET MNT_F_WR_B MNT_I_CL MNT_K_ET_B MNT_F_WR_C MNT_J_CL MNT_M_ET MNT_F_WR_D MNT_K_CL MNT_N_ET Mnt_G_WR MNT_L_CL MNT_O_ET Mnt_G_WR_B MNT_M_CL MNT_H_WR MNT_O_CL MNT_J_WR MNT_R_CL_PVE MNT_K_WR MNT_L_WR MNT_M_WR MNT_N_WR MNT_O_WR MNT_W_WR MNT_W_WR_B MNT_X_WR_PVE I have found a bug with the ServerGridEditor that occur when : You add a new island on your map, you export it and put it on your server. You start your server, the island work properly. BUT if you want to move the island again you will need to remove it and place it again on the grid because if you don't do that, the island will be completly bugged when you will re-launch your server with the new position. You won't be able to farm any ressources and have some collision bug with rocks etc. 3.3 Discovery Zone Creation To create a discovery zone just press Shit + Left Click and expand it to do a square. To configure it also do a Shit + Left Click on the yellow square : Zone Name = The name of the Discovery Zone ID = ID of the discovery (The soft handle it directly) Zone XYZ = height and width of the zone. Zone XP = The XP obtened when a player find this Discovery Zone. ExplorerNote = The index of the explorer note (more info to come) Allow Sea = Check to allow the player to discover the discovery zone from the water (else he must go on the ground to discover it) Also note, since v15.61 there's a server side parameter to configure how many point a player can gain per discovery : Game.ini: [/script/shootergame.shootergamemode] MinPointsPerDiscoveryZone=3 3.4 Template Creation (Biome) I highly recommend to use the default template from the official server. To find them open the file Projects/ServerGrid.json with another ServerGridEditor then Edit -> Edit Server Template -> Select a Template and click Edit. On your other ServerGridEditor, Click Edit -> Edit Server Template -> Add -> Then copie EVERYTHING you see in this window (Example with the Polar template) : As you can see, there're some parameters called ServerCustomDatas1, ServerCustomDatas2. In these fields you can set all these options (and maybe some others) : ServerCustomDatas1: ,DisableRain,ChanceForCold,NPCShipDifficultyMult,NPCShipDifficultyLerp,FloatsamQualityMultiplier,RainIntervalMultiplier,DisableFog,FogIntervalMultiplier,DisableClaimFlags,NPCShipNumMult, ServerCustomDatas2 : ,1,1,1.25,0.33,1.2,0.36,1,0.36,1,1, There are 6 template on the official map: Polar, Temperate, Equatorial, Desert, Tropical, Tundra 3.5 Server Edition To edit a server : Ctrl + Left Click on a grid : Name : Name of the server Template : The template of the server (biome) IP : The public IP fo your server Port : The port of your server Game Port : The game port of your server SeamlessDataPort : This is handled by the software, do not touch this, BUT verify that no other server has the same port. As you can see with the red arrow, you may also add some configuration from the Game.ini directly in the server configuration, for example : Key : bDontUseClaimFlags Value : 1 (for true or 0 for false) You can also overwrite the ServerCustomDatas 1 and 2 from the template you linked to the server. You will need to edit all the servers and add at least an IP, Port, Game Port and verify the SeamlessDataPort. 3.6 Ship path Press P on the map to create a Ship path : To add a node, put your mouse over an existing node then press Num+ or Del to remove it. To change the path with the red circle, put your mouse over the node and press Right Click then move on the map while still pressing Right Click. To edit the Ship path : Ctrl + Left Click : There're 2 Ship path option : The Ghost Ship and the Trader Ship. Ghost Ship configuration : Path Name : GhostShip AutoSpawnEveryUTCInterval : 21600 AutoSpawnShipClass : Blueprint'/Game/Atlas/ShipPaths/PathFollowingGhostShip_BP.PathFollowingGhostShip_BP' Loop around world : Loop around the node (not sure) Auto Spawn At First Node : Checked Trader Ship configuration : Path Name : NPCTrader1 (1 to 9) AutoSpawnEveryUTCInterval : 0 Auto Spawn At First Node : Checked 3.7 Freeport First you will need to add special freeport island to your server : (Up to 4 island MAX per freeport server) Free Ports Cay_H_WR_E Cay_K_TR_E Cay_J_EE_E Mnt_A_WU_E Mnt_F_ET_E Mnt_J_WT_E Mnt_L_CH_E Mnt_O_CL When you have added your 4 island, Edit the Server configuration (Ctrl + Left Click on the server grid) : Check Home Server then Click on the Spawn Regions button then add this : Name | Parent Cell Northern Island | 0,2 Eastern Island | 0,2 Southern Island | 0,2 Western Island | 0,2 The Parent Cell correspond to the grid X,Y Example, If you want to put your freeport in A1 than put 0,0. 3.8 Export To export it, simply click Export then Local Export All. The files will be exported in the directory ServerGridEditor/Export. You will have 2 files and 1 directory (for a 3x3 map) : ServerGrid CellImg_0-0.jpg CellImg_0-1.jpg CellImg_0-2.jpg CellImg_1-0.jpg CellImg_1-1.jpg CellImg_1-2.jpg CellImg_2-0.jpg CellImg_2-1.jpg CellImg_2-2.jpg MapImg.jpg ServerGrid.json ServerGrid.ServerOnly.json I have read many post about the map being black, and some people tell to rename those file into jpeg or to add an external link to the ServerGrid.json with the "MapImageURL": "" option, but most of the problems can be resolved simply by adding the PUBLIC IP to the paramater SeamlessIP in the launch start command. (I also got this problem so i know what i'm talking about ) ↓ The tutorial continue below ↓
  8. Hallo Atlas Spieler, mit diesem Beitrag möchte ich eine einfache Installation eines Atlas Dedicated Servers beschreiben. Diesen wird es auf English sowie Deutsch geben. Vorbereitung: Natürlich braucht man einen Server mit viel Leistung um ein großen Server mit vielen Grids zu erstellen. Wir verwenden hierfür einen Server mit einer Internetanbindung von einem Gigabit sowie 2 CPUs mit jeweils 6K/6T und 64GB DDR3 RAM sowie Windows Server 2019. (Wichtig: Atlas Server benutzen viel RAM und CPU. Für unseren Server haben wir ein 4x3 Grid und der RAM lastet sich dabei auf 37GB aus. Das liegt aber auch daran wieviele Inseln man späters auf die einzelnen Grids hinzufügt.) Als "Control Tool" benutzt man das ASC von @SparcMX (Vielen Dank für dieses einfache und moderne Tool) [Link] Für das Grid benötigt man dann auch noch den ServerGridEditor. Hierbei ist es wichtig immer einen aktuellen zu benutzen da es sonst zu Problemen kommen kann mit verschiedenen Inseln! Das Tool kann hier heruntergeladen werden. [Link] Dort wird es auch immerwieder aktualisiert. Viel Zeit und Durchhaltevermögen . _________________________________________________________________________________________________________________________________________________________ Installation des Tools auf dem Server: Downloaded euch das Tool und führt es aus. Sollte ein Fenster kommen mit "Der Computer wurde durch Windows geschützt" müsst ihr auf "Weitere Informationen" und dann auf ausführen drücken. Installiert das Programm auf euren Server und führt es aus. Nachdem werdet ihr gefragt, ob ihr eine neue Installation haben wollt oder eine bestehende verwenden möchtet. Erstellt euch am besten ein Ordner auf den Desktop mit dem Namen "Atlas_SRV" und wählt diesen als Pfad für eine Neuinstallation aus. Sobald er dann den Server heruntergeladen hat sollt ihr auswählen, ob ihr ein 1x1, 2x2 oder 4x4 Grid haben wollt. Hier wählt ihr am besten 1x1 aus und vergebt eure Ports [Game, Query, Seamless] sowie den Namen des Servers und das RCON Passwort. (Wichtig ist keine Ports doppelt zu verwenden. Query: 57000 Game: 5700 Seamless: 27000) Jetzt habt ihr erfolgreich ein Atlas Server heruntergeladen und eingestellt! Nun könnt ihr das Programm beenden und den ServerGridEditor starten wenn ihr nicht schon ein selber erstelltes ServerGrid habt. _________________________________________________________________________________________________________________________________________________________ ServerGridEditor, Welten, Schiffe etc: Um auf einem Atlas Server spielen zu können benötigt ihr ein ServerGrid das Inseln sowie Schiffpfade beinhaltet. Downloaded euch hierfür den ServerGridEditor und entpackt ihn auf dem Desktop. Erstellt euch am besten auch einen Seperaten Export Ordner um die Datein nachher dort zu Exportieren. Sobald das erledigt ist könnt ist im Ordner "ServerGridEditor-master" den Editor starten. Geht nun folgende Schritte durch: Drückt auf "Create Project" und kopiert die Atlas Id und schließt das Fenster wieder. (WICHTIG!) Drückt nun auf "Load Project" und wählt die ServerGrid2x2.json aus. (Der Grund warum nicht die ServerGrid.json => ServerGrid.json ist 15x15 Grids nicht 1x1 Grids) Nachdem die ein 2x2 Grid geöffnet hat geht ihr auf "Project" => "Edit" und fügt dort eure Kopierte Atlas ID ein. Zudem könnt ihr hier gleich: Friendly Name (Name eures Servers) Cells [X/Y] (Größe des Grids, 2x2 = 4 Server, 3x3 = 9 Server etc.) Map Image URL (Kann gelöscht werden) MetaWorldURL (Kann gelöscht werden) BaseServerArgs (Kann gelöscht werden) einstellen. Warum Map Image URL und MetaWorldURL gelöscht werden kann => Wir verwenden nachher die Maps vom ServerGrid Lokal. BaseServerArgs werden nachher vom ASC eingestellt. Mit Edit die Einstellungen übernehmen. Wichtig: Bevor ihr die Inseln auf die jeweiligen Grids zieht muss jedes Grid manuell eingestellt werden. Hierfür drückt ihr "STRG" auf ein Grid und gibt folgendes ein bei: Name: Name des Grids IP: IP Adresse des Servers (KEINE DOMAIN ODER DNS) Port: Den Querry Port (z.B 57000 [Ist nachher der Port auf den die Spieler sich drauf verbinden]) Game Port: Der Game Port (z.B 5700 etc. Nicht den gleichen Port wie der Query Port) SeamlessDataPort: Der Seamless Port (z.B 27000) Home Server: Wird nur auf dem Grid eingestellt wo ihr auch eure Startinseln habt. Dabei muss beachtet werden das jedes Grid einen anderen Port braucht. Ich empfehle für den Home Server (z.B A1) einen "schönen" Port wie z.B Query Port: 57000 Game Port: 5700 Seamless Port: 27000 Solltet ihr nun 2x2 oder mehr Grids besitzen würde Ich für jedes Grid immer den Port um 2 bei allen erhöhen (57002, 57004..., 5702, 5704..., etc.) Nun könnt ihr euch mit dem Editor austoben und verschiedenen Inseln auf der rechten Seite per Trag and Drop hinzufügen. Wichtig ist darauf zu achten nicht zuviele Inseln auf ein Grid zu machen da mehr Inseln auch mehr RAM und CPU benötigen. Zudem gibt es vorgefertigte Biome. Diese passen auch zu den meisten Inseln da diese gekennzeichnet sind im Namen. Polar = PO & CP Tundra = WU & CU & EU Temperate = WF & WT & ET Equatorial = EE & BO Tropic = WR & ER & TR Desert = CL & CH Um einem Grid ein Biom zuzuordnen muss man mit "STRG" auf das jeweilige Grid klicken um es zu bearbeiten. Dort steht dann oben dann Template. Außerdem gibt es Inseln mit einem "_E". Diese sind Startinseln mit Händlern und einem Begrenztem Level. Erkundigt euch am besten anhand von dieser Liste wo welche Materialen vorkommen. Um später Blueprint Waffen etc. herzustellen werden diese Benötigt. Mit diesen Inseln werdet ihr aufjedenfall alle Ressourcen haben. Schiffspfade: Im Editor lassen sich auch Schiffspfade einrichten von Händlerschiffen sowie einem GhostShip. Dabei muss beachtet werden, dass "GhostShip" nicht die kleineren Geisterschiffe sind sondern die große Galleone die in der Nacht spawnt. Dieses Geisterschiff kann als Quest für den 9. PowerStone verwendet werden. Um ein Schiffspfad hinzuzufügen müsst ihr, am besten an einem Meer, die Taste "P" drücken. Nun habt ihr 3 Punkte die ihr verschieben könnt und mit "Numpad +" werden mehr Punkte generiert. Diese Punkte verlegt ihr nun und achtet darauf das keine Linie durch eine Insel geht. Sollte das der fall sein kann mit Rechtsklick auf einem Punkt die Route angepasst werden (Rundungen etc.) Wenn ihr alle Schiffsrouten erstellt habt müsst ihr mit "STRG" auf die Schiffsroute draufklicken und folgende Werte bearbeiten: Path Name: Entweder NPCTrader1 (NPCTrader2, NPCTrader3...) oder GhostShip AutoSpawnEveryUTCInterval: 41600 (oder eigenen Wert) AutoSpawnShipClass (Nur wenn im Path Name GhostShip angegeben ist): Blueprint'/Game/Atlas/ShipPaths/PathFollowingGhostShip_BP.PathFollowingGhostShip_BP' Discoverys (Ohne PowerStones): Was sind überhaupt Discoverys? Discoverys sind Entdeckungen die einem Spieler einen XP Boost (oder XP direkt) geben. Hier erscheint beim erkunden einer neuen Insel eine Schriftrolle mit dem Namen des Discoverys. Warum werden Discoverys benutzt? Um Spielern XP zu geben sollten sie eine neue Insel erkunden oder um das Maximale Level zu begrenzen. Den das Hängt auch damit zusammen. Spieler werden schnell das Maximale Level erreichen wenn sie nicht andere Inseln erkunden. Wie kann ich Discovery Zonen hinzufügen? Im ServerGridEditor kann mit "SHIFT" und Linker Maustaste ein Bereich gezogen werden. Diesen könnt ihr auch später noch verschieben. Über "EDIT" => "Edit Discovery Zones" könnt ihr nun verschiedene Werte eingeben: ManuelName: Wird später interessant Name: Der Name der Discovery (wird später auch im Spiel so angezeigt) XP: Die XP die ein Spieler bekommen soll (z.B 5 bei einer normalen Insel und 10 bei einer PVE Insel) ExplorerIndex: Wird später interessant allowSea: Wenn hier ein Haken drin ist muss der Spieler die Insel betreten um das Discovery zu erhalten (Landfall required). Wenn der Haken nicht drin ist muss der Spieler nur in die Zone der Discovery reinfahren. Ich würde empfehlen immer ein Discovery zu erstellen und es dann direkt zu bearbeiten, da man sehr schnell den Überblick verliert. Sobald dann alle Discoverys erstellt wurden könnt ihr zum nächsten Schritt. _________________________________________________________________________________________________________________________________________________________ Exportieren des fertigen ServerGrids: Erstellt euch am besten auf dem Desktop ein Ordner mit den Namen Export wo ihr dann die Sachen exportiert. Nun könnt ihr das fertige ServerGrid exportieren inklusive MapImage und CellImages. Klickt hierzu auf "Export" und geht alle 3 durch (All, Only Map Image und Only Cell Images). Mit All wird leider nicht alles Exportiert warum auch immer. Die MapImage und CellImages müssen in den Ordner ServerGrid. Exportiert am besten erst All in euern Export Ordner und danach das Map Image sowie die Cell Images in der ServerGrid Ordner. Schließt das ASC (falls nicht schon getan) und kopiert alle Datein im Export Ordner in den Ordner des Servers unter ShooterGame (<Server-Dir>/ShooterGame). Jetzt könnt ihr wieder das ASC starten und schauen ob er euer ServerGrid direkt übernommen hat indem ihr auf den ServerGridEditor im ASC klickt. Wird euch dort das neue angezeigt könnt ihr die Server starten. Falls nicht folgt dieser Anleitung: Drückt auf Service Menu => Reload ServerGrid Wählt das ServerGrid was euch vorgeschlagen wird (das im Server Verzeichnis) aus. Startet ASC neu und falls Fehler kommen öffnet ihr es trotzdem Wiederholt nun die Schritte 1 und 2 nocheinmal und startet es nochmal neu Nun sollte das ASC ohne Probleme starten und bei Cluser Overview werden euch auch alle Server angezeigt _________________________________________________________________________________________________________________________________________________________ PowerStones Einstellungen: !!Dieser Schritt kann auch übersprungen werden wenn man nicht den Endboss besiegen möchte!! Wozu dienen PowerStones? PowerStones sind Kristalle, die ihr von einem Endgegner (Hydra oder Drachen) auf einer PVE Insel bekommt. Nachdem ihr den Endgegner getötet habt bekommt ihr ein Artifact Key mit dem ihr in die Höhle auf der PVE Insel euren PowerStone abholen könnt. Insgesammt gibt es 9 PowerStones. Davon sind 8 auf PVE Inseln versteckt und einer auf dem "GhostShip". Hat man alle gesammelt kann man den Endgegner (Krake) besiegen und vollendet die Quest. Was muss Ich alles einstellen damit die Quest funktioniert? Zuerst müsst ihr euch sicher sein das ihr alle PVE Inseln besitzt. Hierzu gibt es 8 verschiedene: Cay_C_EE_PVE MNT_G_ET_PVE MNT_R_CH_PVE MNT_R_CL_PVE MNT_S_WT_PVE MNT_U_ER_PVE MNT_X_WR_PVE MNT_Y_EU_PVE ACHTUNG: Es gibt einmal MNT_Y_EU_PVE einmal MNT_Y_WU_PVE. Verwendet die Insel mit "EU" im Namen da die andere nicht funktioniert (Keine Landschaft und keine Gegner/Tiere). Was ihr noch wissen müsst: Der PowerStoneIndex beginnt bei 0 und geht bis 8. Unter dem ManuelName gibt es den PowerStone und dieser beginnt bei 1 und geht bis 9. Ich hab statt dem GhostShip eine PVE Insel genommen da das GhostShip nicht immer richtig funktionierte. Ihr könnt euch da eine Insel welche ihr halt dann 2x hinzufügt. Wie ihr nun vorgehen müsst: Öffnet euer ServerGrid im ServerEditor und fügt die PVE Inseln hinzu. Editiert jede Insel mit "STRG" auf dien jeweilige Insel. Hier müsst ihr nun den PowerStoneIndex im IslandInstanceCustomDatas1 eintragen. Im IslandInstanceCustomDatas2 wird der Wert (0-8) eingetragen. (Jede Insel benötigt einen anderen [0-8]) Nun sind die Inseln konfiguiert. Jeder PowerStone hat aber auch sein eigenen Discovery. Erstellt ein Discovery auf einer freien Fläche (Meer) und klickt auf "EDIT" => "Edit Discovery Zones" Nun habt ihr eine neue Discovery Zone und trägt folgende Werte ein: Dies wiederholt ihr nun insgesamt 10 Mal bis es dann bei euch aussieht wie bei mir ⬎ !!!Erstellt auch auf jeder Insel ein normales Discovery ohne diese Werte wie oben bei Discoverys angegeben! Die PVE Inseln benötigen auch ein Discovery!!! Wichtig: Hacken bei isManuel muss rein. Insgesamt gibt es 9 PowerStones. Für jeden PowerStone muss eine Discovery angelegt werden mit unterschiedlichen ManuelNamen und ExplorerIndex. Auflistung: ManuelName ExplorerIndex PowerStone1 = 21 PowerStone2 = 22 PowerStone3 = 23 PowerStone4 = 24 PowerStone5 = 25 PowerStone6 = 26 PowerStone7 = 27 PowerStone8 = 28 PowerStone9 = 29 TheSeaDemon = 20 Bei SizeX SizeY und SizeZ tragt ihr bei allen den Wert 0 ein. Bei Name könnt ihr reinschreiben was ihr wollt. Dies wird nachher im Spiel angezeigt. Hier mein Beispiel (inklusive XP): PowerStone1 Der Violette Stein! XP 40 PowerStone2 Der Blaue Stein! XP 40 PowerStone3 Der Tuerkise Stein! XP 40 PowerStone4 Der Gruene Stein! XP 40 PowerStone5 Der Gelbe Stein! XP 40 PowerStone6 Der Orangene Stein! XP 40 PowerStone7 Der Rote Stein! XP 40 PowerStone8 Der Weiße Stein! XP 40 PowerStone9 Der Cyan Stein! XP 40 TheSeaDemon Der Finale Kampf XP 40 So sollte es dann bei euch aussehen: Um "TheSeaDemon" zu erstellen würde Ich euch ein leeres Grid empfehlen wo keine Inseln drauf sind. Editiert das Leere Grid mit "STRG" auf das Grid und gebt folgenden Wert bei "ExtraSublevels" ein: EndBossLevel So sollte es dann bei euch aussehen: Mit diesem Wert spawnen keinerlei Gegner auf dem Grid und sobald man alle PowerStones hat spawnt der Endgegner (Krake). Nachdem das alles erledigt ist speichert ihr das Projekt ab. ("Project" => "Save") Nun könnt ihr den Editor erstmal schließen. Öffnet nun die ServerGrid.json die ihr abgespeichert habt mit einem Editor (NotePad++). Erklärung was nun mit NotePad++ gemacht wird: Wir ändern nun die Werte für die Discoverys damit diese im Spiel angezeigt werden. Hierbei muss beachtet werden das die Werte PowerStoneIndex und PowerStone immer in paaren bleiben müssen: PowerStoneIndex 0 = PowerStone 1 PowerStoneIndex 1 = PowerStone 2 PowerStoneIndex 2 = PowerStone 3 PowerStoneIndex 3 = PowerStone 4 PowerStoneIndex 4 = PowerStone 5 PowerStoneIndex 5 = PowerStone 6 PowerStoneIndex 6 = PowerStone 7 PowerStoneIndex 7 = PowerStone 8 PowerStoneIndex 8 = PowerStone 9 Drückt in NotePad++ "STRG + F" um eine Suche zu starten. Sucht nun die Discovery Zone die über der Insel mit dem PowerStoneIndex 0 ist. Mein Bsp: Kopiert euch die letzten 3 Zeilen ("worldX bis "rotation": 0.0) Sucht nun nach dem PowerStone1 Discovery und fügt hier die Werte die ihr kopiert habt ein: Wiederholt dies bei allen 9 PowerStones. Jeder PowerStone muss dann die Werte vom Discovery der jeweiligen PVE Insel haben (worldX, worldY und rotation). WICHTIG: Die PowerStones müssen immer im Paar bleiben wie oben genannt! Ich würde empfehlen die Discovery Zones von den PVE Inseln so zu bennen wie der PowerStoneIndex auf der Insel. Ich hatte nebenbei mein ServerGridEditor noch offen deshalb wusste Ich wo welche Discovery Zone ist. Sobald das Fertig ist speichert ihr die ServerGrid.json ab und öffnet sie wieder im ServerGridEditor. Nun wird es ein wenig Rechnerisch: Es gibt das "Feature" die PowerStones auf der Karte Ingame anzeigen zu lassen. Diese sind mit der Quest verknüpft und diese Punkte können auch ausgerechnet werden. Bewegt ihr eure Maus über das Grid stehen oben Rechts 2 Koordinaten (X, Y). Geht mit der Maus über alle eure PowerStone Inseln und schreibt euch die Werte auf. Am besten beginnt ihr hier auch mit der Insel mit dem PowerStoneIndex 0 und arbeitet euch hoch bis 8. Speicher euch es am besten so ab: PowerStoneIndex0: RausgeschriebenerWertX0: <WertX> RausgeschriebenerWertY0: <WertY> PowerStoneIndex1: RausgeschriebenerWertX1: <WertX> RausgeschriebenerWertY1: <WertY> PowerStoneIndex2: RausgeschriebenerWertX2: <WertX> RausgeschriebenerWertY2: <WertY> etc. Sobald ihr die Werte aufgeschrieben habt müsst ihr eine Zwischenrechnung machen. AnzahlXGrids * 1400000 = GridX | RausgeschriebenerWertX0 / GridX = EndergebnissX AnzahlYGrids * 1400000 = GridY | RausgeschriebenerWertY0 / GridY = EndergebnissY Schreibt euch dann maximal 6 Nachkomma stellen raus. zB. 0.500000 Ihr müsst dann insgesamt 16 Ergebnisse haben: Speicher es euch am besten so ab: PowerStoneIndex0: EndergebnisX0 = <Wert> EndergebnisY0 = <Wert> PowerStoneIndex1: EndergebnisX1 = <Wert> EndergebnisY1 = <Wert> PowerStoneIndex2: EndergebnisX2 = <Wert> EndergebnisY2 = <Wert> etc. Diese Ergebnisse müssen nun in diesen Parameter eingetragen werden: (QuestEntries=((QuestID=0,CompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Icon_PowerStonesQuest_Complete.Icon_PowerStonesQuest_Complete',UncompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Icon_PowerStonesQuest_Uncomplete.Icon_PowerStonesQuest_Uncomplete',QuestName="PowerStone Quest",QuestDescription="Reise um die Welt um alle Power Stones zu finden und bringe sie zum Endgegner",QuestPointsOfInterest=((PointOfInterestID=0,PointOfInterestName="Power Stone 1",WorldMapPosition=(X=0.300529,Y=0.602469),CompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Item_InfinityGem_Icon.Item_InfinityGem_Icon',UncompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Item_InfinityGem_Icon10.Item_InfinityGem_Icon10'),(PointOfInterestID=1,PointOfInterestName="Power Stone 2",WorldMapPosition=(X=0.373015,Y=0.708994),CompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Item_InfinityGem_Icon2.Item_InfinityGem_Icon2',UncompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Item_InfinityGem_Icon10.Item_InfinityGem_Icon10'),(PointOfInterestID=2,PointOfInterestName="Power Stone 3",WorldMapPosition=(X=0.538741,Y=0.243307),CompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Item_InfinityGem_Icon3.Item_InfinityGem_Icon3',UncompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Item_InfinityGem_Icon10.Item_InfinityGem_Icon10'),(PointOfInterestID=3,PointOfInterestName="Power Stone 4",WorldMapPosition=(X=0.631745,Y=0.830099),CompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Item_InfinityGem_Icon4.Item_InfinityGem_Icon4',UncompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Item_InfinityGem_Icon10.Item_InfinityGem_Icon10'),(PointOfInterestID=4,PointOfInterestName="Power Stone 5",WorldMapPosition=(X=0.926454,Y=0.692768),CompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Item_InfinityGem_Icon5.Item_InfinityGem_Icon5',UncompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Item_InfinityGem_Icon10.Item_InfinityGem_Icon10'),(PointOfInterestID=5,PointOfInterestName="Power Stone 6",WorldMapPosition=(X=0.792592,Y=0.820458),CompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Item_InfinityGem_Icon6.Item_InfinityGem_Icon6',UncompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Item_InfinityGem_Icon10.Item_InfinityGem_Icon10'),(PointOfInterestID=6,PointOfInterestName="Power Stone 7",WorldMapPosition=(X=0.475249,Y=0.142661),CompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Item_InfinityGem_Icon7.Item_InfinityGem_Icon7',UncompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Item_InfinityGem_Icon10.Item_InfinityGem_Icon10'),(PointOfInterestID=7,PointOfInterestName="Power Stone 8",WorldMapPosition=(X=0.701234,Y=0.604506),CompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Item_InfinityGem_Icon8.Item_InfinityGem_Icon8',UncompletedIcon=Texture2D'/Game/Atlas/UI/Icons/Item_InfinityGem_Icon10.Item_InfinityGem_Icon10'),(PointOfInterestID=8,PointOfInterestName="Power Stone 9",WorldMapPosition=(X=0.205290,Y=0.785890),CompletedIcon=Texture2D'/Game/Atlas/UI/Icons/HUD_GhostShip_Icon_Complete.HUD_GhostShip_Icon_Complete',UncompletedIcon=Texture2D'/Game/Atlas/UI/Icons/HUD_GhostShip_Icon.HUD_GhostShip_Icon'),(PointOfInterestID=9,PointOfInterestName="Bringe alle Power Stones zum Endgegner!",WorldMapPosition=(X=0.879893,Y=0.503703),CompletedIcon=Texture2D'/Game/Atlas/UI/Icons/HUD_BossLocation_Icon_Complete.HUD_BossLocation_Icon_Complete',UncompletedIcon=Texture2D'/Game/Atlas/UI/Icons/HUD_BossLocation_Icon.HUD_BossLocation_Icon'))))) Kopiert euch den Parameter und fügt ihn in Notepad++ ein. (Hier reicht eine Temporäre Datei da wir nur die Werte ändern müssen) Sucht nun wieder nach PowerStone1. Dort steht später ein Wert bei X und Y drin. Ersetzt diesen mit euren gerechneten Werte. Hier ist auch wieder PowerStone1 = PowerStoneIndex0. Am Ende sucht ihr noch nach PointOfInterestID=9 und gebt da euren ausgerechneten Wert für den Endboss ein. Nun kopiert ihr den kompletten Parameter und fügt ihn beim ServerGridEditor unter "Project" => "Edit" => "globalGameplaySetup" ein. Speichert es mit Edit und fertig ist euer ServerGrid mit den PowerStones! Nun müsst ihr nurnoch die gleichen Schritte wie oben durchführen: _________________________________________________________________________________________________________________________________________________________ Anleitung wird noch weiter geupdated sobald ich Zeit habe (Es folgt noch: GameUserSettings.ini/Game.ini; Mods; Global Options; Event Schedule) Bei Fragen könnt ihr einfach ein Kommentar da lassen oder auf unseren TeamSpeak3 Server kommen "multilex.de". Dort werdet ihr mich eigentlich jeden Abend finden (unter den Namen Marco) falls ihr Hilfe benötigt. Sollte Ich mal nicht da sein könnt ihr auch einen Admin nach mir Fragen. Dafür ihn einfach anstupsen. Dieser wird mich dann benachrichtigen.
  9. Introduction For this forum post, I thought I would cover some of the wind mechanics. I think this will conclude my discussion of the wind mechanics (unless anyone can think of something else to test!) that started with ship weight and cargo racks (somewhat related to wind mechanics) and continued to my discussion of the sextant buff. Once you finish reading the guide, you should have a very good idea of how to efficiently travel around the ATLAS, armed with the knowledge of the invisible force in ATLAS that allows ye' scallywags to explore the open ocean - the wind! To organize the post a bit, I will try to progressively get into more of the details toward the end of the guide, and reserve the beginning as a summary for people who don't really care about the details. I will summarize the main points in the "Big Questions" section, and most of the discussion will be in "The Bulk" section. For those interested in the intricate details with how I did my testing, I will leave most of that to "The Details" section. Big Questions How do the different types of sails (speed, handling, and weight) differ? The sails differ in the effective angle and maximum speed that they can give the ship. Speed sails give more maximum speed than the other two sails, and handling sails give a larger effective angle than the other two sails. Weight sails have the same effective angle as a speed sail, but they contribute much less to the maximum speed than speed sails - in return, they will add maximum weight to your ship. When should I use one type of sail over another? Weight sails should only be used when the ship is very overweight. As a rough estimate, put on the first weight sail around 65%, and add more weight sails every 7% weight you add on from there. Handling sails are faster than speed sails only when you are sailing against the wind (up to 27 degrees either direction from directly against the wind). The benefit with handling sails is that you will never bottom out on speed, unlike speed and weight sails which bottom out quite easily. However, if you aren't making a ship specifically to sail against the wind, speed sails are more widely applicable, just use them. How does the wind rotation work? The wind rotates in a large circle at a constant speed. It takes about 5 real-life hours (+/- 5 minutes) for the rotation to complete, and it goes through 2 full-wind/low-wind cycles every time. That means that if you are currently in low wind, wait 75 minutes, and the wind will be strong. Furthermore, the strong winds only point North or South, and the weak winds only point East or West. If you have the luxury to plan multiple bases far apart, this means that it will be easier to get back and forth between them if you put them close to the same column (vertically). Does sail angle affect ship speed? How about wind angle within the effective angle? Unlike in real life, the angle that your sails make to your ship's body make NO difference to your speed. The only angle that changes your ship speed is the angle between your sails and the wind. As this angle increases, the ship speed steadily decreases, even at small angles within the effective angle. Similarly to how weight effects your ship speed (in-depth discussion here), the speed drops off very quickly as you approach the effective angle. Therefore, it is wise to minimize the angle between your sails and the wind whenever possible. Related questions that I will not be answering in this post: How does ship weight affect the speed of the ship? How accurate are the numbers that the sextant buff gives you? The Bulk 1. How do the different types of sails differ? All sails have 5 values that dictate their differences: Maximum weight addition, effective angle, acceleration, maximum speed, and turning effectiveness. I mainly tested what I believe to be the most important values, and I may update this post in the future to discuss the acceleration and turning effectiveness, which only affect the handling sails. The rest of this discussion talks about the maximum weight increase, maximum speed, and effective angle of each type of sail. Speed Sail: Speed sails have an effective angle of about 82 degrees, and by far have the fastest maximum speed of any sail type. In addition, they don't add any maximum weight to your ship - they are the simplest and most reliable type of sail in the game. Weight Sail: Like speed sails, weight sails have an effective angle of 82 degrees. However, they produce less maximum speed than speed sails (about 60% speed) in return for increasing the maximum weight of your ship. Small weight sails will increase the maximum weight by 1,000 kg, medium sails will increase it by 2,500 kg, and large sails will increase the maximum weight by 4,000 kg. Handling Sail: Handling sails have the largest effective angle of any sail in the game, at around 118 degrees. Their speed is between the speed of weight sails and speed sails (around 75% of a speed sail's max speed), but they have the fastest open/close times of any sail, and they also rotate faster than the other sails. Side note: Since the angle of the sails to the ship body doesn't matter, and the sails can be rotated to +/- 75 degrees, you can always reach a max speed for the first 75 degrees by rotating the sails. After that is when the effective angle starts kicking in, and you will bottom out on speed at 157 (82+75) degrees with a speed sail, and 193 (118+75) degrees with a handling sail. Since 180 degrees is straight behind you, this means that you will never bottom out on handling sail speed unless you purposefully point your sail in the wrong direction. Speed sails, however, have a 46 degree arc toward the rear of the ship where you can bottom out in speed no matter what you do. 2. When should I use one sail type over another? In typical sailing conditions, speed sails are almost always faster than weight or handling sails. Unless you like the feel of sails opening and closing quickly, I would argue (although this is speculation, I haven't done the math on this) that speed sails are always better than handling sails, when used optimally. As for why I haven't done the math on this, consider the following complication: Handling sails are faster than speed sails only past 153 degrees. That gives you a 54 degree window for which handling sails would be better. However, it might be faster to just adjust the angle you sail at to make the speed sail faster, and then tack back toward your destination when you get closer. It makes your trip longer, but you also go faster. Weight sails have a bit more utility for hauling large loads. However, they only add a fixed amount of ship weight (not a percentage), so they are relatively less beneficial as you put points into weight. Additionally, you can split up your haul into 2 trips if you really have to carry a lot, and that may even speed up your haul time. In general, it is beneficial to add your first weight sail at 63% weight, and then add another one every 8% weight you add after that. If you have not read my guide regarding cargo racks, I highly recommend you read that if you have a heavy ship. At any weight that you would consider using weight sails for, you should also be considering cargo racks, unless you have a lot of weight that you cannot put in cargo racks (such as cannons and cannonballs). This is a section that I can definitely do a bit more testing and mathematics (trigonometry, here I come), so I will be updating this in the future. Until then, much of the notes in this section are speculation based on dozens of hours of testing these mechanics. Trust them or don't, it's up to you. 3. How does the wind rotation work? The wind rotation is locked into the cardinal directions - strong winds always go North or South, whereas weak winds always go East or West. Furthermore, the rotation is locked into the clock as well - strong winds always happen at Noon and weak winds always happen at Midnight. There is a day in between strong and low wind, so if you have strong wind (at Noon on some day), the next low wind happens at midnight the following day, 1.5 days later. If you currently have low wind, just wait 1.5 in-game days for the next strong wind period. Since one in-game minute is 2.1 seconds (see my sextant buff post for more details), This means you should wait for 75 minutes to get the opposite strength of wind. The wind strength does not change consistently over the course of the rotation. From Noon on the day before the weakest wind until Noon on the day after the weakest wind (for a total of 1 in-game day), the wind strength drops to the minimum and then rises very quickly, starting and ending at about 50% wind strength. Therefore, most of the time the wind is above 50% strength, and if you find yourself caught in a low wind period, you only have to wait until the next Noon for the wind to become strong again. Pull over, feed your animals, pay your crew, and you can be on your way again in no time! The image on the left shows how the wind strength arrow changes over time, with the in-game time overlaid around the image to show you how fast it rotates. You can see in this image why you should wait for the next Noon after a low wind - that is when the wind starts picking up again! 4. Does sail angle affect ship speed? How about wind angle within the effective angle? As long as your sails are pointing with the wind, the angle your sails make with the body of your ship does not affect your speed. Therefore, only the angle between your sails and the wind makes an impact on your speed.This angle makes a big difference in your speed as you get close to the effective angle. For example, if you are 75% of the way to the effective angle, you still have about 61% of your max speed. Once you reach 90% of the way to the effective angle, though, your speed drops to 44% of your max speed. At 95% of the effective angle, you only have 35% of your speed left. Wind-sail angle effects your ship in a very similar way to weight. The biggest difference is that when you reach the effective angle, you go a minimum speed of 29% of the max speed. However, because of the very fast drop-off of speed as you approach the effective angle, it is generally wise to not get anywhere near it. In-game, this means that you should avoid sailing in a direction that makes your sails turn red in the HUD indicator, and think a bit about your heading if your sails are dark orange. It may be wiser to turn a little more with the wind, and then cut back in the other direction (tack) when you get closer to your destination. The Details Testing Details All numbers in this guide were obtained through testing in single player, and confirmed (somewhat) using the numbers in the devkit. It is hard to convert the numbers in the devkit into actual usable in-game numbers, but I did my best. If anyone is familiar with the devkit and would like to give me a tutorial, I would love to talk to an expert, just message me and I will give you my details. For the most part, the tests I ran involved getting the sextant buff, then equipping a ship with a specific sail configuration and sailing it across H8 (no islands, so I can stay within a single grid and get about 19k meters of testing space, along a diagonal). Once the knot display reached a stable speed, I recorded the time, latitude, longitude, and speed in knots, given by the sextant buff. I recorded this data again at the opposite end of H8, and computed the total distance traveled and the time in game-minutes it took to travel that distance (in longitude units). I then converted this speed in long/game-minutes into ATLAS knots (see my sextant buff post for details). For the effective angle calculations, I had to do something slightly different. I aimed my ship as close to true North as I could. This involved setting the wind direction (using setdir 90) to North and the wind speed (using setwind 12) to the maximum strength, and rotating my ship until the wind arrow had no pixels off of the directly vertical line. I verified my (very close to) true North heading by sailing some time and noticing no change in the longitude coordinate. In fact, for much of my testing, my ship could lean left and show one longitude and lean right to show another, 0.01 higher. Because this lasted a long time, I am fairly confident in my heading being essentially true North. With my ship and sails pointing due North, I set the wind to many different angles away from North (using setdir X), and recorded long/lat/time like before. However, there is the added complication of crossing server borders. I kept track of the time as I crossed borders (only going North, remember, not East or West), and there was no time gained or lost. The coordinates were a different matter - when you cross a border (at least in Single player), the game puts you at 0.14 longitude units further than you entered. I just had to keep track of how many borders I crossed and subtract 0.14 for each one. This added some error, but I couldn't think of a better way to do the tests without rotating the ship between tests. If I did rotate between tests, the slight variation in the way my ship was pointing would make the effective angle very difficult to compute, since small changes in angle near the effective angle make a large difference in the ship speed. Any derived numbers (like maximum speed contribution per sail) were obtained using the trendline function in Excel, or the Solver addon for Excel. Detailed Numbers I will put detailed information here about the specific numbers I obtained from testing. I will also update this section if I did some math that confuses anyone. - Since the full wind rotation takes 6 in-game days, the wind rotates around at 60 degrees per in-game day, or 1.19 degrees per real-life minute. Additionally, the strength of the wind changes twice as fast in the "low wind region" from Noon before the lowest wind until Noon after the lowest wind. The graph below shows this region where the wind power changes much more rapidly. - Weight and speed sails have an effective angle of 82.0305 degrees, and handling sails have an effective angle of 117.725 degrees - The table below shows my current data on maximum speed from each type of sail, for each type of ship. I will be adding to this in the future, as I collect more data. - Handling sails are faster than speed sails once you pass 152.59 degrees. At that point, you should switch all sails over to handling sails (if you can't just rotate a few degrees to make the speed sails worth it). Conclusion Generally, you will want to use speed sails, and only in rare cases will you want to use handling or weight sails, since their benefits don't outway the massive increase in speed that speed sails give. However, if the wind is just too weak and you are doing everything you can to milk speed out of your ship, you can always just wait for the next Noon, and the wind will be guaranteed to be at 50% and rising in strength. Finally, Avoid sailing in a direction that makes your sail HUD indicator dark orange, since your speed drops off very quickly as you get close to the effective angle, where the sails turn red. Please leave a comment if you think I missed anything, and let me know if I have not explained something clearly enough. I am happy to answer DMs or regular comments. Finally, I would like to thank @Kummba for encouraging me to look into the wind mechanics, and giving me a jumping off point with the wind rotation mechanics. See you on the high seas!
  10. INTRODUCTION: The sextant buff is one of the most useful buffs in the game, so I figured a guide explaining how to get it, what it does, and what aspects of it you should not take for granted, would be quite worth it. I'll start by listing the questions I am going to answer, and then we'll get into the thick of the content. The Big Questions: What is the sextant buff, and how does it help? How do I get the sextant buff, and how long does it last? How large are the grids (and the whole ATLAS map), in terms of lat/long points or meters? When would crossing the edges of the map to get to another grid make my trip faster? How accurate are the speed, lat/long, and direction that the sextant tells you? What is an ATLAS knot? Related questions other posts have answered, that I will skip here: Which type of ship is the fastest? Read on for more detailed info on each of these topics! What is the sextant buff, and how does it help? The sextant buff is a buff that helps you navigate the seas. When you apply the buff, you will be given the following information as a HUD at the top of your screen: A compass showing the direction you are looking in A minimap of your surrounding area (able to be toggled on/off via the settings menu) What region you are currently in, including any special qualities of that grid (lawless, golden age ruins, etc) latitude and longitude coordinates of your current position When sailing a ship: The direction you are headed and your current speed in knots In-game map marker overlay and guidance. Left-click on an ATLAS map marker to activate an in-world guidance marker. minimap and ATLAS map player markers show the direction you are facing Although the buff is indispensable in helping you navigate the seas, it is also very useful on land. I have used the sextant buff to help navigate an island due to the minimap that comes with it, as well as to line up my camera to the cardinal directions for building. Feel free to share in the comments if you have any creative ways you have used the sextant buff! How do you get the sextant buff? To get the sextant buff, you first have to unlock and get the sextant. The sextant is unlocked by the "Navigator's Tools" skill, which is the first skill in the Seamanship skill tree. It takes 11 skill points after a respec to get to this skill. Once you have it unlocked, you have to craft it with the materials shown in the wiki page. The sextant is a tool that you can use to get the buff. To use it, you will first need to get to a high location, typically the crow's nest of your tallest sail if you are on a ship. Hold right-click to bring the sextant up to your eyes, and start looking around for stars in the sky. They will still be visible in the day, and they will have a green diamond show up around them if you get close. Once the diamond shows up, left-click while continuing to hold down right click. This will add a star to your total, and 4 stars are needed to get the buff. Once you add a star to your total, a trail will lead from it to the next star. However, you have to try to be fast, since you only have a few seconds to find all of your stars. Here are a few tips: During the day, the first star tends to be near the sun (not rigorously tested) The trails that lead from one star to the next will curve if they travel a long distance, since they move on a sphere, which distorts their motion. Try to follow the curve around, or you will end up quite far from where the star actually is. Once you click on the first star, you will have 50 seconds to find your stars (+5 seconds for each cosmology level, then x1.10 for each level in able navigator skills) If you find 4 stars, you will get 1500 seconds (25 minutes) of sextant buff. Each star above that will give you +1180.6 seconds (almost 20 minutes) of buff, up to the 9th star and above, which give you a total of 7200 seconds (2 hours) of buff. NOTE: The able navigator skill currently has no effect on sextant buff duration, although it says it does. Be aware. How large are the grids? How large is the whole ATLAS map? Using the sextant buff's guidance marker feature and GPS coordinates, you can get very accurate information about the size of each grid. For example, the center of the center maw (where the Kraken spawns) is at the coordinates of 0/0 long/lat. Moving to the East increases longitude, whereas moving to the North increases latitude. NOTE: Most real-world coordinates are given in lat/long notation, but the game chooses to give the coordinates to you in long/lat notation, so try not to confuse the two. By using singleplayer to fly to the corner of a grid, then marking a waypoint at an adjacent corner and activating the guidance marker, you can get the following size for a grid 14,000 meters along a side, and 13 1/3 lat/long along a side. This means that the whole ATLAS map is 14 * 15 = 210 km in width and length, and the maximum lat/long coordinates are +/- 100. When would crossing the edges of the map make my trip faster? The right edge of the ATLAS map is connected to the left, and the top is connected to the bottom, just like in Pac-man. Curiously, this means that the ATLAS map is not on a sphere, like our Earth, but rather on the surface of a torus (a doughnut shape). Since there are a total of 15 grids in each direction, you could go 8 tiles in one direction, or 7 tiles in the other direction to get to the same grid. Therefore, you should never go more than 7 tiles E/W or N/S to get to your destination. If your route takes you on a path with more than 7 tiles in one direction (for example, West), just go in the opposite direction (East) and it will be shorter. Never go more than 7 tiles in one direction (E/W or N/S) to get to your destination. Go the opposite way, and you can get there in under 7 tiles. The furthest grid from you on the map is 7 tiles E/W and 7 tiles N/S away from you, for a total of 9.9 tiles to get to the opposite side of the map. How accurate are the numbers that the sextant buff gives you? To start, I will assume that the long/lat numbers are exact, since they are simply related to the in-game coordinate system that the game invariably uses. From these numbers, we will discuss the accuracy of the sextant buff speed and direction numbers, and any relevant conversion factors. First up: speed. In real life, a knot is defined as about 1.15 mph, or around 0.514 m/s. Using this number, and the fact that grids are 14 km in width, a ship going around 20 knots would take over 23 minutes to cross a grid. This isn't the case (you can traverse a grid much quicker), so the game must think that knots are something different. To test this, I started a brig off in a random direction at full speed, in singleplayer. Using singleplayer commands, I made the wind a constant speed and not rotate, and I sailed for about 1/2 of an in-game day, and computed the total long/lat distance traveled, compared to the speed shown in the sextant buff. I determined that 1 knot is equivalent to about 0.077 lat/long per in-game minute, or 0.347 grids/in-game hour. To convert in-game minutes to real-life minutes, you just have to divide by 2.1 (I got this number by timing with a stopwatch for about 10 minutes and figuring out how many in-game minutes passed by). Therefore, 1 ATLAS knot is about 38.56 meters/real-life second. Thus, a ship going at 20 knots can cross a grid in just over 6 minutes. Here are a few useful conversion factors: 1 ATLAS knot = 38.56 meters/real-life second = 0.0367 lat/long per real-life second = 0.165 grids/real-life second 1 in-game minute = 2.1 real-life seconds 1 lat/long = 1050 meters NOTE: The speeds given by the sextant buff depend on your current CPU usage. If your CPU spikes, the speed will dip. I tested this by changing the slomo setting - as time is slowed down, the sextant buff indicator sped up. This is because the slower time allowed the CPU to rest more and keep up with the speed calculations. Additionally, I ran the user benchmark cpu test while playing the game at normal settings and similarly saw a drop in the sextant buff reported speed. I found that, for my game under typical settings and activity, the speed can increase by about 1% by slowing the game down absurdly, and it can slow down significantly when speeding the game up. Just a heads up - the speed is not universal, and the same ship may report different speeds on different PCs, even with all variables taken care of. The second task: Direction indicator/heading. I first noticed that the direction indicator is off somewhat when I set my ship to head North (0 degrees) and found my longitude changing still. When I set the ship sailing in a direction that had no longitudinal changes (even over a very long period of time), the directional HUD said 1 degree. More of my testing included recording start and stop lat/long for my ship, and the direction of travel. I then computed the angle from the lat/long data, to compare to the given direction. I found that the direction is accurate to +/- 1 degree always. This can contribute to error when testing and trying to determine actual numbers for these things, but I doubt it will affect gameplay in any noticeable way. The biggest effect I could see this having is if you skirt along a grid border, you should look at the lat/long directly instead of the direction, since you could end up veering off course for long journeys. Conclusion: The sextant buff is a very useful buff, which is why I try to keep it on most of the time I play ATLAS. It helps plot a course on the sea, navigate a new island, or just stay oriented in your home base. Although the speed and direction have a few small accuracy issues, this shouldn't affect your gameplay at all unless you are crazy like me and want to dig up the numbers behind the game that make it all work. That's it for this guide, let me know in the comments if there are any other sextant-related topics you want me to cover, or if you want me to make a guide on another subject that interests you. See you on the high seas!
  11. Example: eco's RP Decor Server: RootServer/Windows ATLAS 18.XX Cannot lern Engram or Something Server overwrites mod data with incomplete version, 1631908356.mod file deletes every startup. FAQ from "Eco" don´t help me ...but... my solution work for me this time. 1.) Close Redis and Server! 2.) Copy Mod-Files from Client SERVERPATH\ShooterGame\Content\Mods \1643109631 \1643109631.mod Important: 1643109631.mod must be flag "read-only" in Properties of the File. 3.) ALTAS have AutoManageMod-System temporarily switched off! SERVERPATH\Engine\Binaries\ThirdParty\SteamCMD Rename "SteamCMD" Folder like "SteamCMD_" 4.) The MoD-ID [1631908356] write into your DefaultGameUserSettings.ini & ServerGrid.json SERVERPATH\ShooterGame\Config\DefaultGameUserSettings.ini [ServerSettings] ActiveMods=1631908356 ServerGrid.json ModIDs "1631908356" That it...
  12. If you ever wanted to switch your crew between cannons while you are sailing your ship. Well, it's possible but it's also not perfect. I made a guide on how to do this. Click on video to watch it. Video
  13. I'll preface this by saying that there's probably an easier way to do this, but this is what works for me. I'll be using my setup as an example, but this should work on any setup though the file paths may be different. What you'll need: Atlas (obviously, preferably on steam) Filezilla or your prefered ftp client Mod id's for the mods you want to use (these can be found on the steam mod page, in the browser address, it's all the #'s after id= ) FTP Host name, user name, password, and port for each server (on nitrado, these are found at the bottom left of each server's dashboard page) 1. Subscribe to the mods you'd like to use on steam. 2. Launch Atlas to force steam to download your selected mods. 3. Close Atlas. 4. Launch Filezilla. 5. In the appropriate fields enter the host name, user name, password, and port for your home server and hit enter. 6. On the left side, navigate to your desktop (c:\users\desktop) 7. On the right side navigate to atlasmain\shootergame\saved\savegame*\config\WindowsServer (*the savegame folder will have a long string of numbers\letters for a name, if there's more than one, use the one with the most recent time stamp) 8. Drag the GameUserSettings.ini file over to the desktop folder on the left. 9. Open the GameUserSettings.ini file you just downloaded with a text editor (notepad, etc.). 10. At the bottom of the server settings section (the first section, before [/Script/ShooterGame.ShooterGameUserSettings]) add ActiveMods= followed by your mod id's separated by a comma (for example ActiveMods=1629667379,1629097213,1628157075,1635287345,1633503401) in the order you want them to be loaded. 11. Save and close GameUserSettings.ini 12. Copy GameUserSettings.ini back to your server. 13. On the left side navigate to your atlas content folder (c:\program files x86\steam\steamapps\common\atlas\shootergame\content 14. On the right side navigate to atlasmain\shootergame\content (you will need to create the content folder if it isn't there already). 15. Drag the mods folder from the content folder on the left to the one on the right and wait until filezilla tells you that the transfer is complete. 16. Repeat 12-15 for each of your expansion servers using their hostname, user name, password, and port (each one is different on nitrado), on expansion servers the filepath will start in atlasexp instead of atlasmain but is otherwise the same. 17. Once you've completed uploading the files, close filezilla, restart your cluster, log in, and enjoy modded goodness =D
  14. We have added some guides on the creation of armor and skins. you can find them at the link below, as well as a guide on colorization on the site. All the source art you need should be available from the source art download. And the Clothing Wizard can be found in the AtlasDevkitContent tool repo on the grapeshot github. (links are on the devkit site) If anyone finds there is something missing that they need, let me know. https://devkit.playatlas.com/en/latest/Guides/Armor.html
  15. I had quite the adventure last night trying to get the ship out of the barrier between servers. After much troubleshooting, my partner and I discovered a method to debug the ship and free it from the void of Davy Jones Locker. Expect some time travel. I'll outline the steps below and some unexpected outcomes. 1 - You've been force logged out by the server with a timeout error message stating you are traveling between servers log in later. You're friends or self are cursing the game and telling you to get the ship back. Fear not! With this guide, you too, can be the hero. When you log back into the game, notate the zone it's trying to load you into. It will either be the server you came from or were going to. Remember this server. Step 1 - Try to log into a new Atlas - Same Server - Freeport Result - It fails to load you into the freeport but allows you to select a bed to spawn in. Step 2 - I know you wanna click on that bed for the ship you were stuck on.. you can if you choose, but you may need to repeat this step later once you realize you just keep getting kicked. Click on your home base or nearest ship. Result - This can be tricky as it sometimes forces you to continue to spawn at the stuck ship. Step 2b - If you are having trouble spawning at base or another ship, log out. This puts you into a sleep state in game. Step 3 - Once you've spawned at home or another ship it's time to make that journey to the zone mentioned above. The one that the game tries to load you into. That's where your ship is actually at. Our objective is to make the ship render. Once you approach the ship and it's name appears or it renders, relay that information to your Company. Result - The ship is no longer stuck and your company can spawn on it and continue the journey. Step 4 - Time travel. IF you choose to fast travel to the ship you may actually spawn in with your inventory and armor that you had at the time of getting kicked. Immediately! put all your gear into a chest. If you are going to change servers on your trip again you will be teleported back to your base with nothing. This is important! In closing, I hope this helps!
  16. Hey this is going to be a short and sweet guide for how to stream Atlas with only 1 PC. I use 2 monitors and for some reason every time I used StreamLabs OBS I would get horrible stream FPS drop. No matter what setting I tried it would not work. What finally did work however, is plugging my second monitor into the motherboard port and updating my Intel drivers...after you do that, try to use game capture to stream. You should notice markedly better stream fps...I was sitting at 4-22 prior to doing this, and after I'm sitting at 50+ at all times, with everything in Atlas maxed (in game FPS is 40-80 at all times. Mind you, I am using an I9990K with RTX2080, however...this fix should work for all of you trying to stream without a second PC and capture card...maybe not at all max graphical settings...but it will WORK. I want to thank ghosteez from Stream Labs for working together with me to find this fix out. I love Atlas, and Stream Labs...and am happy to finally be able to stream this game without much of a problem. I did order a capture card to set up in my old PC, which I will use once I have it instead of this fix/workaround...but for those who cannot afford two pcs let alone a capture card, this is a very viable alternative.
  17. If you want to fine tune harvesting so elephants don't lag your entire server when they harvest 18k berrys when you just want some wood. Codes to implement fine turning of materials. I strongly recommend you only put the resources you specifically want to have extra for and set your base harvest rate to x1. Base Harvest rate will multiply the specific harvest rate so be warned you could make things worse. These changes go in your defaultgame.ini file. Remember to always backup your files before making any changes. https://github.com/Karageek/AtlasHarvestResourceList Update these must go in your game.ini for each shard. This changed when they changed the default from x1 to x2 base not sure why it broke it in defaultgame but now u have to put each in each game.ini for each shard. some reason this forum is not sending me notifys when ppl reply, sorry about that. Multiple Minor changes Update 2: Added Primefish Update 3: Fixed missing _Vegetable for some items Update 4: Fixed typo in Coral Update 5: Changed all amounts to vanilla 1.000000
  18. First off I did not make these videos but after getting help from the creator on his quick 1x1 guide he made these videos. If you have having trouble with anything concerning dedicated server creation I highly suggest starting fresh with these guides. Just select from the playlist which you need help with if you are confident you know the basics. if not start with the quick 1x1. https://www.youtube.com/playlist?list=PL0TwOxC8-YOivCyubY0mhOQIr8ErGh4WP
  19. I thought I would make a list of things to check if you are having issues with server setup. These are mostly issues I ran into myself setting up the "Utopia EU" server. - Use a dedicated server with enough spec to support your entire map and player count. If you require a much larger map, this is not for you. - Check ports match up with your "start.bat" which you use to launch your server. - In the start.bat, make sure you use a unique identifier for "AltSaveDirectoryName=" Eg "AltSaveDirectoryName=A1" "AltSaveDirectoryName=A2" "AltSaveDirectoryName=B1". - If your having red wall issues, try using different port numbers and test one by one. Make sure to add new ports to firewall and "start.bat". - Try to keep everything in order. - Check you have entered the correct IP everywhere you entered an IP (I made this mistake, once.). - Simplify your server startup by making one start.bat. Use "timeout /t 30" to space out the time between each tile boot. - Server may not boot due to missing audio files "X3DAudio1_7.dll" and "XAPOFX1_5.dll". Don't worry, just download them and place them in "C:\atlasserver\ShooterGame\Binaries\Win64", fx. - Remember to start redis first. - You can clear the redis database using "C:\atlasserver\AtlasTools\RedisDatabase\clearall_127.0.0.1 - If you would like to restart your map and remove all char stats/buildings/claims, delete the contents of C:\atlasserver\ShooterGame\Saved - To become admin, enter this line into your start.bat "ServerAdminPassword=YOURPASSWORD?". - A list of admin commands "https://streamline-servers.com/billing/knowledgebase/4250/Atlas-Admin-Commands.html" Have your own suggestion? Leave a comment bellow and I will add to the list.
  20. For all the map creators/designers. This spreadsheet identifies Freeport, and Powerstone Locations and the type of template they are using. (Tropical, Equitorial, Tundra etc.) https://docs.google.com/spreadsheets/d/1IchDv2boXfQqP1JAKOBye1e6xHwgzEotqSm9aLvZ_zQ/edit?usp=sharing War And Peace, UnknownSoldier
  • Create New...