Battletech BattleTech discussion thread: May the light of Hanse Davion guide us

Jormungandr said:

....I really, really need to learn how to properly art, since Zerg-infested Battlemechs would be a kickass crossover project.

You've seen Infested Terran units like Marines? Scale it up to Battlemechs.

Click to expand...

The Whispering Monk said:

Legend of the Black Marauder

"The Black Marauder resembles an MAD-3R Marauder with flat black paint, although its shape supposedly looks somehow "wrong" and its "proportions not quite right", too sleek yet of terribly imposing bulk and with too-smooth angles. It has no serial number and no other factory markings whatsoever.

Its presence seems to grow larger when sight is obscured by darkness, fog or smoke, incidentally circumstances in which it seems to perform markedly better.

In some instances the 'Mech was—always inconclusively—described to move in ways that are impossible for a Marauder (or any 'Mech), including one tale where it was said to have turned its "head" by bending its long snout just forward of the arm joints and revealed a maw with rows of serrated teeth."

Click to expand...

Jormungandr said:

Huh... was this made before or after Starcraft became a thing? 'Cause it looks like someone was a fan of Starcraft, haha.

Edit: Though, a Chaos-infected machine makes more sense, if it's older. Looks like a Daemon Machine.

Click to expand...

Jormungandr said:

Huh... was this made before or after Starcraft became a thing? 'Cause it looks like someone was a fan of Starcraft, haha.

Click to expand...

ShadowArxxy said:

Honestly, it comes off as more generic eldritch horror tropes than anything specifically Starcraft or 40K.

Click to expand...

PsihoKekec said:

Click to expand...

Spoiler: Sample map from the generator with Inkscape touch up

import openpyxl

# Define the dictionary with abbreviations and corresponding lists of strings
abbreviations = {
    "abbr1": ["string1", "string2"],
    "abbr2": ["string1", "string2"],
    # Add more key-value pairs as needed
    # Ref: "abbr1": ["string1", "string2"],
}

# Load the workbook and select the desired sheet
#file_path = '' Replace with specific file path
file_path = 'Systems By Era.xlsx'
workbook = openpyxl.load_workbook(file_path)
sheet = workbook['Systems']

# Iterate over each row in column B
for row in sheet.iter_rows(min_row=2, max_col=2, values_only=False):
    cell_b = row[1]
    if cell_b.value:  # Check if the cell has a value
        # Search for each value in the dictionary
        for abbr, strings in abbreviations.items():
            for string in strings:
                if string in cell_b.value:
                    # If found, change the corresponding cell in column Y
                    col_y_index = openpyxl.utils.cell.column_index_from_string('Y') - 1
                    sheet.cell(row=cell_b.row, column=col_y_index + 1).value = abbr
                    break  # Stop searching once a match is found for the current abbreviation

# Save the changes
workbook.save(file_path)

1. Manually create your new faction entries on the Factions sheet. Required data: ID (abbreviation), name, associated color (hex).
2. Make a list of the planets you want for each faction, and DOUBLE CHECK THE SPELLINGS. The script uses exact matches, so if you typo, planets will NOT change factions.
3. In the abbreviations section of the script, put your list(s) into this format: "abbr1": ["string1", "string2"], . This will allow the script to cycle through all planets associated with a faction, then through a list of factions.
4. Set the file path to the Systems By Era spreadsheet - use \\ in a places where a \ would normally go.
5. The script is set to handle 3025 by default. If you want to change any era besides 3025, go to this line and change the value Y to the value of the appropriate column:
   col_y_index = openpyxl.utils.cell.column_index_from_string('Y') - 1
6. Execute the script.
7. Open the spreadsheet and do a manual save. (When I ran the script, it seems the file changes trigger Excel to load a recovery version.)
8. Do a test render to check if all the intended changes appeared.
9. If not, find and correct typos in the script or manually fix the specific entries in the spreadsheet.