Note that if you have a large CC3+ maps and just need a section of it in higher detail, you can use the rectangular section export option, this allow you to export that small section in the same size as you would normally do for the entire map.

That's a sheet order issue.

It's easy enough to fix, but if you are brand new, you may be unfamiliar with some of the procedures.

There are basically on of three things that can be wrong here, and I can't see which just from a picture

• Either the coastline is on the wrong sheet
• Or the mountains is on the wrong sheet
• Or the sheets are in the wrong order.

To check what sheet something is on, you can use the List command (From the Info menu) on the shoreline and mountains to figure out what sheet it is on. Note that you'll probably have problems selecting just the shoreline, as the landmass is also in the same position. Usually, you can just look at both of the, in the list output and determine which is which, or you can start by temporarily hiding the LAND sheet so entities there doesn't get in the way.

That looks like a cc3 standard overland style map, so here the coastline should be on the COASTLINE sheet and the mountains on the SYMBOLS sheet. If that isn't right, you'll want to use :CC2MCHANGE: on them to move them to the correct sheet. (Note that if the mountains are on the wrong sheet, you'll want to move all of them, not just the ones crossing the shoreline)

If they are on the correct sheet, it's probably the sheet order. :CC2SHEETS: can be used to rearrange these. Basically, what you want to ensure here is that COASTLINE appears higher up in the list than SYMBOLS.

a) This is a bug that happens rarely, but do show up every now and then. The fastest way to fix it is to just use :CC2KEEP: on the existing wall, the erase it, and then draw a new one with the :CC2PATH: tool. Note that the dungeon corridor tool adds a little notch of wall at the end there, overlapping the meeting perpendicular wall, this is to get a full corner there.

b) Not sure. I didn't have any problems at all placing a door and cutting the room there once I turned off snap. If you have trouble with the behavior though, the workaround is to :CC2BREAK: the wall manually instead. (Hide the floor first to make sure you work with the right entity)

If it is just things getting to dark in the shadows, maybe consider just lowering the opacity of the Wall Shadow effect instead of trying to add point lights?

The point light system is a completely different way of creating shadows, and doesn't work with the well shadow effect. Which means that if you want to use it, you can't just set up a light source in the dark corner, you have to properly set up lighting for the entire room.

If you're looking for something in particular, the atlas is fully searchable, although there are no search option for interesting locations though.

To pick a spot, find some feature on any map that looks like it could hold a dungeon. Could be a cave, or a ruin, or a building (both on the overland map or a city map)), or perhaps there are some stairs or holes in another dungeon out there that may lead to yours?

And note that the mega-dungeon always could use new levels. It is already a crazy place with levels completely different from each other, making it a good place for anyone just wanting to make a dungeon level without looking for a specific location in the atlas (Just remember that mega-dungeon levels should have exactly one entrance from above and one exit going down so they can be linked in a long chain.)

Exactly. Tokens are used on a map during play, they aren't normally part of it (except as the odd decoration). Downloading a png map image from the atlas with tokens pre-placed in the image would make it useless as a battle map.

I guess if all the tokens are placed on their own sheet that can be hidden, and I am notified of it during submission, I can set up one of my toggles in the nav menu. That way the map can be displayed without tokens by default, but users of the .fcw can hit the link to show them.

No, that's actually a very different issue (but somewhat also related to time). You may remember the old version of vanilla used whispers embedded in the discussions themselves, a feature not available in this version. But those whispers caused the read counts for those threads to be off when they were removed from the discussion and turned into PM's during the upgrade process to this version of vanilla. It affects all discussions that contained whispers, but it works itself out for active discussions as people continue posting in them.

To add to Quenten's reply, you would do that by using the regular :CC2MCHANGE: command.

What you see there is what is commonly referred to as transparency acne. It happens because the way the effects processing engine looks for edges to apply edge fading on is to look for changes from the previous sheet. But if two overlapping pixels are the same color, that causes the effects engine to see it as no change, and therefore a spot to apply edge fade to.

The common way to work around this is to create a new sheet just below it in the sheet order with the same effects on it, then make a copy of the entity on that sheet, but change the fill to a solid color guaranteed not to appear in the textures, such as pink. You might want to make the sandwitch entity a little smaller than the actual one, to make sure you don't get a pink glow at the fading edges. You could also use a colour that is more similar, but you must be certain it's not found in either the sheet above or below.

Welcome.

You can click the :TOOLSICON: button to change the toolbar button sizes.

Don't hesitate to post if you have any questions.