Guild of Writers

Probably the sound is just triggered first, starts faster, or something equally innocuous. It's obvious they are not in sync. I've always had relatively slow computers with underpowered video cards. Maybe on a really fast system it's not as noticeable.

The rain always worked that way for me (since 2007). It was always heard before it was seen.

Besides satisfying some human need for competition... nothing at this moment.

Then again, why play fantasy sports games if you don't get any exercise?

Edit: And as Deledrius hinted, this shard is a WIP and who knows what the future holds.

Actually I do agree with Tweek and Christopher. Ages should be held to the high standard from the artistic pov. My only problem is that, without live content to drive events or some storyline or puzzle to figure out, the Age is just a pretty museum piece worthy only for a visit to see the sights ...

"Wow! What a beautiful Age! What can I do here?

>"You can walk around and admire the clever texturing of the walls and floor... notice the reflective sheen of the stonework.

"Yes, but what is the story line? Are there any puzzles to solve or goals to accomplish?

>"No but observe the detailing in ...

So, is it that Cyan tends to focus more on the artistic aspects of their games to the detriment of gameplay? Too bad... no fan ages for MOULa unless they are pretty enough, I guess.

I've rewritten and tweaked the code every way I could think of but...

Although I managed to trick the script to make the losers know that they lost and to go execute the endgame code, the loser client always crashes. I can get either the yellow or purple team to win the game.

Using the ...

ok, thanks again. back to tinkering with the code...

Progress (sort of). I disabled the OnTimer() code and ran a test again. As soon as the south team won, the north team client crashed and I got the same drifting view of the wall room when I should have linked to the nexus. For whatever reason, I switched to 1st person view and, lo and behold, I was ...

I'll mess with it a bit to see if I can find where my code logic fails. Time to enhance all the new debug statements I added to be less cryptic. Now that I know the intent of the OnTimer() code, I can put it in my back pocket and use it if it's still needed.