[b]NOTE:[/b] Unlike [apitype]ISteamInput::EInputActionOrigin[/apitype], which updates with Steam and may return unrecognized values, [apitype]ISteamInput::ESteamInputType[/apitype] will remain static and only return valid values from your SDK version. [b]Returns:[/b] [apitype]ISteamInput::ESteamInputType[/apitype] [b]Example:[/b] [code=cpp] ESteamInputType inputType = SteamInput()->GetInputTypeForHandle(controller1Handle); switch(inputType) { case k_ESteamInputType_Unknown: printf("unknown!…

In the case of "HandHeld" devices with integrated screens like the SteamDeck ([i]k_ESteamInputType_SteamDeckController[/i]) and Lenovo Legion Go ([i]k_ESteamInputType_SteamOSHandheld[/i]), users will typically rotate the controller up by ~90 degrees in order to point the screen toward their eyes. …

[/list][section]Installation/use of SteamVR in an environment without internet access[/section] Many enterprise or government users are unable to use the Steam client to access the SteamVR Runtime, particularly due to restricted internet access behind corporate firewalls or on PCs without any internet connection. In order to address this issue you can download one initial copy of the SteamVR Runtime onto a PC with full internet access and then copy it manually onto the target PC(s). …

Copy this entire directory onto a portable medium of your choice (e.g. a USB thumb drive) and copy it again onto the target PC that does not have access to the internet. [*]In order to run SteamVR you should start the file "vrstartup.exe" [*]SteamVR should now be running on the new PC and support any application that is built using the OpenVR SDK, the SteamVR Unity Plugin or the VR tools within Unreal Engine. …

[subsection]Enabling a separate store page on a released demo[/subsection] If your demo is already live and you choose to enable the separate store page for it, you'll find there are a few additional required fields that you weren't required to fill out in order to set your demo live initially. Once you select the box to enable your store page and hit save, you'll find that the store checklist has reappeared on your demo landing page and notes any missing content. …

[section]Testing your demo[/section] To work properly for customers, your application type must be set as 'Demo' and the App ID of your base game must be entered in the General Application Settings section of the Steamworks website for your demo. …

Additionally, the Unit commands have the special action "queue." When an order action is received, if the game detects that the "queue" action is also currently being fired, it will not immediately execute the original order, but instead stick it on queue for that unit. When done with a "move" order this could be used to set waypoints, for instance. Again, this sort of logic would need to be implemented by the game itself. [code] "In Game Actions" { "actions" { "GameControls" { "title" "#Set_GameControls" "StickPadGyro" { "MoveCursor" { "title" "#Action_MoveCursor" "input_mode" "absolute_mouse" } "CameraPan" { "title" "#Action_CameraPan" "input_mode" "absolute_mouse" } "CameraZoom" { "title" "#Action_CameraZoom" "input_mode" "absolute_mouse" } } "Button" { "click" "#Action_Click" "cancel" "#Action_Cancel" "select" "#Action_Select" "select_add_remove" "#Action_AddRemove" "select_type" "#Action_SelectType" "select_idle" "#Action_SelectIdle" "move_attack" "#Action_MoveAttack" "move_no_attack" "#Action_Move" "attack_target" "#Action_Attack" "assign_group" "#Action_AssignGroup" "add_remove_group" "#Action_AddRemoveGroup" "select_group" "#Action_SelectGroup" "group_0" "#Action_Group0" "group_1" "#Action_Group1" "group_2" "#Action_Group2" "group_3" "#Action_Group3" "group_4" "#Action_Group4" "group_5" "#Action_Group5" "group_6" "#Action_Group6" "group_7" "#Action_Group7" "group_8" "#Action_Group8" "group_9" "#Action_Group9" } } "MenuControls" { "title" "#Set_MenuControls" "Button" { "MenuUp" "#Menu_Up" "MenuDown" "#Menu_Down" "MenuLeft" "#Menu_Left" "MenuRight" "#Menu_Right" "Affirm" "#Menu_Affirm" "Cancel" "#Menu_Cancel" "Other" "#Menu_Other" "ScrollUp" "#Menu_ScrollUp" "ScrollDown" "#Menu_ScrollDown" "DismissMenu" "#Menu_DismissMenu" } } } "action_layers" { "title" "#Layer_UnitMenu" "Button" { "stop" "#Unit_Stop" "hold" "#Unit_Hold" "patrol" "#Unit_Patrol" "follow" "#Unit_Follow" "queue" "#Unit_Queue" "unit_ability_1" "#Unit_Ability1" "unit_ability_2" "#Unit_Ability2" } "title" "#Layer_BuildMenu" "Button" { "build_0" "#Build_0" "build_1" "#Build_1" "build_2" "#Build_2" "build_3" "#Build_3" "build_4" "#Build_4" "build_5" "#Build_5" "build_6" "#Build_6" "build_7" "#Build_7" "build_8" "#Build_8" "build_9" "#Build_9" } } "localization" { "english" { "Set_GameControls" "Game Controls" "Set_MenuControls" "Menu Controls" "Layer_UnitMenu" "Unit Menu" "Layer_BuildMenu" "Build Menu" "Action_MoveCursor" "Move Cursor" "Action_CameraPan" "Pan camera" "Action_CameraZoom" "Zoom camera" "Action_Click" "Click mouse" "Action_Cancel" "Cancel" "Action_Select" "Select" "Action_AddRemove" "Add/remove from selection" "Action_SelectType" "Select all units of type" "Action_SelectIdle" "Select idle worker" "Action_MoveAttack" "Attack-Move" "Action_Move" "Move (no attack)" "Action_Attack" "Attack target" "Action_AssignGroup" "Assign group" "Action_AddRemoveGroup" "Add/remove from group" "Action_SelectGroup" "Select group" "Action_Group0" "Group 0" "Action_Group1" "Group 1" "Action_Group2" "Group 2" "Action_Group3" "Group 3" "Action_Group4" "Group 4" "Action_Group5" "Group 5" "Action_Group6" "Group 6" "Action_Group7" "Group 7" "Action_Group8" "Group 8" "Action_Group9" "Group 9" "Menu_Up" "Up" "Menu_Down" "Down" "Menu_Left" "Left" "Menu_Right" "Right" "Menu_Affirm" "Affirm" "Menu_Cancel" "Cancel" "Menu_Other" "Other" "Menu_ScrollUp" "Scroll Up" "Menu_ScrollDown" "Scroll Down" "Menu_DismissMenu" "Dismiss Menu" "Unit_Stop" "Stop" "Unit_Hold" "Hold ground" "Unit_Patrol" "Patrol" "Unit_Follow" "Follow" "Unit_Queue" "Queue action/waypoint" "Unit_Ability1" "Ability 1" "Unit_Ability2" "Ability 2" "Build_0" "Build option 0" "Build_1" "Build option 1" "Build_2" "Build option 2" "Build_3" "Build option 3" "Build_4" "Build option 4" "Build_5" "Build option 5" "Build_6" "Build option 6" "Build_7" "Build option 7" "Build_8" "Build option 8" "Build_9" "Build option 9" } } } [/code] [section=4x] 4X Strategy[/section] This is a simple 4X strategy game, where you move units on a main map, colonize territory (whether that's planets or islands or cities), and engage in combat with other empires. …

For more information about general Steam branding, refer to the [doclink=marketing/branding][/doclink]. [section]Workshop Types[/section] There are two main types of Steam Workshop integration options available. Each has benefits and trade-offs, so you should think carefully about which option makes the most sense for your product. …

[/b] If you are accepting items such as weapons via the Workshop, it may be important for you to be able to assign the attributes of the weapon such as speed, power, damage, reload time, etc. in order to best balance the gameplay in your title. [*] [b]Want tight control over the content added to your game.[/b] Depending on how you've set up your game, you can accept items in two different ways: [list] [*] [b]Download and build[/b] - If you want to download the assets to your local machine and include it in your game depots. …

. [*] Activating an action set layer that is already active will not change its order in the stack. [*] Deactivating an action set layer, and then activating it, will set it to the top of the stack. [*] Calling [apitype]ISteamInput::ActivateActionSetLayer[/apitype] is cheap and can be safely called repeatedly (but see callout below) [callout=red] [h3]Careful with multiple layers!…

The last layer applied will override any conflicting information that came before, so take special care to apply them in the correct order. Your code could easily have race conditions or other subtle timing bugs that could swap the order. Action set layers are intended for narrow use cases and a good practice is to apply and remove them only on specific game state changes. …

. [*][b]Export filtered packages[/b] - You can apply filters to the visible grid of packages in order to export a subset of packages. This can be useful if you wish to focus on a subset of your packages, say for just one game or franchise. …

Here are a couple of helpful tips to keep in mind: [list] [*][b]Reorder columns[/b] - You can change the order of columns without breaking the upload. Just make sure the first row in your file always has the right currency name for each column. [*][b]Removing rows or columns[/b] - You can remove rows or columns from the spreadsheet with two exceptions: [list] [*]Don't remove the first row. …

Be consistent with auto-aim on joysticks [/b] If you have any auto-aim or aim-assist applied to XInput analog sticks, consider applying that to Steam Input devices as well, at least for traditional controller models configured through Steam Input. You can call [apitype]ISteamInput::GetInputTypeForHandle[/apitype] to determine an individual controller's model type or implement separate mouse-style and joystick-style camera actions. …

Additionally: [olist] [*] [b]Set a recommended controller configuration for all controller types[/b] This way Steam doesn't have to prompt the user to select a configuration on startup. By the way, you don't need to provide a configuration for both the Xbox 360 and the Xbox One controllers -- if you only supply one, it will work for the other model. [*] [b]Opt-in Controller Type you don't have native support for to Steam Input[/b] If you don't have built-in support for these controller types, you should use the partner site to opt them in to using Steam Input. …

To enable the interaction profile you must request to use the extension: [code]XR_VALVE_frame_controller_interaction[/code] Then you can suggest bindings for the interaction profile path: [code]/interaction_profiles/valve/frame_controller_valve[/code] You can use the following paths: [code] "/user/hand/right/input/a/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/a/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/b/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/b/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/x/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/x/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/y/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/y/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/menu/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/menu/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/system/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/system/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/bumper/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/bumper/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/squeeze/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/squeeze/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/squeeze/value", XR_ACTION_TYPE_FLOAT_INPUT "/user/hand/right/input/trigger/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/trigger/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/trigger/value", XR_ACTION_TYPE_FLOAT_INPUT "/user/hand/right/input/thumbstick/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/thumbstick/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/right/input/thumbstick/x", XR_ACTION_TYPE_FLOAT_INPUT "/user/hand/right/input/thumbstick/y", XR_ACTION_TYPE_FLOAT_INPUT "/user/hand/right/input/thumbstick", XR_ACTION_TYPE_VECTOR2F_INPUT "/user/hand/right/input/grip/pose", XR_ACTION_TYPE_POSE_INPUT "/user/hand/right/input/aim/pose", XR_ACTION_TYPE_POSE_INPUT "/user/hand/right/output/haptic", XR_ACTION_TYPE_VIBRATION_OUTPUT "/user/hand/left/input/dpad_up/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/dpad_up/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/dpad_left/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/dpad_left/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/dpad_down/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/dpad_down/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/dpad_right/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/dpad_right/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/view/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/view/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/system/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/system/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/bumper/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/bumper/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/squeeze/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/squeeze/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/squeeze/value", XR_ACTION_TYPE_FLOAT_INPUT "/user/hand/left/input/trigger/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/trigger/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/trigger/value", XR_ACTION_TYPE_FLOAT_INPUT "/user/hand/left/input/thumbstick/touch", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/thumbstick/click", XR_ACTION_TYPE_BOOLEAN_INPUT "/user/hand/left/input/thumbstick/x", XR_ACTION_TYPE_FLOAT_INPUT "/user/hand/left/input/thumbstick/y", XR_ACTION_TYPE_FLOAT_INPUT "/user/hand/left/input/thumbstick", XR_ACTION_TYPE_VECTOR2F_INPUT "/user/hand/left/input/grip/pose", XR_ACTION_TYPE_POSE_INPUT "/user/hand/left/input/aim/pose", XR_ACTION_TYPE_POSE_INPUT "/user/hand/left/output/haptic", XR_ACTION_TYPE_VIBRATION_OUTPUT [/code] [subsection=openvr]OpenVR Bindings[/subsection] You can bind to the Steam Frame Controllers like you would any other OpenVR controller type. …

[subsection]OpenVR[/subsection] OpenVR has two functions in IVRInput [b]GetEyeTrackingDataRelativeToNow[/b] and [b]GetEyeTrackingDataForNextFrame[/b]. To use those you will need to create a new action of type [code-inline]"eyetracking"[/code-inline] to pass into the functions. …

[/td][/tr] [tr=k_PFI_MatchingFileType_Art][td][b]k_PFI_MatchingFileType_Art[/b][/td][td]2[/td][td]Artwork.[/td][/tr] [tr=k_PFI_MatchingFileType_Videos][td][b]k_PFI_MatchingFileType_Videos[/b][/td][td]3[/td][td]Videos.…

[/td][/tr] [tr=k_PFI_MatchingFileType_Games][td][b]k_PFI_MatchingFileType_Games[/b][/td][td]6[/td][td]Unused.[/td][/tr] [tr=k_PFI_MatchingFileType_Software][td][b]k_PFI_MatchingFileType_Software[/b][/td][td]7[/td][td]Unused[/td][/tr] [tr=k_PFI_MatchingFileType_Concepts][td][b]k_PFI_MatchingFileType_Concepts[/b][/td][td]8[/td][td]Unused[/td][/tr] [tr=k_PFI_MatchingFileType_GreenlightItems][td][b]k_PFI_MatchingFileType_GreenlightItems[/b][/td][td]9[/td][td]Unused[/td][/tr] [tr=k_PFI_MatchingFileType_AllGuides][td][b]k_PFI_MatchingFileType_AllGuides[/b][/td][td]10[/td][td]Guides.…

Up to 50 results may be returned, but usually it's no more than a couple. The results are returned ordered by geographical distance and based on any near filters set. By default, we will not return lobbies that are already full, and the distance filter is set to [apitype]ISteamMatchmaking::k_ELobbyDistanceFilterDefault[/apitype] (nearby). …

Only add in metadata and values that are used for search (for example, game type or game state). You will not need to put in player counts, as a lobby search will already look for lobbies with available slots [*]Do not join lobbies just to find out their metadata. …

[section=FrameCompatibilityChecklist]Frame Compatibility Checklist[/section] [subsection]Form Factor Requirements[/subsection] While Steam Frame is a fully-functional PC, we anticipate the most common use cases will be different from a standard desktop. In order to receive the [docimg=verified_18.png]Verified badge[/docimg] [b]Verified[/b] badge, you need to meet all of the following criteria, aimed at helping customers feel comfortable playing your game on Frame. …

The default controller configuration must provide users with the ability to access all content. Players must not need to adjust any in-game settings in order to enable controller support or this configuration. [*][b]controller glyphs[/b]: when using Steam Frame's physical controls, on-screen glyphs must either match Frame button names, or match Xbox 360/One button names. …

You can then select a space here on your homepage to display all your public lists. The lists will display here in the order you set for your lists in your list management interface. [section]"Multiplayer" Section[/section] [docimg=multiplayer_tag_01.jpg]multiplayer_tag_01.jpg[/docimg] This multiplayer section is achieved by selecting "Multiplayer" as a tag so that the section automatically populates with all the game's Valve has made that are tagged with "Multiplayer". …

This section will then automatically populate with the titles we've made, sorted in order of revenue. [section]Customized Tags[/section] [docimg=custom_tags_01.jpg]custom_tags_01.jpg[/docimg] You can also customize the tags that are shown in the left-most column of your tabbed area. …

The [doclink=api][/doclink] catalogs and documents every interface, function, callback, and type supported in the API. Integration with the Steamworks API is never required to ship your product on Steam, but it is highly recommended as it allows you to accomplish many interactions that Steam users expect. …

An event will only come through one or the other, not both. You must make sure that you are registering for the right type of event! Call results must be created as a member in a struct/class using the CCallResult type and you will also need to create the member function that will receive the callback. …

[subsection=AddVRScreenshotToLibrary]AddVRScreenshotToLibrary[/subsection] [code=cpp]ScreenshotHandle AddVRScreenshotToLibrary( EVRScreenshotType eType, const char *pchFilename, const char *pchVRFilename );[/code] [table] [tr][th]Name[/th][th]Type[/th][th]Description[/th][/tr] [tr][td][b]eType[/b][/td][td][apitype]ISteamScreenshots::EVRScreenshotType[/apitype][/td][td]The type of VR screenshot that this is.…

[b]Associated Functions:[/b] [api]ISteamScreenshots::TriggerScreenshot[/api] [section=enums]Enums[/section] These are enums which are defined for use with ISteamScreenshots. [subsection=EVRScreenshotType]EVRScreenshotType[/subsection] Describes the type of VR screenshots. [table] [tr][th]Name[/th][th]Value[/th][th]Description[/th][/tr] [tr=k_EVRScreenshotType_None][td][b]k_EVRScreenshotType_None[/b][/td][td]0[/td][td][/td][/tr] [tr=k_EVRScreenshotType_Mono][td][b]k_EVRScreenshotType_Mono[/b][/td][td]1[/td][td][/td][/tr] [tr=k_EVRScreenshotType_Stereo][td][b]k_EVRScreenshotType_Stereo[/b][/td][td]2[/td][td][/td][/tr] [tr=k_EVRScreenshotType_MonoCubemap][td][b]k_EVRScreenshotType_MonoCubemap[/b][/td][td]3[/td][td][/td][/tr] [tr=k_EVRScreenshotType_MonoPanorama][td][b]k_EVRScreenshotType_MonoPanorama[/b][/td][td]4[/td][td][/td][/tr] [tr=k_EVRScreenshotType_StereoPanorama][td][b]k_EVRScreenshotType_StereoPanorama[/b][/td][td]5[/td][td][/td][/tr] [/table] [section=typedefs]Typedefs[/section] These are typedefs which are defined for use with ISteamScreenshots. …

[section=ReportAbuse]ReportAbuse[/section] [code=http]POST https://partner.steam-api.com/ISteamCommunity/ReportAbuse/v1/[/code] [table] [tr][th]Name[/th][th]Type[/th][th]Required[/th][th]Description[/th][/tr] [tr][td][b]key[/b][/td][td]string[/td][td]✔[/td][td]Steamworks Web API publisher authentication key.[/td][/tr] [tr][td][b]steamidActor[/b][/td][td]uint64[/td][td]✔[/td][td]SteamID of user doing the reporting[/td][/tr] [tr][td][b]steamidTarget[/b][/td][td]uint64[/td][td]✔[/td][td]SteamID of the entity being accused of abuse[/td][/tr] [tr][td][b]appid[/b][/td][td]uint32[/td][td]✔[/td][td]AppID to check for ownership[/td][/tr] [tr][td][b]abuseType[/b][/td][td]uint32[/td][td]✔[/td][td]Abuse type code (see EAbuseReportType enum)[/td][/tr] [tr][td][b]contentType[/b][/td][td]uint32[/td][td]✔[/td][td]Content type code (see ECommunityContentType enum)[/td][/tr] [tr][td][b]description[/b][/td][td]string[/td][td]✔[/td][td]Narrative from user[/td][/tr] [tr][td][b]gid[/b][/td][td]uint64[/td][td][/td][td]GID of related record (depends on content type)[/td][/tr] [/table] Allows publishers to report users who are behaving badly on their community hub. …

[/td][/tr] [/table] [code-inline]game_names[/code-inline] has the following structure: [table] [tr][th]Name[/th][th]Type[/th][th]Description[/th][/tr] [tr][td][b]id[/b][/td][td]uint32[/td][td]ID number of entry; referenced in site info below[/td][/tr] [tr][td][b]name[/b][/td][td]string[/td][td]Game name[/td][/tr] [/table] [code-inline]sites[/code-inline] has the following structure: [table] [tr][th]Name[/th][th]Type[/th][th]Description[/th][/tr] [tr][td][b]siteid[/b][/td][td]uint64[/td][td]64-bit SiteID of the site[/td][/tr] [tr][td][b]site_name[/b][/td][td]string[/td][td]Site name you have assigned to the site[/td][/tr] [tr][td][b]games[/b][/td][td]see below[/td][td]list of all game titles played[/td][/tr] [/table] [code-inline]games[/code-inline] has the following structure: [table] [tr][th]Name[/th][th]Type[/th][th]Description[/th][/tr] [tr][td][b]id[/b][/td][td]uint32[/td][td]ID of game in the [code-inline]game_names[/code-inline] section of the response[/td][/tr] [tr][td][b]license_type[/b][/td][td]string[/td][td]Playtime is divided up for each game by the type of license used. …

[/td][/tr] [tr][td][b]playtime_seconds[/b][/td][td]uint32[/td][td]total playtime for this game and license type, in seconds, for the requested period.[/td][/tr] [/table] …

[subsection]Situation[/subsection] You've got a released game with customers already playing it and you need to rename your exe. [subsection]Solution[/subsection] The order of operations can matter here, as setting a build live doesn’t go through the publish process but changing the launch options does. …

[/td][/tr] [tr=k_EWorkshopFileTypeVideo][td][b]k_EWorkshopFileTypeVideo[/b][/td][td]4[/td][td]External video.[/td][/tr] [tr=k_EWorkshopFileTypeScreenshot][td][b]k_EWorkshopFileTypeScreenshot[/b][/td][td]5[/td][td]Screenshot.…

[/td][/tr] [tr=k_EWorkshopFileTypeConcept][td][b]k_EWorkshopFileTypeConcept[/b][/td][td]8[/td][td]Unused, used to be for Greenlight concepts.[/td][/tr] [tr=k_EWorkshopFileTypeWebGuide][td][b]k_EWorkshopFileTypeWebGuide[/b][/td][td]9[/td][td]Steam web guide.…

Generator Legendary applies the tag [code-inline]quality:legendary[/code-inline] and creates sword or shield items, while Generator Common applies the tag [code-inline]quality:common[/code-inline] and also creates sword or shield items. [code] itemdefid: 10 type: item name: Sword itemdefid: 11 type: item name: Shield itemdefid: 100 type: generator name: Generator A bundle: 101x1;102x9 tags: color:red itemdef: 101 type: generator name: Generator Legendary bundle: 10;11 tags: quality:legendary itemdef: 102 type: generator name: Generator Common bundle: 10;11 tags: quality:common [/code] Another way to assign tags would be to use the [code-inline]tag_generator[/code-inline] item definition type. …

In the end you could end up with "Legendary Red Shield with Flames" or a "Common Red Sword with Lasers." [code] itemdefid: 10 type: item name: Sword itemdefid: 11 type: item name: Shield itemdefid: 100 type: generator name: Generator A bundle: 10;11 tags: color:red tag_generators: 101;102 itemdefid: 101 type: tag_generator name: Tag Generator Quality tag_generator_name: quality tag_generator_values: legendary:1;common:9 itemdefid: 102 type: tag_generator name: Tag Generator FX tag_generator_name: fx tag_generator_values: flames;sparks;lasers [/code] The format for the [code-inline]tag_generators[/code-inline] field is a list of all item definition ids of the tag generators you want applied, separated by the ";" character. …