BEE2: Fixing 60's Style Compilation Errors

Let's dive into this issue where the 60's style in BEE2 is flat-out not working, guys. We're going to break down the problem, analyze the logs, and figure out a solution. This should help anyone else running into similar issues with BEE2 and custom styles.

Understanding the Problem

So, the user is experiencing a critical error when trying to compile a map using the 60's style in BEE2. Specifically, the default room isn't even working. This suggests a fundamental problem with the style's assets or configuration within BEE2. The error message in the logs points to a map leak, which is a common issue in map design where the map isn't fully sealed, causing the compiler to fail.

Key Information from the Logs

The provided logs give us a ton of information to work with. Here's a breakdown of the important parts:

• BEE2 Application Version: v4.46.1
• BEE2 Package Version: v4.46.1
• Operating System: Windows 11
• Error: A map leak was detected during the VBSP compilation process.
• Leak Coordinates: Several coordinates are listed, all in the vicinity of (832, 770, 62). This is a crucial clue to the location of the problem.

The error message itself is quite helpful:

Error message: TransToken(namespace='', orig_pack='', token='{msg}\n
{list}
',
parameters={
    'msg': TransToken(namespace='', orig_pack='', token='This map has "leaked". This is a bug in an item or style, which should be fixed. The displayed line indicates the location of the leak, you may be able to resolve it by removing/modifying items in that area. Please submit a bug report to the author of the item so this can be resolved. Leak coordinates:', parameters=srctools.EmptyMapping),
    'list': JoinTransToken(namespace='', orig_pack='', token='\n', parameters=srctools.EmptyMapping, children=[
        TransToken(namespace='', orig_pack='', token='\n{text}\n', parameters={'text': '(832 771 62.75)'}),
        TransToken(namespace='', orig_pack='', token='\n{text}\n', parameters={'text': '(832 772.25 61.5)'}),
        TransToken(namespace='', orig_pack='', token='\n{text}\n', parameters={'text': '(832 771 -1.25)'}),
        TransToken(namespace='', orig_pack='', token='\n{text}\n', parameters={'text': '(832 770 -1)'}),
        TransToken(namespace='', orig_pack='', token='\n{text}\n', parameters={'text': '(832 769 61.749996)'}),
        TransToken(namespace='', orig_pack='', token='\n{text}\n', parameters={'text': '(832 770 62.75)'})
    ], sort=False)
})

This clearly states that a leak has been detected and pinpoints it to a specific area of the map. It also suggests that the issue might be a bug in an item or the style itself.

Diagnosing the Map Leak

Map leaks occur when the VBSP compiler can't find a sealed