POLPOX/Sandbox2 – User

From Bohemia Interactive Community
Jump to navigation Jump to search
(Made it a Steam page)
No edit summary
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{TOC|side}}
So uh. This is rough idea so far - feel free to give any idea
{{Link|https://store.steampowered.com/|Steam}} is a video game distribution platform that hosts, sometimes exclusively, {{GameCategory|bi|link= y}} games such as {{arma3}}, {{tkoh}} and {{armaR}}.
{{Feature|informative|See {{Wikipedia|Steam (service)}}.}}


== Arma 3: Scripts, Configs and Addons walkthrough ==
=== Overall idea ===
Give a newcommer some idea of how these works. Not a document, but a tutorial. A walkthrough even.<br>
(Note: ''document'' here is ''telling technical terms, techs etc'', and ''walkthrough'' here is ''you just want a bit of progress eh? do this, I'll explain later how it works, just try this for now''. Like PMCwiki's terrain tutorial)
=== Why? ===
I always feel '''make an achievement/progress is much much important''' before knowing anything, knowing what is a [[Boolean]]. There are a LOT of tutorials without some walkthrough guides (including BIKI even [[Introduction to Arma Scripting]]). Which can make people confused very easily.<br>
Nobody is going to hop into SQF after how an [[Array]] works. They just wanted to know how to do something beforehands.<br>
We also need to teach and make the newcommer at least a little bit mature. I'm not after a shitty tutorials like mobile games often do, but ''teach''.<br>
<br>
I just don't want people overwhelmed by telling a LOT of terms and unknown things at once.
=== How it works ===
# '''Do this''' (Please do this without doubt. So you'll achieve a Hello World)
# '''Teach terms and things you need to know''' (Init can run a SQF script. This is where you start your SQF - put a code and it will run)
# '''Explain''' ([[hint]] is a command to show a hint message on the screen)
=== What kind of things can be listed? ===
* '''Introduce into SQF'''
** What it can do?
* '''Hello World'''
** Run a very basic command. Now you made your first script
* '''Do some obvious trick'''
** setPos etc to make a visually-obvious changes into the mission


== Available {{Name|bi}} Games ==
* '''Make a new music'''
** Introduce into config through [[Description.ext]]


{{Columns|3|
* '''Make a difference'''
* {{GameCategory|ofp|link= y}}
** Making a PBO with a very basic config, like, just one ''displayName'' update etc
* {{GameCategory|arma1|link= y}}
etc
* {{GameCategory|arma2|link= y}}
=== Expected audiences ===
* {{GameCategory|arma2oa|link= y}}
* people who doesn't really know how a programming would work even
* {{GameCategory|arma3|link= y}}
* people who doesn't have a ''better'' text editor even
* {{GameCategory|armaR|link= y}}
* people who doesn't have an experience with scripting or configuring
* {{GameCategory|dayz|link= y}}
* {{GameCategory|ylands|link= y}}
* {{GameCategory|tkoh|link= y}}
* {{GameCategory|tkom|link= y}}
* {{GameCategory|carriercommand|link= y}}
}}
 
 
== Assistance ==
 
=== Verify Game Files ===
 
In the event of a game issue, it is sometimes recommended to make Steam verify the game files:
* right-click on the game in the Steam list
* select "Properties"
* click on "Local Files"
* press "Verify integrity of game files"
Steam will now verify and repair modified files. This will not erase any personal files; game progress, controls and other configurations will remain unchanged.
 
{{Feature|informative|See {{Link|https://help.steampowered.com/en/faqs/view/0C48-FCBD-DA71-93EB|Steam's tutorial}}.}}
 
=== Move {{arma3}} Workshop Items ===
 
A {{Wikipedia|Symbolic link}} (also known as Symlink) can make this happen, making Windows believe a directory is actually in another location.
 
# Locate the Workshop directory, in which the {{hl|107410}} directory (which has the entire {{arma3}} related Workshop items) is present.<!--
-->{{Feature|informative|Usually {{hl|C:\Program Files (x86)\Steam\steamapps\workshop\content}} or if SteamLibrary is installed on another drive (e.g {{hl|D:}}), {{hl|D:\SteamLibrary\steamapps\workshop\content}}.}}
# '''Copy''' the {{hl|107410}} directory to its new location (e.g {{hl|E:\NewArma3WorkshopDirectory}})
# Rename the {{hl|<workshop directory>\107410}} source directory to make a backup and ensure it is not used accidentally(e.g {{hl|107410_backup}})
# Open Command Prompt in Administrator mode (Windows Search > type "cmd", right-click > "Run as Administrator")
# Enter this command: <code>mklink /d ''target'' ''source''</code>, where:
#* ''target'' is the original {{hl|107410}} location, e.g {{hl|C:\Program Files (x86)\Steam\steamapps\workshop\content\107410}}
#* ''source'' is the actual data directory, e.g {{hl|E:\NewArma3WorkshopDirectory}}
# Press {{Controls|Enter}} to run the command, here <code>mklink /d "C:\Program Files (x86)\Steam\steamapps\workshop\content\107410" "E:\NewArma3WorkshopDirectory"</code>
# This is it! There is nothing else to configure and nothing to change Launcher-wise. Start the game to make sure it recognizes the items properly.
# If everything went well, the backup can be safely deleted ({{hl|C:\Program Files (x86)\Steam\steamapps\workshop\content\107410_backup}}).
 
{{Feature|informative|
To delete a symbolic link, simply delete the ''target'' directory from Windows Explorer (here {{hl|C:\Program Files (x86)\Steam\steamapps\workshop\content\107410}} > right-click > delete).<br>
See also {{Link|https://www.howtogeek.com/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/|How-To Geek tutorial}}.
}}

Latest revision as of 10:55, 4 October 2024

So uh. This is rough idea so far - feel free to give any idea

Arma 3: Scripts, Configs and Addons walkthrough

Overall idea

Give a newcommer some idea of how these works. Not a document, but a tutorial. A walkthrough even.
(Note: document here is telling technical terms, techs etc, and walkthrough here is you just want a bit of progress eh? do this, I'll explain later how it works, just try this for now. Like PMCwiki's terrain tutorial)

Why?

I always feel make an achievement/progress is much much important before knowing anything, knowing what is a Boolean. There are a LOT of tutorials without some walkthrough guides (including BIKI even Introduction to Arma Scripting). Which can make people confused very easily.
Nobody is going to hop into SQF after how an Array works. They just wanted to know how to do something beforehands.
We also need to teach and make the newcommer at least a little bit mature. I'm not after a shitty tutorials like mobile games often do, but teach.

I just don't want people overwhelmed by telling a LOT of terms and unknown things at once.

How it works

  1. Do this (Please do this without doubt. So you'll achieve a Hello World)
  2. Teach terms and things you need to know (Init can run a SQF script. This is where you start your SQF - put a code and it will run)
  3. Explain (hint is a command to show a hint message on the screen)

What kind of things can be listed?

  • Introduce into SQF
    • What it can do?
  • Hello World
    • Run a very basic command. Now you made your first script
  • Do some obvious trick
    • setPos etc to make a visually-obvious changes into the mission
  • Make a difference
    • Making a PBO with a very basic config, like, just one displayName update etc

etc

Expected audiences

  • people who doesn't really know how a programming would work even
  • people who doesn't have a better text editor even
  • people who doesn't have an experience with scripting or configuring