Fixed: 11 below. Great, I've run into this one several times. Thanks Bungie.

26. .gor limit on PCs is 24 18 august

1.3 did introduce the long awaited ability to play 3rd party maps, and anyone who has been on bungie.net the last week knows that interest has been rekindled with several amusing maps. There has come new way of scoring damage, and the BC team bug (24) below is gone, other than that I have so far found no difference. All other bugs/quirks remain. Worth noting is that the 1.3b2 patch does not modify tags.gor or the mesh files, so any map anomalies remain. Berserk number 9 still gets stuck on Dire marsh, and on that same map you can still march your entire army off the field. In the same way the odd sinkhole for balls remain. The most annoying bugs (1 and 7 below) remain. In fact I got an e-mail from Bungie where they say that (1) is not a bug. Well the sheer amount of grief this one has caused, as well as the the fact that it breaks the basic rules of user interface should be enough to qualify it as such. Bahh! End rant.

28. 1.2 films dont work correctly?
I have found a single instance where a film did not playback the same way in 1.3b2 as in 1.2. This is Seven Gates. When viewed in 1.2 it is a win. When viewed in 1.3b2 or 1.1 it is a total loss. This might be a bug in 1.2, not 1.3.
Film - Zipped - Binhexed.

27. Film of which map? Wait, now I know. 6 august
If you want to view a film played on a 3rd party map, any map-specific info shown will be either nothing or that of the previously selected film, sometimes it will be random.
For example: select a film played on Creep, select the film in question, the number of starting positions will be listed as 2. Select a film played on Grave, select the film in question, the number of starting positions will be listed as 5.
see this jpeg. I assure you that the game is NOT StB on Shadow of the Mountain.
Once you have viewed a film of any map, the .gor for that map will be open and the info will be displayed correctly.

26. Correct map, wrong .gor. 6 august
This one will cause a lot of grief, I have already run into it twice. If the host has a .gor file open, and a player does not have that .gor file, the game is red to the player, even if the player has the map. To bypass this, in order to play bungie standard maps, you should as host select None as .gor file.
A common way this bu will manifest itself is if you get thrown out of a game with friends because you do not have the correct .gor file. In the kindness of his heart the host selects a standard bungie map to let you in. But unless he also selects None as .gor, you cannot get in.
Look at these jpegs. Unless you have cloud.gor you cannot enter a game like the one on the right.

The right way. Cant get in without cloud.gor

25. Fog of ball. 6 august
Any ball in the northwest corner of RiP is invisible on the overhead. See this gif.

Why this page? We dont need no stinkin bugs! :-)
Well, Myth, being such a great game, has few bugs. But hopefully this page will help - and encourage - Bungie to fix the last few ones without having to read tons of e-mails. I intend to mail this list to Bungie when there seems to be no new additions.

This page is now in inverse chronological order. Newest on top.

25. Units can attack from afar. 28 june
This is a film of this. It takes 6:25 before anything happens as I try it out. Things happen more and more often as I get the hang of this.
8:40, 11:56, 14:07, 15:23, 16:03, 16:46 and more
Film, Binhexed, Zipped

24. A quitting player takes his BC damage with him. 28 june

23. Mutual destruction games not ending.
In a netgame, if all players gets eliminated during Sudden Death or before any objectives are taken - the game never ends.
A blast. Who won? Can you say forced host drop?

22. Veteran wights accumulate on Dance maps.
From Codex bungie net board.
If veterans is checked, surviving wights gets added to the next game. Up to 4 in number.

21. Scoring anomalies. (Not bugs but people need to know about this)
Body count displays but ignores fractions.
If a game of territories or captures at any time results in one team owning all, sudden death kicks in and the clock is ignored even if the sudden death is resolved before the original time runs out. This means that if your opponent ever controls all flags, you will have to contest a flag at all time in order to win.

Entries below this line has been mailed to Bungie

19. Detach problem
Poena Dare reports:
How do you detach units to player #11? Check this JPEG.

18. Lines do not stagger with even number of units.
Pond Scum reports:
If you choose a even number of units (such as archers since this really needs to work for archers), formations 3 (Loose line) and 4 (Staggered line) turn out to be exactly the same (Loose line).

17. Captain leaves, team stays.
If your captain drops during the game, and you get back to the game room, you are part of a non-existant team. (Surreal)

16. Save and Film folder limit.
Open dialog only shows a 100 files, even if there are more. (Not quite a bug, but annoying)

15. No error message if diskspace runs out when running.
If the game cannot write its "submesh cache" file, you either quit back to start screen or get large chunks of strangely colored squares on the map (Screenshot).

14. No error message if diskspace runs out when saving files.
You just get corrupted files.

13. The cutscenes become blurred on slower machines.
Bungie says its on 2x CD's but it also affects slower machines.
Workaround of sorts.

12. Five champion script error.
Poena Dare reports:
Alric can be awakened on five heroes by damage. This is documented on The Journal's Easter egg pages.

11. Hidden teammate selection
If you select a teammate and press Join Team, the selection goes invisible.
This is very annoying because you might think that your next chat line will be broadcasted to everybody, but it will only go to your teammate.

10. On the Mac, films don't show up correctly on the desktop.
The films are saved with the type "RECO", but there is only an icon for "reco".
(For PC owners this is like having a file with .TXT instead of .txt)
Workaround: Open Myth with ResEdit, open the BNDL resource and change the "reco" to "RECO". Save and rebuild the desktop of your Myth drive. (Press option and Command while restarting)

9. You can kill your teammates. (Not tried this yet.)
Alienate #CP#J reports:
Shift-Clicking on enemy units will also have your men kill your Team-mates guys.

8. Start ranked games with less than 4.
Electrofryer reports:
When hosting a ranked game, "Start game" is activated when 4 people are in the room, but it does not get deactivated if the number of players drops below 4.
Addition by Earnur:
The game wont count if played by less than 4. (Thanks. So much for laming using this).

7. "No password entered"
Traxus VR reports:
If you try to enter a passworded game that has been restarted, you get the 'game requires password, but none was entered' dialog.

6. Foreign keyboards not supported (not quite a bug)
Zydeco reports:
Myth does not support the keyboard layout switching scheme of the PC or MacOS Because Myth doesn't support keyboard layouts, I find it frustrating to chat on bungie.net and IMPOSSIBLE to be a decent captain in a game of Myth. This may also affect some people with foreign language systems.
My comment: Myth thinks all keyboards are US keyboard. The key mapping is strange, but works, just assign a key to detach and it will work.
Workaround: If using a foreign keyboard, the first thing you do should be enter Preferences - Configure controls... and set the keys to those of your choosing. If a key is not a normal letter key - that is when the key is identified by Myth with a long text - ignore what the settings say and just remember what key you used.

5. Typing gets aborted. (not quite a bug).
MaGStaff reports:
Everytime I'm playing a game, and I'm typing something, if one of my units die (and I can see that unit that died in the camera) it erases what I typed, and I have to retype it. It's even more annoying if I've got my wight selected, and then another one of my units dies while I'm typing, and I press a "T" right after it erases what I typed.

4. Map anomalies.
Reported by DeusExMachina among several others:
A berserker often gets stuck on Death in Dire marshes if you start in the north-west corner.
Workaround: Never get more than 8 berserker if you start in this corner.

ThorulfR reports:
A berserker can get stuck on the Watcher, see this film.
There was a film on one of the big sites where the bacon dissappeared on Creep.

Alienate #CP#J reports, the Dire map lets you push or blow the ball off the map.
ThorulfR: Larger things can dissappear to! Here is a film where a Trow walks off the map (binhqx) (zip) I told him to go east from the northwest corner and he decided that the shortest route was outside the map. Or maybe he just tired of my whining.

Poena Dare reports:
Mudpit Massacre (Dark) has a few places that 'eat' soulless on the map edges. (I have seen this, but as yet unable to recreate it on 1.2)

Butcher reports:
I have a film showing Bacon on Grave where the bacon falls right through the mesh.
Here is the film. Just the verbal argument between Loki and Butcher is worth the download.

Download
Binhexed
Zipped

The fallthrough occurs when it is 1.53 left of the game, and then the balls warps between positions below the mesh for a while.

ThorulfR reports:
I have had a spider fall through the mesh on Grave.It happens when it is 5.34 left of this film.

Download
Binhexed
Zipped

3. Myth will try to delete films that it thinks are corrupted.
If it cannot, myth will enter an endless loop. For example if the file is locked. Try this one, binhexed zipped remember to lock it. If you could view it, it would show a ranked game with a lamer. Game killed with 2 secs left.
Here's another one. Binhexed. Zipped. This one is weird. It can be opened and viewed on 1.1, but the above bug kicks in on 1.2. Dont forget to lock it.

2. Legendary saves can get out of synch for no appearant reason. (This ones weird)
I have saves played entirely on 1.2. Opening them results in an Out of synch message. Sometimes reopening the same save will result in no out-of-synch. And opening them on 1.1 often works. Check this saved game. Binhqx. Zipped. It was played entirely on 1.2. If opened on 1.2, it shows out-of-sync. If opened on 1.1 it works ok.

1. Preferences difficulty overrides that of a game.
The New game setting is ignored. Also an ongoing campaign started on legendary and continued at a later date will continue at the preferences settings, not the setting of the last played game.
Example1: Your preferences settings says Timid. Start a new game on Legendary. The game will be played on Timid.
Example2: Your preferences settings says Timid. Open a legendary save. The next level will be played on Timid.