.Map :: MoHAA Mapping

You could try setting the max_health variable of the players.

g_allclasses wrote:max_health( Integer max_health )

sets max_health without changing health

I'm not sure if you could just use $player.max_health = 200, or if you'd have to apply it to each player as they joined the server.

// brush 0
{
( -64 192 -64 ) ( -128 192 -64 ) ( -128 128 -64 ) central_europe/normndybrik1sml 0 0 0.00 1 1 0 65536 0

( -128 128 0 ) ( -128 192 0 ) ( -64 192 0 ) barracks/tentallies 0 0 0.00 1 1 8192 134217728 0

( -128 128 -56 ) ( -64 128 -56 ) ( -64 128 -64 ) barracks/mag1 0 0 0.00 1 1 8192 512 ...

fillstar wrote:The other thing i notice is when a segment is checked and i hit the done button to delete, occasionaly i see a few extra segments like neighbours, also change in appearance just curious

Any facets adjacent to those you have deleted are forced to be max detail (I think they're shaded red).

They're not really deleted within the editor, only marked as deleted, this tells the compiler to ignore the facet, thus deleting it ingame. If you highlight them and uncheck delete they should reappear.

I'm not sure why it works in some game modes and not others, but you should probably change the for loop used to make the script wait to: wait 30 (Unless you're planning to expand the script to do something else within the loop).

gravity:
$gravity_hotspot waittill trigger
local.player = parm ...

The view is of the propellers on the outside and bits of the nose and tail, all outside items. What I would like is for the view to be that of inside the c47.


Are you sure the inside of the plane is modelled, it sounds like only the outside is which is why you only see the outside parts ...

Yes, radiant does store some data in the registry. The exact path varies depending on your version of windows, but it will be something like: HK_USERS/../Software/MOHAA/Radiant/ .

Just do a search for "radiant" in regedit, and delete the relavent keys.

+= and -= ... never seen those used.

These operators are a "short hand" way of writing the following expressions:



// local.number += 1 is equivalent to the line below.
// It means add one to local.number, and store the result in local.number.

local.number = local.number + 1


// local.number ...

You perhaps need to turn off the physics for the player:

I'm guessing you mean a static placed machine gun like the mg42 in Moh:AA. Yes you can alter the weapon view, it's stored in a seperate *.tiki.

So take the mg42 for example, it would have two files: mg42_gun.tiki which is the "world" model, and a mg42_gun_viewmodel.tiki which is the model displayed ...

plane:
local.plane = spawn script_model
local.plane model "vehicles/stuka_fly.tik"
local.plane.origin = ( 482.53 2568.24 340.42 )
local.plane.angles = ( 0 180 0)
local.plane.scale = .2


local.trig = spawn trigger_use
local.trig targetname plane
local.trig.origin = ( 482.53 2568.24 340.42 ...

Yes Splaetos' script will do what you want.

I guess that means you're in the goto camp

Try changing the model to "fx/dummy.tik":
Plus you should move the mylite_thread definition out your main thread, because I think that will also cause a problem.

Splaetos wrote:I wouldnt bother with global variables in this case

Good job I made them local

It all depends on whether you like using goto, personally I always try to avoid it. Although for MoH scrippting it's not too bad since there are certain limitations to using it.

How about this to get you started, but keep in mind there is more than one way of doing it:



thread alliesLever:

// Controls the checking loop.
local.triggered = 0

// While the trigger hasn't been used by allies, keep checking.

while (!local.triggered) {
// Wait till it's used.
$trigger ...