Robert Olesen
-
Posts
616 -
Joined
-
Last visited
Never
Posts posted by Robert Olesen
-
-
Well, column "5" (N) in the core force sheet should do this for you, though it only affects individual units, not the point total of the available units for the battle. Just clear the OK in that cell for the units that don't participate (and remember to set it manually for the coming battles when required, as you now deleted the formula). The only two values this cell is allowed to contain are "OK" and "" (empty).Originally posted by Ardem:What would be really helpful for me is in the spreadsheet is a did force participate in battle Y or N Column if N then no experience is calculated to the force, should be easy enough.
-
Ardem, I'm not quite sure what it is you're asking me to do.
But it seems to me that the simplest way to do something like you're doing is to keep two spreadsheet series - one with the full battalion and one with the units you use in a particular battle. Just roll the before battle dice, copy the full sheet and delete the units you don't use (this will presere all the extra info you need, like intermediate die roll results). You'll then need to transfer the battle result back to the full sheet and it'll give you some problems moving from battle to battle, but you can probably handle that. Actually, you can simply roll the after battle dice in the sheet you used for the battle - there are a few die roll modifiers that depend on core force size, but that's not too significant. Than when you're all done, copy the core force info after the battle to the full sheet, reset the date, clear the dice and start over again.
That should work reasonably well.
But be aware that the battle size is dependent on the size of your core force so it may change once you reduce the core force by deleting some of it.
Also take a look at the Auto sheet. Unprotect it and play around with some of the die roll modifiers - that should give you the intel effects you want. But be careful not to delete any of the formulas I made - better to use an empty cell for an intermediate calculation and add the result into an existing modifier. Or unlock some cells and use them to manually input some die roll modifiers. The gray cells are useful for this.
Also, the Raid die is in E6 of the Auto Sheet. A roll of 6 converts an Attack or Hold operational order to a Raid.
Was that helpful?
[ November 30, 2004, 01:13 AM: Message edited by: Robert Olesen ]
-
There is a minor error in v2.21
Cell K59 of the Tables1 sheet should contain the value -1, not -2.To change it you need to unprotect the sheet (Tools > Protection, it has no password). Remember to protect it afterwards in order to avoid accidental overwrites.
-
The dice rolls are most definitely not rigged, nor does the AI take the spreadsheet into account when making it's plans, so I guess that leaves paranoia :eek:
Welcome Ardem, I'm glad you like it
-
[shameless plug]
clifford1944, once you get a feel for the game, check out my campaign (in sig).
[/shameless plug]
Actually, it really is a good campaign system - playing against the AI not against humans.
-
Good question. I guess the shell has to be propelled by an explosion in order to travel as far as it does - but it doesn't seem to be a big/loud one. I have never been close to a mortar while it fires off shells.
-
You buy your support in the QB setup and there you can pick any quality that's available (which depends on the battle setup).
There are a few other units thar aren't really support units, e.g. the exploiting force. You by these in the editor and the rules specify a quality for these. But I don't thnk these are the ones you're talking about.
-
Exactly. So there's most likely some difference. But what it is is probably hard to find out.Originally posted by Akula2:I don't think I've ever seen steppe in Finland though. :confused:
-
Hmm, you may be right there. Pyewackets tool does work from the editor.
-
Yes there is. Check out Pyewacket's map converter. It can also be used to copy maps from CMBB to CMBB. Check the whole thread - the tool has developed a good deal along the way.
-
Thanks, Krautman. I get lots of praise (e.g. just take a look at the first post in this thread
), and I'm glad that I do. It tells me that I'm not the only one with a need for a tool like this. -
v1.12 is out. I found a serious problem:
Spreadsheet error corrected: You could not issue commendations in the spreadsheet because the cells were erroneously write protected.
I also updated the suggested campaign files.
-
Version 2.21 is out. It contains a spreadsheet correction, the rules are unchanged:
You could not issue commendations in the spreadsheet because the cells were erroneously write protected.
-
-
Oh, and that bonus is ony for the officers (HQ units in CM). Those are the ones that should have HQ in the unit name. It's in the rules: Section 5.8.2 and a somewhat difficult to find entry in 3.7.5
-
Oops
You need to unlock those cells. And to do that you need to unprotect the sheet (Tools > Protection). The lock setting is in the last tab of the "Format Cells" dialogbox.
You should protect the core force sheet afterwards to protect yourself against accidental overwrites of formulas.
Sorry about that. I'll get an update up as soon as I can.
-
-
OK, let me try again. Assuming you're using the spreadsheet.
You'll download a rules file (or two) and a spreadsheet (perhaps an example spreadsheet as well). Make a folder for the ROQC rules and stick them there (or put them anywhere you like).
When you start up a campaign, I recommend making a folder for that (I like to keep things clearly separated). Copy the spreadsheet to that directory (not the example, the one called e.g. ROQC_CMBB_Sheets_2_20.xls). Rename it to a name suitable for your campaign. I suggest numbering it because you get one of these for each battle, e.g. it could be MyCampaign01.xls
You'll also have a core force .cme file for each campaign - this one will be updated after each battle and can be kept wherever you like. I tend to use the Quick Battle Maps folder. This file is included in the suggested campaign downloads. You'll have to make it yourself if you're playing another campaign.
Finally, there'll be a .cme file for each battle - you can choose to keep them or to overwrite at each battle. I tend to keep those in the Quick Battle Maps folder as well, as they're to be imported when you set up a Quick Battle. These files are copies of the core force file - the rules explain this. The point of this file is that it allows you to tailor the core force to each battle while the core force .cme file contains the full core force.
Is that more clear?
-
Deathsai, here's a short explanation. It may not be enough, tell me if you need more. Also, the CMAK campaign rules have a better getting started guide.
The installation is really easy. Let me repeat the rules:
Oh, btw., these installation tips sort of assume that you're using a PC, not Mac. I'm not familiar with the file structure on a Mac.I recommend making a directory for the rules and the original spreadsheet, and another directory for each campaign.
Copy the spreadsheet to the campaign directory and rename it to reflect the campaign and the first battle, e.g. Schutz01.xls. You can then increment the counter when generating a spreadsheet file for the coming battles.
There are two other files that you need in a campaign. Both are CMBB scenario files (.cme): The core force file and the file used to setup each battle. In the example, I have named them Schutz_core.cmg and Schutz.cme (which means that they are overwritten from battle to battle, as the battle number is not used in the file name – but that’s up to you ofc.). I usually keep these in the Quick Battle Maps directory, but you can in fact keep them wherever you want, as you can browse your way to them from within the editor when you need them.
-
Hi Krautman, glad you like ROQC.
Alech is correct. It has to be the first unit in the list and the name in the "Unit Type" column has to contain the phrase "HQ", e.g. it could be
Company HQ
or it could be
Hauptmann Krautman (HQ)
or whatever you feel like as long as it contains HQ.
The commendations are specified in the core force sheet column labelled 29, just type in 1 or 2 for the unit(s) you want to give these to. I guess the rules could have been clearer on this (section 5.8.4 page 63).
Send me the spreadsheet if you can't get it to work.
-
Interesting point. It is a bit complex to get done right, however. Should it apply only to the AI, not to you? Is it a function of battle type, not operational order? And the weather is random, not controlled by my rules. I need to give it some thought.
-
Had to release version 1.11 for CMAK because I got a relatively serious bug report.
Changes from Version 1.10:
The “Always Fight with Own Division” option didn’t work in 1.10.
The British division type availability table corrected.
I have not had time to update the campaign examples. Get it at http://www.roqc.cdgroup.org/
-
-
There's a small error in the British division type
availability table, the row for December 1942 is
missing.
You can find the correct table here:
), and I'm glad that I do. It tells me that I'm not the only one with a need for a tool like this.
Questions about RobO's Campaign Generator
in Combat Mission: Barbarossa to Berlin
Posted
Yes, that's column 5. And you probably sjouldn't have to set the number of men to 0 if you use column 5. Though I could be wrong there - not sure of any side effects, this haven't been tried before. I still think the safest approach is to copy the full spreadsheet for a given battle and then delete the men that aren't in the battle.
No, you haven't used up your allotment of questions, but I don't understand this one - what difficulty modifier?. The enemy force handicap is a result of one of the two difficulty die rolls, it is not used as a die roll modifier in itself.
That web page looks good - except that there are no links in the Links section
I'll add a reference to it on the ROQC site. You should post your rule changes on that page as well.
Btw, did you send that email? I don't think I got it. Give it a recognizable subject when you do so I don't mistake it for spam.