I hope to see. They are more about mapping, so that's why I post here.
- Adding of FG42 scoped and mortars as weapons you could use as objectives/gifts for some tasks. With moving mortars to soldier class they can't be used for objectives (like now). So I think it should be possible to grant them to team for fullfilling task. AFAIK now you can't spawn scoped FG42 so maybe it could be fixed too.
If you are looking for reducing entity count (it looks like with changes to Bazookas and mortars) there are more thing that could help:
- Spawn zones (single entity for whole team). In such zone soldiers would spawn in some grid (like every 64, 72, 96 units, this would tell how much soldiers fit there).
- object spawn zone (like above but for objects - weapons, satchels, etc.).
- light with included sprite field (so 1 ent. instead on two).

Whit der **** yoo beh talkin aboot boy?

You see, there is this game, called Day Of Defeat. In this game, there are certain maps with special soldiers called "Paratroopers". They are called that because they parachute into battle (Parachute + Troopers = paratroopers). These parachute troopers get slightly different weapons, like the FG42. This FG42 comes in two flavours. One with a bipod, one with a scope.

You said it is impossible to spawn with a scoped FG42.

When you start a game, choose to be Axis (make sure you are on a paratrooper map, like dod_flugplatz) and find the FG42 with scope. Click on it.

Voila! when you spawn, you are carrying a FG42 with a scope! Isn't modern, user-friendly, so-easy-to-use-that-my-five-year-old-sister-can-do-it technology great?

P.S: That was sarcasm.

P.P.S: If you not know what sarcasm is, stab yourself in the eyes with a large pencil. Then jump off a building and get run over by a car. Twice.

all good ideas sir :)


he's talking about spawning the weapon entity in a map, not spawning ingame WITH a fg42

Wow dark, no need to be a sarcastic asshat


Edited for truth


Craftos, I love the spawn idea... its clever and sexy

Another thing that came into my mind:
In info_doddetect : instead of selecting country for Allied team (you can leave it for compatibility for older maps as "default" country), add 2 more text fields. They would contain paths for default soldier models for both teams. This way we could use custom models for some missions - winter, desert camo, some special scenarios involving other countries (but with default weapons_ - like Canadians, French, Italians, Polish (:)).
With current fast web downloads it would be quite easy for ppl to get everything (also pack such models into map pack for distribution). Since there is code for loading models for paras and brits it shouldn't be too hard to change it a little to allow using custom-as-default models.

Very interesting premise...I'll ask around...I like this thought.

Yeah I bounced the idea a while ago that info_dod_detect should have:
Allied team model (defaults to models/player/us-inf/us-inf.mdl)
Axis team model (defaults to models/player/axis/axis-inf/axis-inf.mdl)

Also, it would be good (but I doubt possible) if custom voice sets could be specified, this could be done with the first word of the player WAV files, in the same way the ENV.tga files are identified. For example default German voices all begin with ger_ (eg ger_grenade as opposed to brit_grenade), so the axis voice set would be identified with ger_.

Also, recently I have been musing the idea of "spawn areas" - usually 2 separate ones (ATM all maps spawn players in more or less the same area). EG a beach map could have allied_spawn_a, where the beach infantry land, and allied_spawn_b, where paratroopers land :) I know thats a bit far fetched! But thats the general idea.

^ Craftos - don't forget Aussies! Someone has to do a map with them!
On the subject of French players... can I reiterate my idea of French resistance maps? :) Possibly a new gamplay style could emerge...

One thing to note...we're not going to have this option in 1.3 and I have serious doubts it'll ever be an option in the DoD 1.X world...too much "sourcing" going on and it's never as easy as just adding a line or two of code here-n-there. As to the future? No clue.