Commands hu HU

Parancsok

Az ASF számos parancsot támogat, amivel a program és a botok viselkedését lehet befolyásolni.

A parancsokat számos módon lehet elküldeni a bot számára:

• Az interaktív ASF konzolon keresztül
• Privát, vagy csoportos Steam chaten keresztül
• Az IPC interfészünkön keresztül

Tartsd észben, hogy az ASF interakciókhoz szükséges, hogy legyen megfelelő hozzáférésed a parancshoz az ASF engedélyek alapján. Nézd meg a SteamUserPermissions és a SteamOwnerID konfigurációs beállításokat, ha többet szeretnél erről tudni.

A Steam chaten keresztül kiadott parancsokra befolyással van a CommandPrefix globális konfigurációs beállítás, ami alapértelmezetten a ! karakter. Ez azt jelenti, hogy például a status parancs kiadásához azt kell beírnod, hogy !status (vagy a CommandPrefix által meghatározott karakter(eke)t). A CommandPrefix használata nem kötelező konzol, vagy IPC esetén, ki lehet hagyni.

---

Interaktív konzol

A V4.0.0.9-es verziótól kezdődően az ASF támogatja az interakítv konzolt, amit a SteamOwnerID beállításával lehet engedélyezni. Utána egyszerűen a c gomb megnyomásával engedélyezni lehet a parancs módot, beírhatod a parancsot és enterrel el lehet azt küldeni.

Az interaktív konzol nem elérhető a Headless módban.

---

Steam chat

A Steam chaten keresztül is futtathatsz parancsokat egy ASF bot számára. Természetesen önmagaddal nem beszélgethetsz, ezért szükséged lesz minimum egy másik bot accountra, ha a fő accountodra szeretnél parancsokat kiadni.

Ugyanígy egy Steam csoport csoportos chatjét is használhatod. Tudd, hogy ha ezt szeretnéd használni, akkor a SteamMasterClanID-t be kell állítani, így a bot a csoport chatjén is figyelni fogja a kiadott parancsokat (és be fog lépni, ha szükséges). Ezt arra is fel tudod használni, hogy "magaddal beszélgess", mivel így nincs szükség egy külön bot accountra a privát chattel ellentétben. Egyszerűen be tudod állítani a SteamMasterClanID-t az újonnan létrehozott csoportodra, majd hozzáférést adhatsz magadnak vagy a SteamOwnerID, vagy a SteamUserPermissions használatával a botodon keresztül. Így az ASF bot (te) be fog lépni a csoportba, majd a csoport chatjébe, ahol is várni fogja az általad kiadott parancsokat. Ezután beléphetsz ugyanabba a csoportos chat szobába, hogy magadnak adj ki parancsokat (mivel a parancsokat a chat szobában fogod kiadni és az ASF példány ugyanabban a chat szobában fogja fogadni őket, még akkor is ha csak a te accountod van ott).

A csoportos chat számára kiadott parancsokat mindenki megkapja. Ha azt írtod be, hogy redeem X és 3 botod van a chat szobában, akkor az olyan lesz, mintha mind a háromnak kiadnád a redeem X parancsot külön-külön. A legtöbb esetben nem ezt szeretnéd, ezért a given bot parancsot használd, ami csak egy bot számára lesz elküldve privát ablakban. Az ASF ugyan támogatja a csoportos chateket, mivel számos esetben hasznos lehet, ha az egyetlen bot példányoddal szeretnél kommunikálni, de szinte sosem ajánlott egy parancs kiadása, ha a csoportos chatben 2 vagy több ASF bot van egyszerre, kivéve, ha tisztában vagy az ASF viselkedésével és valóban szeretnéd ugyanazt a parancsot kiadni az összes bot számára.

And even in this case you should use private chat with [Bots] syntax instead.

---

IPC

A legfejlettebb és legrugalmasabb módja a parancsok kiadásának, tökéletes a felhasználói interakciókhoz (ASF-ui), valamint a harmadik féltől származó programokhoz, vagy szkriptekhez (ASF API), használatához az ASF-t IPC módban kell futtatni, valamint a kliensnek az IPC interfészen keresztül kell parancsot kiadnia.

---

Parancsok

Parancs	Hozzáférés	Leírás
2fa [Bots]	Master	Ideiglenes 2FA tokent generál a megadott bot példányokhoz.
2fano [Bots]	Master	Megtagadja az összes 2FA megerősítést a megadott példányoktól.
2faok [Bots]	Master	Elfogadja az összes 2FA megerősítést a megadott bot példányoknak.
addlicense [Bots] <Licenses>	Operator	Activates given licenses, explained below, on given bot instances (free games only).
balance [Bots]	Master	Visszaadja a megadott bot példányok pénztárca egyenlegét.
bgr [Bots]	Master	Információt ad a BGR várólistáról a megadott botok számára.
encrypt <encryptionMethod> <stringToEncrypt>	Owner	Encrypts the string using provided cryptographic method - further explained below.
exit	Owner	Leállítja a teljes ASF processzt.
farm [Bots]	Master	Újraindítja a kártya farmoló modult a megadott bot példányokon.
fb [Bots]	Master	Lists apps blacklisted from automatic farming of given bot instances.
fbadd [Bots] <AppIDs>	Master	Adds given appIDs to apps blacklisted from automatic farming of given bot instances.
fbrm [Bots] <AppIDs>	Master	Removes given appIDs from apps blacklisted from automatic farming of given bot instances.
fq [Bots]	Master	Lists priority farming queue of given bot instances.
fqadd [Bots] <AppIDs>	Master	Adds given appIDs to priority farming queue of given bot instances.
fqrm [Bots] <AppIDs>	Master	Removes given appIDs from farming queue of given bot instances.
hash <hashingMethod> <stringToHash>	Owner	Generated a hash of the string using provided cryptographic method - further explained below.
help	FamilySharing	Megmutatja a súgót (egy linket erre az oldalra).
input [Bots] <Type> <Value>	Master	Megadott input típust beállítja a megadott értékre a megadott bot példányok számára, kizárólag a Headless módban működik - lentebb jobban el van magyarázva.
level [Bots]	Master	Shows Steam account level of given bot instances.
loot [Bots]	Master	Sends all LootableTypes Steam community items of given bot instances to Master user defined in their SteamUserPermissions (with lowest steamID if more than one).
loot@ [Bots] <AppIDs>	Master	Sends all LootableTypes Steam community items matching given AppIDs of given bot instances to Master user defined in their SteamUserPermissions (with lowest steamID if more than one). This is the opposite of loot%.
loot% [Bots] <AppIDs>	Master	Sends all LootableTypes Steam community items apart from given AppIDs of given bot instances to Master user defined in their SteamUserPermissions (with lowest steamID if more than one). This is the opposite of loot@.
loot^ [Bots] <AppID> <ContextID>	Master	Sends all Steam items from given AppID in ContextID of given bot instances to Master user defined in their SteamUserPermissions (with lowest steamID if more than one).
mab [Bots]	Master	Lists apps blacklisted from automatic trading in MatchActively.
mabadd [Bots] <AppIDs>	Master	Adds given appIDs to apps blacklisted from automatic trading in MatchActively.
mabrm [Bots] <AppIDs>	Master	Removes given appIDs from apps blacklisted from automatic trading in MatchActively.
nickname [Bots] <Nickname>	Master	Changes Steam nickname of given bot instances to given nickname.
owns [Bots] <Games>	Operator	Checks if given bot instances already own given games, explained below.
pause [Bots]	Operator	Permanently pauses automatic cards farming module of given bot instances. ASF will not attempt to farm current account in this session, unless you manually resume it, or restart the process.
pause~ [Bots]	FamilySharing	Temporarily pauses automatic cards farming module of given bot instances. Farming will be automatically resumed on the next playing event, or bot disconnect. You can resume farming to unpause it.
pause& [Bots] <Seconds>	Operator	Temporarily pauses automatic cards farming module of given bot instances for given amount of seconds. After delay, cards farming module is automatically resumed.
play [Bots] <AppIDs,GameName>	Master	Switches to manual farming - launches given AppIDs on given bot instances, optionally also with custom GameName. In order for this feature to work properly, your Steam account must own a valid license to all the AppIDs that you specify here, this includes F2P games as well. Use reset or resume for returning.
points [Bots]	Master	Displays number of points in Steam store.
privacy [Bots] <Settings>	Master	Changes Steam privacy settings of given bot instances, to appropriately selected options explained below.
redeem [Bots] <Keys>	Operator	Redeems given cd-keys or wallet codes on given bot instances.
redeem^ [Bots] <Modes> <Keys>	Operator	Redeems given cd-keys or wallet codes on given bot instances, using given modes explained below.
reset [Bots]	Master	Resets the playing status back to original (previous) state, the command is used during manual farming with play command.
restart	Owner	Restarts ASF process.
resume [Bots]	FamilySharing	Resumes automatic farming of given bot instances.
start [Bots]	Master	Starts given bot instances.
stats	Owner	Prints process statistics, such as managed memory usage.
status [Bots]	FamilySharing	Prints status of given bot instances.
std	Owner	Special command for SteamTokenDumperPlugin which triggers submission of data immediately.
stop [Bots]	Master	Stops given bot instances.
tb [Bots]	Master	Listázza a tiltólistán lévő felhasználókat, melyek így nem tudnak csereajánlást küldeni a megadott bot példányok számára.
tbadd [Bots] <SteamIDs64>	Master	Tiltólistára rakja a megadott steamIDs-t, így a megadott bot példányoknak nem tud csereajánlatot küldeni.
tbrm [Bots] <SteamIDs64>	Master	A megadott steamIDs-t törli a tiltólistáról, így azok tudnak csereajánlást küldeni a megadott bot példányok számára.
transfer [Bots] <TargetBot>	Master	Sends all TransferableTypes Steam community items from given bot instances to target bot instance.
transfer@ [Bots] <AppIDs> <TargetBot>	Master	Sends all TransferableTypes Steam community items matching given AppIDs from given bot instances to target bot instance. This is the opposite of transfer%.
transfer% [Bots] <AppIDs> <TargetBot>	Master	Sends all TransferableTypes Steam community items apart from given AppIDs from given bot instances to target bot instance. This is the opposite of transfer@.
transfer^ [Bots] <AppID> <ContextID> <TargetBot>	Master	Sends all Steam items from given AppID in ContextID of given bot instances to target bot instance.
unpack [Bots]	Master	Unpacks all booster packs stored in the inventory of given bot instances.
update	Owner	Checks GitHub for ASF updates (this is done automatically every UpdatePeriod).
version	FamilySharing	Prints version of ASF.

---

Megjegyzések

All commands are case-insensitive, but their arguments (such as bot names) are usually case-sensitive.

[Bots] argument is optional in all commands. When specified, command is executed on given bots. When omitted, command is executed on current bot that receives the command. In other words, status A sent to bot B is the same as sending status to bot A, bot B in this case acts only as a proxy. This can also be used for sending commands to bots that are unavailable otherwise, for example starting stopped bots, or executing actions on your main account (that you're using for executing the commands).

Access of the command defines minimum EPermission of SteamUserPermissions that is required to use the command, with an exception of Owner which is SteamOwnerID defined in global configuration file (and highest permission available).

Plural arguments, such as [Bots], <Keys> or <AppIDs> mean that command supports multiple arguments of given type, separated by a comma. For example, status [Bots] can be used as status MyBot,MyOtherBot,Primary. This will cause given command to be executed on all target bots in the same way as you'd send status to each bot in a separate chat window. Please note that there is no space after ,.

ASF uses all whitespace characters as possible delimiters for a command, such as space and newline characters. This means that you don't have to use space for delimiting your arguments, you can as well use any other whitespace character (such as tab or new line).

ASF will "join" extra out-of-range arguments to plural type of the last in-range argument. This means that redeem bot key1 key2 key3 for redeem [Bots] <Keys> will work exactly the same as redeem bot key1,key2,key3. Together with accepting newline as command delimiter, this makes it possible for you to write redeem bot then paste a list of keys separated by any acceptable delimiter character (such as newline), or standard , ASF delimiter. Keep in mind that this trick can be used only for command variant that uses the most amount of arguments (so specifying [Bots] is mandatory in this case).

As you've read above, a space character is being used as a delimiter for a command, therefore it can't be used in arguments. However, also as stated above, ASF can join out-of-range arguments, which means that you're actually able to use a space character in argument that is defined as a last one for given command. For example, nickname bob Great Bob will properly set nickname of bob bot to "Great Bob". In the similar way you can check names containing spaces in owns command.

---

Néhány parancsot alternatív módon is meg lehet adni, így nem kell annyit gépelned:

Parancs	Alternatív parancs
owns ASF	oa
status ASF	sa
redeem	r
redeem^	r^

---

[Bots] argument

[Bots] argument is a special variant of plural argument, as in addition to accepting multiple values it also offers extra functionality.

First and foremost, there is a special ASF keyword which acts as "all bots in the process", so status ASF command is equal to status all,your,bots,listed,here. This can also be used to easily identify the bots that you have access to, as ASF keyword, despite of targeting all bots, will result in response only from those bots that you can actually send the command to.

[Bots] argument supports special "range" syntax, which allows you to choose a range of bots more easily. The general syntax for [Bots] in this case is firstBot..lastBot. For example, if you have bots named A, B, C, D, E, F, you can execute status B..E, which is equal to status B,C,D,E in this case. When using this syntax, ASF will use alphabetical sorting in order to determine which bots are in your specified range. Both firstBot and lastBot must be valid bot names recognized by ASF, otherwise range syntax is entirely skipped.

In addition to range syntax above, [Bots] argument also supports regex matching. You can activate regex pattern by using r!<pattern> as a bot name, where r! is ASF activator for regex matching, and <pattern> is your regex pattern. An example of a regex-based bot command would be status r!\d{3} which will send status command to bots that have a name made out of 3 digits (e.g. 123 and 981). Feel free to take a look at the docs for further explanation and more examples of available regex patterns.

---

privacy beállítások

A <Settings> argumentum akár 7 különböző opciót is elfogad, a szokásos ASF elválasztóval, a vesszővel, elválasztva egymástól. Ez sorrendben a következők:

Argumentum	Név	Gyermeke
1	Profile
2	OwnedGames	Profile
3	Playtime	OwnedGames
4	FriendsList	Profile
5	Inventory	Profile
6	InventoryGifts	Inventory
7	Comments	Profile

Ha szeretnél egy leírást a fentebbi mezőkről, akkor kérlek látogasd meg a Steam privacy beállításokat.

A következő értékeket vehetik fel:

Érték	Név
1	Private
2	FriendsOnly
3	Public

You can use either a case-insensitive name, or a numeric value. Arguments that were omitted will default to being set to Private. It's important to note relation between child and parent of arguments specified above, as child can never have more open permission than its parent. For example, you can't have Public games owned while having Private profile.

Példa

If you want to set all privacy settings of your bot named Main to Private, you can use either of below:

privacy Main 1
privacy Main Private

This is because ASF will automatically assume all other settings to be Private, so there is no need to input them. On the other hand, if you'd like to set all privacy settings to Public, then you should use any of below:

privacy Main 3,3,3,3,3,3,3
privacy Main Public,Public,Public,Public,Public,Public,Public

This way you can also set independent options however you like:

privacy Main Public,FriendsOnly,Private,Public,Public,Private,Public

The above will set profile to public, owned games to friends only, playtime to private, friends list to public, inventory to public, inventory gifts to private and profile comments to public. You can achieve the same with numeric values if you want to.

Remember that child can never have more open permission than its parent. Refer to arguments relationship for available options.

---

addlicense licenses

addlicense command supports two different license types, those are:

Típus	Alternatív parancs	Példa	Leírás
app	a	app/292030	Game determined by its unique appID.
sub	s	sub/47807	Package containing one or more games, determined by its unique subID.

The distinction is important, as ASF will use Steam network activation for apps, and Steam store activation for packages. Those two are not compatible with each other, typically you'll use apps for free weekends and permanently F2P games, and packages otherwise.

We recommend to explicitly define the type of each entry in order to avoid ambiguous results, but for the backwards compatibility, if you supply invalid type or omit it entirely, ASF will assume that you ask for sub in this case. You can also query one or more of the licenses at the same time, using standard ASF , delimiter.

Complete command example:

addlicense ASF app/292030,sub/47807

---

owns games

owns command supports several different game types for <games> argument that can be used, those are:

Típus	Alternatív parancs	Példa	Leírás
app	a	app/292030	Game determined by its unique appID.
sub	s	sub/47807	Package containing one or more games, determined by its unique subID.
regex	r	regex/^\d{4}:	Regex applying to the game's name, case-sensitive. See the docs for complete syntax and more examples.
név	n	name/Witcher	Part of the game's name, case-insensitive.

We recommend to explicitly define the type of each entry in order to avoid ambiguous results, but for the backwards compatibility, if you supply invalid type or omit it entirely, ASF will assume that you ask for app if your input is a number, and name otherwise. You can also query one or more of the games at the same time, using standard ASF , delimiter.

Complete command example:

owns ASF app/292030,name/Witcher

---

redeem^ módok

redeem^ command allows you to fine-tune modes that will be used for one single redeem scenario. This works as temporary override of RedeemingPreferences bot config property.

<Modes> argument accepts multiple mode values, separated as usual by a comma. Available mode values are specified below:

Érték	Név	Leírás
FAWK	ForceAssumeWalletKey	Forces AssumeWalletKeyOnBadActivationCode redeeming preference to be enabled
FD	ForceDistributing	Forces Distributing redeeming preference to be enabled
FF	ForceForwarding	Forces Forwarding redeeming preference to be enabled
FKMG	ForceKeepMissingGames	Forces KeepMissingGames redeeming preference to be enabled
SAWK	SkipAssumeWalletKey	Forces AssumeWalletKeyOnBadActivationCode redeeming preference to be disabled
SD	SkipDistributing	Forces Distributing redeeming preference to be disabled
SF	SkipForwarding	Forces Forwarding redeeming preference to be disabled
SI	SkipInitial	Skips key redemption on initial bot
SKMG	SkipKeepMissingGames	Forces KeepMissingGames redeeming preference to be disabled
V	Validate	Validates keys for proper format and automatically skips invalid ones

For example, we'd like to redeem 3 keys on any of our bots that don't own games yet, but not our primary bot. For achieving that we can use:

redeem^ primary FF,SI key1,key2,key3

It's important to note that advanced redeem overrides only those RedeemingPreferences that you specify in the command. For example, if you've enabled Distributing in your RedeemingPreferences then there will be no difference whether you use FD mode or not, because distributing will be already active regardless, due to RedeemingPreferences that you use. This is why each forcibly enabled override also has a forcibly disabled one, you can decide yourself if you prefer to override disabled with enabled, or vice versa.

---

encrypt command

encrypt command allows you to encrypt arbitrary strings using ASF's encryption methods. <encryptionMethod> must be one of the encryption methods specified and explained in security section. We recommend to use this command through secure channels (ASF console or IPC interface, which also has a dedicated API endpoint for it), as otherwise sensitive details might get logged by various third-parties (such as chat messages being logged by Steam servers).

---

hash command

hash command allows you to generate hashes of arbitrary strings using ASF's hashing methods. <hashingMethod> must be one of the hashing methods specified and explained in security section. We recommend to use this command through secure channels (ASF console or IPC interface, which also has a dedicated API endpoint for it), as otherwise sensitive details might get logged by various third-parties (such as chat messages being logged by Steam servers).

---

input parancs

input command can be used only in Headless mode, for inputting given data via IPC or Steam chat when ASF is running without support for user interaction.

General syntax is input [Bots] <Type> <Value>.

A <Type> kis- és nagybetű érzékeny és meghatározza az input típust, amit az ASF felismer. Jelenleg az ASF az alábbi típusokat ismeri:

Típus	Leírás
Login	SteamLogin bot konfigurációs beállítás, ha hiányozna a konfigurációból.
Password	SteamPassword bot konfigurációs beállítás, ha hiányozna a konfigurációból.
SteamGuard	Engedélyező kód, amit az e-mail címedre küldenek, ha nem használsz 2FA-t.
SteamParentalCode	SteamParentalCode bot konfigurációs beállítás, ha hiányozna a konfigurációból.
TwoFactorAuthentication	2FA token, amit a telefonod generált, ha használod a 2FA-t, de nem az ASF 2FA-t.

A <Value> a megadott típushoz lesz beállítva. Jelenleg minden érték string.

Példa

Mondjuk, hogy van egy botunk, ami SteamGuarddal van védve, de nem 2FA módban. We want to launch that bot with Headless set to true.

Ehhez az alábbi parancsokat kell kiadnunk:

start MySteamGuardBot -> Bot will attempt to log in, fail due to AuthCode needed, then stop due to running in Headless mode. Erre azért van szükség, mert a Steam hálózat el fogja küldeni az engedélyező kódot az e-mailünkre - ha nem lenne erre szükség, akkor átugorhatnánk ezt a részt.

input MySteamGuardBot SteamGuard ABCDE -> We set SteamGuard input of MySteamGuardBot bot to ABCDE. Természetesen az ABCDE-t helyettesítsd be azzal az engedélyező kóddal, amit az e-mailben kaptál.

start MySteamGuardBot -> We start our (stopped) bot again, this time it automatically uses auth code that we set in previous command, properly logging in, then clearing it.

Ehhez hasonlóan hozzáférhetünk a 2FA által védett botokhoz is (ha nem használják az ASF 2FA-t), valamint a többi szükséges beállítást is beállíthatjuk futásidőben.