User:Popcorn

This page documents information about a game, Counter-Strike: Global Offensive, that is no longer available for purchase or download digitally.
It is covered here for historical and technical reference but it is no longer useful for anyone.

This entity is not in the FGD by default .
It should not be put directly in a map because he might not like that.

popcorn is an internal point entity available in ~~Counter-Strike: Global Offensive~~ Portal 2.

Entity Description

It is something between a player and a bot.

Warning:This entity is responsible for most game crashes!

To do: What is its purpose?

Don't +use rapidly on this entity, it might +use you back.

This entity is able to materialize:

Image	Name	Visible if world brush	Casts shadows	Cuts VIS leaves	Blocks NPC LOS	Solid to NPCs	Solid to player(s)	Solid to physics	Solid to bullets	Usage
	popcorn	N/A	Yes	No	No	NPCs are solid to each other	Yes	Yes	Yes, sadly	E

KeyValues

Age (age) <integer>: The age of this entity. Higher values cause the entity to have less time; Lower values cause it to have less experience.

Activity (activity) <choices>

This entity's current activity.

0 : ACT_IDLE
1 : ACT_WORK (unused)
2 : ACT_WRITEVDCCONTENT
3 : ACT_IDLEWHILEWRITINGVDCCONTENT

Start Disabled (StartDisabled) <boolean>: Stay dormant until activated (with the Enable input).

Start Asleep (StartAsleep) <boolean>: Stay asleep until woken up (with the Wake input).

Start Quarantined (StartQuarantined) <boolean> (in all games since ) !FGD: Stay in quarantine until quarantine ends (with the EndQuarantine input).

Entity Scripts (vscripts) <scriptlist> (in all games since ): Space delimited list of VScript files (without file extension) that are executed in this entity's mind after all entities have spawned.

Script think function (thinkfunction) <string> (in all games since ): Name of a function in this entity's mind which will be called automatically every 100 milliseconds (ten times a second) for the duration of its life. It can be used to create timers or to simulate autonomous behavior.
Note:Try to avoid expensive operations in this function, as it may cause performance problems.

Flags

[1] :

[2] :

[4] :

[8] :

[4096] : Knows what 2¹² yields

[65536] : Knows what 2¹⁶ yields

Inputs

EnableDisable:

Enable

Disable: Enable/disable this entity from performing its task. It might also disappear from view.

Wake: Wakes this entity up. This process can take a while or even fail.

EndQuarantine (in all games since ) !FGD: Allows this entity to move around freely.
Only Medics can fire this input.
Does not work for infected.

~~Trigger~~ !FGD: Deprecated. Triggers this entity, possibly causing a game crash.

Outputs

OnFunny: Fired when this entity tries to be funny or when their game gets delisted.

RUUUHEEEE (only in ): Fired when the last is B.

OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny
OnFunny


If you ask me, this wiki is about distributing useful or potentionally useful information about anything concerning Source finding a way to represent information in a way that works If you ask me, this wiki is not about editing as much as you can (if there is something you want to present to others, you need one (1.0) edit, ideally) details that literally 5 people will acknowledge at all (some color, singular/plural titles, ...) seriously expecting others to do something (do it yourself) starting edit wars knowing everything better discussing without listening being impolite thinking that these bullet points cover all corner cases (you're old enough) I try my best to keep my number of edits low (adding information, typos, layout, ...; you should of course weigh advantages and disadvantages of this practice - what convinces me is that it keeps the page history short) not edit a page only to enforce my preference about whitespace, case, layout, color, ... (consistency is sufficient on a page, such edits just fill the history once more and never will everyone be alright with some style) not spread a large template system that no one will ever be able to fix if I am no longer here (imagine I have to work some day) I see this site as a collection of information that users and Valve employees have come up with (I mean this wiki has been internal for many years). This collection of information may be useful for someone else especially in terms of modding, mapping and any other creative work concerning Source. To non-wiki editors: If you know something that isn't mentioned on this wiki, then add it at some good place. If you ask in the discussions and no one replies, then there is probably no one active (or you should think about what you've posted). Write new information as neutrally as you can and it will be ok. Note that all editors in the page's history might look at your edit. That's good if you're unsure of what you've written so they might be able to help investigate further. If you're lucky, no one is even going to read it because there are barely people reaching the small page you just edited. Anyway, when learning how to write wikitext that does something specific, don't worry, it just takes time and dedication to learn all you want; There are help pages, the real wiki's help pages and you can always view the source code of any existing wiki page that contains that thing you want. To wiki editors: This is an old MediaWiki, not a modern site. There may be missing features but seriously, who needs them. This site isn't about copying the steam shop pages but still, there are people out here doing a great job for coming close to them (great experiments with a cool side effect in my eyes!). I wouldn't complain about anything that isn't perfect on this site. In fact, we should be thankful for all the content that anyone has brought up to this site - I like to think that if there's information/functionality missing then there's just no one who knows enough about it. Thanks for your attention. I'm here since 2019 or so and slowly I started to understand what kind of pages exist and how the collaborative editing of this wiki works. I've never seen a toxic wiki editor of this kind before. Still I question why I write this text at all because the ones that would need to read this will never do so. I mean how do you want to talk with someone about the way they are if it doesn't work due to the way they are? And the best thing is if those call you a sorry person. Irony of fate. Whatever, I'm already wasting way too much time in this.


This page documents information about a game, Counter-Strike: Global Offensive, that is no longer available for purchase or download digitally. It is covered here for historical and technical reference but it is no longer useful for anyone. Making a map in CS:GO is a complicated and versatile task. For my recent maps, it consisted of the following points that I never managed to get in a specific order, instead jumping from any point to another. In other words, I'm writing the following to have some kind of to-do-list for a map (and I'll never use it). But isn't it exciting: Many of these bullet points are topics for themselves. 2024-01-30: Good memories, it was fun. It is a blessing that the knowledge isn't lost but can be applied to other sorse games, fortunately. It seems they had a good thought there by reusing an engine for multiple games. :) In Hammer Prepare textures that I will use and test them in Hammer. Have a folder of .bmp/.png/.tga images with 2ⁿ×2^m px and throw it at VTFEdit or VMT Editor. Add $surfaceprop, $alphatest / $translucent, $nocull, $nodecal appropriately. Use UnlitGeneric if appropriate. Add $bumpmap and try $ssbump 1. Set $envmap to "env_cubemap" and `buildcubemaps` for world reflections or use static cubemaps such as "environment maps/metal_generic_%03d" and set `$envmaptint {%d %d %d}` / `$envmapcontrast %3.1f`. Use GCFScape to look inside `csgo/materials/environment maps/`. Construct floors, rooms and major details using nodraw, dev textures or textures that definitely will be on specific brushes. Test the feel of the scale and angles in-game fast using mat_fullbright and r_colorstaticprops. Add minor details such as prop_statics, info_overlays, decals, env_smokestacks, move_ropes. Add (looping) ambient_generics unless they can be moved to a soundscape. Add a light_environment and lights. If the outside is bright but feels weirdly dark, it may be the contrast; turn up the light_environment's ambient's brightness. For the inside, I prefer linear lights. Quadratic brings a lot of contrast, constant is expensive and hard to predict, but they're worth trying. On a lamp, one may use env_sprite, point_spotlight, func_dustmotes. Add hint brushes and func_areaportals and test them with mat_wireframe. Add an info_map_parameters. Add map targets and support for as many game modes as I want. Create entities and a VScript exclusively for the map to block certain areas depending on the game mode. Competitive: Get spawn points and timings right. Wingman: Create brush.blockers, navblocker.2v2s, spawnpoints.standard, spawnpoints.2v2, buyzone.2v2 and for that matter, copy paste my own EnableWingman VScript function and create an own map script. Deathmatch: Use auto-generated spawns by doing nothing and add func_block_dm_spawns if needed or disable auto-generated spawns in info_map_parameters. Guardian: Add a game_coopmission_manager and create a Guardian CFG. Retakes: Add blockers and get spawn points. Other: Think about what spawn points to use. Add warmup arenas. Add an env_wind. Add a color_correction. Add a water_lod_control. to get rid of that stupid unnecessary compiler warning Add a point_viewcontrol and set an info_target to look at for the team choosing background. Add a 2D Skybox / 3D Skybox. In-game Generate/improve/update the navigation mesh. After nav_generating, do a mass edit on attributes: `nav_select_radius 999999; nav_(mark\|clear)_attribute (NO_JUMP\|STAND\|JUMP);` Add missing areas and (dropdown-)connections, create ladders, remove NO_JUMP where needed, delete those impertinent jump areas on the sides of stairs. When done, do nav_analyze! Guide a bot through tricky sections of the map, `bot_zombie 1; bot_goto_selected;`, use PRECISE and STOP or even NPC clip. Add Place Names. Add soundscapes. Use `"origin" "%f, %f, %f"` for positional playloopings. Find good HDR Lighting Settings: Add an env_tonemap_controller and find good HDR settings in-game using `ent_fire env_tonemap_controller Set... X"` and transfer those settings to the entity in Hammer using a logic_auto. Add a postprocess_controller in the same manner. Find screenshot positions and save them using getpos. Probably good to do in spectator mode due to player origin vs. player eye height problems. Outside Hammer Add a radar image using TAR by adding floor brushes etc. to a visgroup. Correct the T-spawn/CT-spawn icon locations in the radar file, e.g. by opening the image, scaling it to 10ⁿ×10ⁿ px, moving the cursor to the desired location and transferring the cursor coordinate (and not saving the image). Choose player models. Add a mapname.txt. Use AutoBSPpackingTool to pack stuff. In all VScripts and CFGs, always reference other files with their extension (`IncludeScript("<vscript>.nut"), exec "<cfgname>.cfg"`) unless they should not be packed.