tain.totalcodex.net

Thanks for those really kind words, pompey. In my opinion, the Myth community still has lots of things to look forward to for many years. No one is exactly sure what though.

Gleep, to address some of your mapmaking problems:

If I'm not mistaken, it's not Fear that only allows you to view 1024 tags in a given folder, but operating systems in general. If you were to make a folder on your desktop and drag more than 1024 files into it, basically, the same thing would happen. Obviously, it's outside of Magma's purview to change how file structures work, but there is a way to set up Fear so it doesn't read any of Bungie's foundation tags, and only what's in your local folder instead - hence reducing the number of tags in a folder to below 1024 and making them all viewable.

Two problems with this. The first is that if any of your local folder tags rely on or are connected to stock Bungie tags, you can easily make a big mess. The second problem is I don't remember how to do it. ozone knows, however, and I'll try to remember to ask him.

In the meantime, the simpler solution, as taught to me by Silicon Dream, is to make a seperate folder called "extra projectiles" or something and temporarily dump any projectiles you absolutely know you won't be editing during a Fear session. Take care not to temporarily dump any projectiles that are connected to other tags that you'll be editing. For instance, if you open a projectile group tag and hit "okay" (as opposed to "cancel") and that projectile group tag connects to a projectile that's missing from your local, you could screw things up. Anyway, it's really not too hard to work using this method. I certainly got used to it with Mazz V.

On a side note, has anyone run into a problem where projectiles start going weird like turning black or not rendering right? I've had it happen recently and its usually in lpgrs, which are at the limit. It may tie into my bug that apparently is related to player count and color indexing. Is there a plan to raise the memory storage for indexing colors? I know on big plugs like UTB, and my map Dream of Death colors get wild and arent assigned right, and I think that its causing the crash on my map.

No, weirdly rendered projectiles or lpgr particles I've not seen, so I don't know what that could be. But as far as unit colors not getting assigned right, that usually stems from too many units sharing the same collection. For instance, in UTB Lichen Sluglords, you have regular dwarves, striders, and pathfinders, all sharing the same exact collection. Don't ask me exactly how it works, but the collection references for those three units get multiplied by the number of players in the game, and once it goes over a certain number, the colors get all whacked.

The solution is not to have more than one or two units share the same collection. Easier said than done if you're on a PC and don't know the following little trick. I forget who posted this tip here once (Baak? haravikk?) but I used it for Mazz V just before I release, and I'm so glad I did.

Follow these steps:

1. Hold down Shift while opening Fear. You'll now have access to uneditable tags.

2. Duplicate the collection that you want more than one unit to reference. Close Fear.

3. Your duplicated tag will appear in your local folder. Open it with Tahoe.

4. In the menu, under Collection, hit "Info...".

5. Carefully note what User Flags are checked, uncheck them, and save the file.

6. Open it up again, go back to Info, and recheck the flags the way you initially found them. Save again.

7. Now you can use this collection for a new monster. Make sure the monster, unit, collection reference, and projectile tags for your new monster ALL reference the duplicate collection you just made, and not the old one.

No more weird team color problems. Enjoy.

The Elfoid wrote:How much of the Magma members in map-making AND coding's focus is on the coding side?

William Wallet wrote:You know what would rock? Giving a flying unit the ability to 'not-stand-still' - basically, a plane wouldn't hover. So if someone made a plane unit, it should sort of fly in circles without ever having to set *foot* on the ground!

(I refuse to edit that other post where I sort of, slipped up).

Easier said than done if you're on a PC and don't know the following little trick.

Yeah, that was me. I was just hoping there'd be an easy way to do this internal to the engine, as it appears to still get whacked now and then even when using this trick. (It appears cumulative - i.e. you won't see the player-unit-colors-whacked bug the first time you host a game, but after many games the probability seems to go up). It just seems like some kind of buffer overrun / out of bounds error that causes the player color indexing to "spill over" if so many units use the same collection - odd that it can be fixed by detaching/re-attaching units - and tedious that you have to duplicate collections to work around it.


Gleep-- I think you're right on the player floyning having to do with some odd attribute of the way color hues are handled. I still think the best (and possibly simplest) solution however is a simple checkbox for the host that says: "Don't Floyn Player Colors"