상세 컨텐츠

본문 제목

29th Infantry Division Darkest Hour

카테고리 없음

by traledenget1981 2020. 1. 23. 02:19

본문

29th Infantry Division Darkest Hour

Welcome to Paradox PlazaThis is a sub-reddit for discussion, links, etc. About any game published by Paradox Interactive or their partners.Games similar to Paradox titles may also be discussed.Our Teamspeak IP is:37.139.14.169:9988Our Discord Address is:. Hover your mouse over any of the boxes below to view relevant information.RulesFor the full rules, click.Posts must be related to Paradox. Just the title of the post being relevant does not qualify.No memes, image macros, reaction pictures, or similar.

I know there is TS and the others, but some sort of better in game system needs to be established to allow everyone on the one side to know what the hell is going on. Lol Which leads me to where it can be fun and effective in both changing the game play and course of a battle. 29th realism scrims. Darkest Hour 8.0. Morra Ret. November 2017 in Public Discussion. Lol Which leads me to where it can be fun and effective in both changing the game play and course of a battle. 29th realism scrims. From assigning players to a squad to controlling your squad on the battlefield to establishing strongholds, this no doubt can be a.

Post those in.No links to pirated materials, pirated game mods, or key resellers. General discussion of piracy or leaked content is allowed.Adhere to the Reddit content policy and the reddiquette.Explain what you want people to look at when you post a screenshot. Explanations should be posted as a reddit comment - referencing the title is not enough.All giveaways, surveys, and petitions must be approved by the moderators first. Game-trade threads are not allowed. This includes games and expansions.Users may only make one self-promotional submission per week.All posts must have link flair.

Infantry

As Germany, my standard army composition for infantry is three divisions per corps, three corps per army. Major and lieutenant generals command the corps and one of the corps is usually commanded by a full general. I keep divisions with slow attachments together - artillery, AA, AT, etc. in the same corps and the same goes for attachments that either increase or don't negatively affect speed, like armored cars, engineers, SP-ART/AT, etc. Several armies make up an army group, commanded by a field marshal with an HQ who is kept separate from the divisions he commands so he can be flexible and go wherever he is needed to ensure a cohesive command and control.I organize armored formations in roughly the same way - three division corps, three corps armies. However, I usually have a ratio of one armored division and two motorized/mechanized divisions in each corps so I'm guaranteed the combined arms bonus. I only attach brigades that will increase or at least not decrease the speed of my units.

Oftentimes I will have individual armored divisions in my 'panzerarmees' to race ahead and seize territory, because motorized divisions will slow you down a bit. My favorite attachment for any mobile division is self-propelled artillery. No, I'm talking about DH. I use 'units' of three divisions. One 'unit' of three divisions is a corps commanded by a major/lieutenant general.

An army is a group of three corps each of three divisions each for a total of nine divisions. This ensures that I never have to worry about exceeding my command limit especially if my HQs are in place properly - one for every army group, which is three armies of three corps for a total of 27 divisions. If you didn't know, you can actually edit the names of your commands in DH. So I rename one 'unit' of three divisions to be something like '3rd Army Group/21st Army/54th Corps'. All you have to do is click the name and delete what's there to add your own text.

I almost always keep like with like - keep infantry with artillery together, because one slow Inf-Art limits the speed of your whole corp. Same with Mot/Mec/Arm, mixing them with Inf/Mil will severely hamper their greatest strength: speed.I will generally have corps made up of 3, 6, 9, or 12 units with their appropriate generals(Major, Lieutenant, General, or Field Marshal). Make sure to have HQs to overcome stack penalties, but only place them in corps with a general or field marshal.Depending on what nation/strategy I am playing, I will either mix or isolate my armored/motorized units. For example, when playing Germany and you want to perform blitzkriegs, stagger your speed units across provinces and have infantry to back them up. This way you can pierce into enemy territory with your speed units and perform encirclements, but your slower infantry is right behind to fill in the provinces your speed units take.But if you want to make a mad dash for a particular strategic target like key provinces with victory points, large industrial areas, or capitols, then group your speed units together and bog your enemy down elsewhere with your infantry.As for attachments, maybe I'm stuck on HOI2 mentality, but I find Anti-air, Anti-tank, and Engineer worthless.

I stick with Artillery, Self-propelled Artillery, Armored Car, and Tank brigades. I like all arty-inf corps to break a front (when I can prepare), really messes them up, then throw in fully fresh tanks just as they break and bum-rush for the rear.I'll often prepare a sector with mostly plains as an arena with these, do a quick grab and destroy of trapped units.

That area becomes unsettled and as they approach again repeat the blow. Keep doing this, and suddenly the entire front is weaker.Always groups of 3 for the mobiles (2 tanks + mot, or 1 tank + 2 mots). Always with SPART. 3s and 6s and 9 for the infantry. HQ separate.

' by Source. Licensed under Fair use via Wikipedia.The server is up and running 24/7, and anyone can use it at any point outside of scheduled events. You are not required to be on the while using it, but it is advisable(You will also find the server password here). Standard settings are All Kits Available and Always Valid Placement, which removes restrictions for kit access and FOB placement. I usually default the map to Chora, but can change the map by request on Discord(May require server restart).Scheduling an event: Anyone can schedule an event, as long as there is a free time slot.

Events must be scheduled at least three days in advance, must provide an overview of the objective(s) of the event, provide information as to what is required to accomplish those objectives, and obtain an admin for the event.Event scheduling template:Event name: This should be a short but descriptive name that allows us to locate and reference any documentation related to the event.Event date: The time(in ) and date(Full month name) of the event start should be listed here.Event lead: Whoever is in charge of the event must be listed by name here. It does not have to be the same person who schedules the event. Event leads must be registered on the.Event objective: The event organizer must provide an overview of the purpose of the event.Estimated time: Up to three hours can be allotted for any event without authorization. Anything beyond that must be authorized on a case-by-case basis by lead admins.Participants required: The event organizer should list the minimum amount of participants they think they require to complete their objective. Regardless of whether they have a group of friends ready or rely on volunteers, this must be listed.Server settings: The event organizer must list what maps and server settings they require for the event.Exclusive use: The event organizer must state whether they want exclusive use of the server for the event duration.

This means they can remove anyone not participating in the event from the server, and set an event exclusive password(Provided to admin at least 1 hour before event start).Admin: Every scheduled event requires an admin to be available(Not necessarily present) for the duration. Event organizers are required to obtain an admin for their event within 1 day of having scheduled the event(At least two days before the actual event). If the event lead or a participant is an admin, they must list themselves.Leading an event: As the event lead, you are responsible for the smooth running of the event. This means being able to effectively communicate your needs to your participants and ensuring that the event objectives are fulfilled. You must make sure that the requisite amount of participants are present, that they are informed of the objectives, that the admin is available, that server settings are correct, and that the event stays within its time frame. You should have a detailed plan of how to accomplish your objectives, which should also be provided in the post-event report.Participating in an event: As an event participant, your primary role is simply to assist the event lead. This may include sitting around for long stretches of time, constant repetition of an action, and require discipline on your part in terms of comms silence, fire discipline, etc.

While the hope is that events will provide some fun and enjoyment, it may often have stretches of boredom depending on the event objective.Post-event report: The event lead must provide a written record of the event after its conclusion, reporting what the objectives were, how they were accomplished, and what the results were. A picture or video record is also helpful. Until a report is filed, you are not allowed to schedule any other events. If a report is not filed within two weeks, you will be banned from the server.Note that while this may seem a little daunting at first, the organization and documentation requirements are entirely proportional to the scope of the event itself.

If the event is something as simple as 'I want to see if I can snipe someone from a gabillion km away', that already serves as your objective overview, and your post-event report would be something like 'Yup, I hit him, and this is how high I aimed, and this is how much I lead the target by'(Also note that you probably don't have to schedule an event to try this out).:PI will provide examples for both scheduling events, detailed event plans, and post-event reports at a later date.Outside of scheduled events, the server is available for use to anyone. Do your own thing, try out your own stuff, and leave other server users to do their own thing. Spend your time building FOBs or whatever, but don't get attached to them. We will try to keep the server on the same map outside of scheduled events, but if nobody's using the server and someone requests a map change, we won't care about the SuperFOB you've spent three days building.Server rules: This one's pretty simple.1. Follow admin instructions.2. During events, follow event lead instructions.3. At all other times, don't be a shithead.

Division

If you're not sure if action X makes you a shithead, don't do X. Admins will destroy you with extreme prejudice and not give a single justification because they're not required to.Server Password: The server password will be updated weekly(Updated on Sundays), and is posted as the channel topic in the Discord #serverpassword channel.Discord Server: This is the main hub of the Squad Skunkworks. It is used for planning, discussion, and events. When joining, you will only have access to the lobby, and you must PM an admin to get greater access.Steam group: There is also a that you can join.ADMINS NEEDED: Both the game server and Discord server requires more admins and moderators. Send me a PM or jump on Discord if you're interested.Original post:A live battlefield isn't always the best place to start testing out your new and fancy theories or messing around with the construction feature, so I thought it would be a good idea for players to have a way of getting together with the explicit goal of doing just that.

Division

29th Infantry Division Records

The point of this is two-fold:1. Evolving the meta-game: The main objective of the skunkworks is simply to test out anything from the mundane to the crazy.

Want to find out how to effectively direct the fire of a grenadier firing without a line of sight? Want to build the tallest tower possible?

Want to test a simple infantry maneuver? Shoot all the things at all the things? Check the ballistic trajectory of an RPG over extreme distances? Anything and everything goes.2. Breaking the game: A side-effect of doing all kinds of weird and crazy stuff is that you come across bugs, exploits, and other things that can break the game. Identifying and reporting these will assist in the development of the game.Looking for server hosting: We need a server on which to do our testing. I'm not sure yet if there will be set dates(Weekly) or if it will be more of an on-demand thing('Need 5 guys this Wednesday'), that's a discussion that will have to be had depending on the interest this generates.

29th Infantry Division United States

The server would not require a large population cap and would not have to be dedicated to this one thing.The only requirement for participation is that you help others in their testing. Myeah, steam community is down at the moment cause of none social life having hackers. Myeah, steam community is down at the moment cause of none social life having hackers.

29th Infantry Division Darkest Hour