Forum posts

void BarneyFirePistol( void );

virtual void BarneyFirePistol( void );

Do both maps contain an info_landmark with exactly the same name? And does each trigger_changelevel match an open, walkable space in the other level (relative to the landmarks)?

And just in case you haven't seen this yet: Tutorial: Changing Levels.

• ...that must enable A: add a trigger_relay TR and make it toggle multisource MS, then make func_button B target trigger_relay TR. (if you let B target MS directly, you'll hit a bug where MS won't be triggered one out of every 4 button presses)
• ...that must disable A: same as above, but also add a trigger_auto that triggers trigger_relay TR as soon as the level starts. This inverts the relationship between B and MS. (give the trigger_auto a small delay, otherwise it might fire before TR has been spawned)

• ...that must enable A: the most common and easy setup: just make func_button B target multisource MS. (buttons don't trigger their target when they auto-reset, unless their target is a multisource - so this scenario was designed to be easy to do)
• ...that must disable A: add a trigger_relay TR that toggles multisource MS, and add a trigger_auto that triggers trigger_relay TR when the level starts. But instead of making func_button B target trigger_relay TR directly (which you would do if B were a toggle button), make it target a multi_manager MM. Then make multi_manager MM target trigger_relay TR twice: first with a delay of 0, then with a delay that corresponds to func_button B's auto-reset time (or slightly lower, just to be safe). (the problem here is that auto-resetting buttons do not trigger their target when the reset, so we'll have to use a multi_manager to simulate that behavior)

Cache_??? Cache memory is for objects that can be dynamically loaded and
can usefully stay persistant between levels. The size of the cache
fluctuates from level to level.

MESS 1.1 is now available!

• MESS 1.1 - The compile tool itself.
• example maps - Updated example maps. Be sure to check out the new rathunt example, and its use of the custom rh_rat and rh_message_system entities!

• Readme - An introduction to MESS, and instructions on how to get started.
• Entity guide - Like TWHL's entity guide, but for MESS' macro entities.
• Rewrite rules - For creating custom entities, and telling MESS to rewrite them to template-inserting entities.
• Scripting system - Documentation for MScript, the scripting language used by MESS. See the functions section for a list of functions, many of which are new in 1.1.

• Added a 'rewrite rule' mechanism, for creating template-based entities.
• Added support for J.A.C.K. template map files (.jmf).
• Added several string, math, trig, color, flags and directory-related MScript functions.
• Added a not operator to MScript (alternative for !).
• MScript now converts none function arguments to the default value for the parameter's type, for non-optional parameters.
• Added a 'REPL' mode, for interactive testing of MScript expressions.
• The special spawnflag<N> attributes now start at 0, not 1.
• The template_name attribute is now a target_destination, so J.A.C.K. can show links between macro entities and the templates they're using.
• Added MScript documentation.

• Fixed that .rmf files without cameras failed to open.

• Game tab: remove any .fgd files and add dmc.fgd instead (this file is included in the FGD collection here).
• Directories tab: I think you only need to change the 'Mod Directory' to point at your Half-Life\dmc folder.
• Textures tab: any .wad files you're using must either be part of DMC, or you'll have to distribute them alongside your map (you can embed textures into maps to make things easier for players). It's easier to only select DMC wad files for now.
• Build Programs tab: you can use the same compile tools as for HL/HLDM, so no changes required here.

• Duplicating complex entity setups as if they were a single entity.
• Covering terrain and other surfaces with props.
• Turning a single brush into multiple entities.

Landmine template

Landmine instances

$csg_exe $bspdir/$file
$bsp_exe $bspdir/$file
$vis_exe $bspdir/$file
$light_exe $bspdir/$file

$csg_exe "$bspdir/$file"
$bsp_exe "$bspdir/$file"
$vis_exe "$bspdir/$file"
$light_exe "$bspdir/$file"

• cycler_sprites do precache their model after reloading, so that is not what's causing them to disappear.
• the brush-based entity 'hack' does not suffer from the reloading problem (tested with func_wall and func_illusionary). However, this requires another entity to precache the model, and that precaching must be done before the brush-based entity is initialized, otherwise HL with hang or crash while loading the map. This depends on the order in which the entities are stored in the .bsp file.
• J.A.C.K. does not handle brush-based entities without brushes well - in some cases it crashes, in other cases it puts them at (0, 0, 0).
• monster_furnitures are dropped to the ground after spawning.
• env_sprite seems to work just as well as cycler_sprite, without the reloading problem.

Why does nobody use monster_furniture...

• cycler_sprites are not restored correctly. That probably wasn't implemented because it's just a sprite-viewer test entity after all.
• monster_furnitures are restored correctly. They're also seen as targets by the auto-aiming system, and bleed a little when hurt by explosives.
• trigger_autos that did not remove themselves after firing are triggered again.

• If you don't need your entity again, then just kill it (quite a few entities support the 'killtarget' property).
• Use a func_wall_toggle. Trigger it to make it disappear (or reappear).
• Use an env_render to make your entity invisible.

• Shearing is quick and easy, but significant shearing results in 'thin' brushes.
• With the clipping tool (shift+X) you can start with a larger brush and cut away parts until you get the desired shape. Press shift+X again to cycle between modes (remove right side, remove left side, keep both sides).
• With vertex manipulation (shift+V) you can move each vertex or edge individually, create new edges (by selecting two vertices or two edges on the same face and pressing ctrl+F) and remove vertices (by dragging them onto other vertices). This is a powerful tool, but keep in mind that each face must remain perfectly flat - bent or curved faces are invalid. Brushes must also remain convex (e.g. no U-shaped brushes). Press shift+V again to cycle between modes (vertices and edges, vertices only, edges only).
• When creating a brush, you can choose between a few different shapes. 'block' is the default choice, but 'arch' is probably more useful in this case. Keep in mind that it'll be facing towards you in the 2D view that you most recently clicked on.