|
|
Line 22: |
Line 22: |
| {{Capsule | | {{Capsule |
| | style = 1 | | | style = 1 |
| | bg = #294157 | | | bg = #4B2A2E |
| | [[Image:Dota workshop.png|link=Dota 2 Workshop Tools]] [[Dota 2 Workshop Tools|<span style="color:white;">'''前往 Dota 2 开发工具文档主页'''</span>]] | | | [[Image:Dota workshop.png|link=Dota 2 Workshop Tools]] [[Dota 2 Workshop Tools|<span style="color:white;">'''前往 Dota 2 开发工具文档主页'''</span>]] |
| }} | | }} |
Line 57: |
Line 57: |
| {{:Valve Developer Community:Tasks}} | | {{:Valve Developer Community:Tasks}} |
| |} | | |} |
| | |
| | <div style="display:grid; justify-items:center; margin-top:2em; padding-inline: 2em; background:rgb(34, 34, 34,.5); box-shadow:rgba(32, 32, 32, .05) 0 0 3px 0 inset; border-radius:.5em;"> |
| | <span style="margin-right:3em;">[[File:Discord-logo.png|150px|link=https://discord.gg/b7dcrAFB7d]]</span> |
| | <span style="margin-right:3em;">[[File:Github-logo.png|150px|link=https://github.com/ValveDeveloperCommunity]]</span> |
| | <span style="margin-right:3em;">[[File:Mediawiki.png|155px|link=https://www.mediawiki.org/wiki/MediaWiki]]</span> |
| | <span style="margin-right:3em;">[[File:Combineoverwiki-wh.png|150px|link=https://combineoverwiki.net/wiki/Main_Page]]</span> |
| | <span style="margin-right:3em;">[[File:Portalwiki.png|150px|link=https://theportalwiki.com/wiki/Main_Page]]</span> |
| | <span style="margin-right:3em;">[[File:Tf2wiki.png|150px|link=https://wiki.teamfortress.com/wiki/Main_Page]]</span> |
| | [[File:Lfdwiki.png|175px|link=https://left4dead.fandom.com/wiki/Left_4_Dead_Wiki]] |
| | </div> |
Revision as of 17:30, 12 April 2023
欢迎来到 Valve 开发者社区(Valve Developer Community)!无论您想要制作一款 3A 大作,还是一款半衰期2的MOD,您都可以在此网站上找到您需要的信息!您可以免费加入 Valve 开发者社区,我们向所有使用 Source Engine 与 Source SDK 的开发者开放。
马上注册,成为社区的一员!
Valve 技术
Template:ValveTechnologyEditable
Source 引擎 与 Source SDK
我们将所有引擎方面的信息和工具都汇聚并展示在本社区维基上,您可以注册成为开发者帮助我们添砖加瓦。
Dota 2 开发工具
Half-Life: Alyx 创意工坊工具
SteamVR 创意工坊工具
|
对于 Mod 制作团队
对于维基所有者
试图将维基所有者的注意力吸引到一个非常有限的维基上。以下是包含有助于改进 wiki 的内容的文章的链接。
对于维基编辑者
The templates to be created are listed below.
Create {{Speedy delete}} to differentiate it from {{Delete}} . The latter should be used such that a discussion can be had before the content is removed whereas the former should be reserved for quickly removing content that violates VDC policies or doesn't require a discussion.
The templates that needs to be improved are listed below.
Add parameters to {{Stub}} to allow more granularity in what the stub is for (ie. a specific game, mapping, textures, programming, etc.) and for an appropriate sub-stub to be used.
Add add a unique category for each {{{reason}}} on {{Delete}} .
The templates listed below need documentation, or having a proper documentation page + template.
The templates listed below should be deleted. Please note that some templates must first be removed or replaced from the pages before they are deleted.
Create a unified cleanup template that consolidates the functionality of all it’s related templates.
Merge {{Game announced}} and {{Game announced2}} into one whole template with optional settings to show/hide "You can also visit store through Steam or your browser for more information."
Create a page listing the bots available for tasking and what they are capable of.
These jobs should only take you a little time for each one.
Add a res to Steam Resource Map. Aswell update ALL the outdated screenshot from the old Steam version to new one as of 2023.
Convert “ and ” (“ and ”) to " in code blocks.
Convert ’ (’) to ' in code blocks.
Convert em dashes — (—) to - in code blocks.
Make sure a page only links to a term the first time it’s mentioned unless important.
Read a new page and give feedback on the discussion page on how the content can be improved.
Possibly add a Related Topics section at the end.
Add see also links to relevant FGDs on all Category:<game_name> entities pages
These projects will take a little longer.
Create a documentation page for a template.
Create a mini-tutorial, for a simple problem users have.
Pick an entity in the list of entities for a game, and transcribe the entity help from inside Hammer.
- • A lot of info on entities can be found by looking at the FGD’s.
- • Test any and all entities before you describe them, for any potential bugs that may occur that the user should know about.
- Make sure to include the basic description, keyvalues, flags, as well as all inputs and outputs. Example: env_fire.
Pick a page in the Hammer Editor documentation, and add links where they are missing.
- • Look for the text “See the topic name section for more information”, and make it a link to the proper page. Capitalized words in Bold are also often link candidates (i.e. Entity Report or Object Properties).
- • Some pages under Category:Hammer Toolbars need links.
- • Add links to the Hammer Hotkey Reference page.
- • Add any potential content that might only be unique to versions of hammer for specific games.
Take an existing page that is too large and divide it into smaller, more manageable topics.
Need a tutorial on how to transfer an existing mod that’s under development from one machine to another and have the tutorial cover all of the gotchas.
Update “List of Soundscapes” pages to include any entries not on them already, and to include more detailed descriptions of soundscapes.
Update any game level creation page (example Portal 2 Level Design) and include any specific content for the games.
Mark (almost all) these pages on Category:Other games on Steam to delete all of them as it's has nothing to do with Valve games (content or assets for example), nor even using GoldSrc/Source/Source 2 engine whatsoever, aka completely off-topic. And these page barely have any content whatsoever anyway.
Extended projects that may take you a while to do.
Update pictures with white backgrounds to match current VDC theme (as of June 2012). Also try to make some of them having transparent PNGs if possible.
|