[Ashon]

We've been having a discussion about how we want to code our weather system for our project.  And we've got some great ideas (reposted here) but i was wondering how everyone else was doing their weather systems?  are they just the normal blah ideas, or are they something unique and special?

[b][u]The WM weather Engine:[u][b]
Each room has a terrain type, and x-y-z coordinates, from these we determine a couple of facts, first off the organic density, which is based on the terrain type, the y coordinate (latitude) and the z coordinate (altitude).

Then we find the water content, by using a LOS type of algorithm we find all the available water sources around.  This is used for the evaporation/condensation part of the weather.

Mix in the Jet stream map which overlays the world map, and now we have movement to our weather system.

In the next step we meld everything onto the day-night/time/temp sine-wave and adjust for the season, and the weather is taking care of.  The system calculates the humidity, the cloud conditions the tempature, the relative tempature, wind and so forth, and creates room objects for each room that takes care of all the effects.


what do you guys do?

[ScourgeX]

[Kallian]

For weather movement, a stat for barometric pressure is given to each room and then averaged into the region's pressure.

Storms are objects (a non sentient npc that can grow, shrink, and occupy many rooms simultaneously, actually) that move and flow according to surrounding pressures.

Humidity is on my to-do list.

[mhc]

We simply ignore any global weather, and let the different areas do their own thing.

[Ashon]

Why? There's no consistency then. While I can understand that some areas should always have a dark cloud around them, or should always be raining for mood and whatnot, why shouldn't there be a global weather system?

[Dre]

Heya all,

Of course a global weather system is cool, but mostly an area determines a different place with all their own weather, in a desert it won't rain fast and so why not just put it in their own system?

Maybe it's easier to just relate some zones into one system, so two forest next to each other will have some kind of weathersystem, but the desert that lies to the south of it will have it desert specific weathersystem.

Although I must say, that Ashon's weather system sounds really neat. Although I wonder what you will do when you add an area, you have to change the whole map everytime, including the jetstream etc?

Greetings Dre

[Ashon]

See, that is part of the problem Dre, is that areas need to be done logisitically. Forest do not exist under any circumstances next to a forest. There is area inbetween the forest and the desert.

A global weather system takes intelligent design issues to deal with. You have to design the world before you can build the world. Just like you have to design the area before you build it.

But regardless in response to how my own projects system handles it: New areas are created dynamically. The world engine creates new parts of the world. An island may appear off the coast, or an ancient tower may appear in a forest. I like to call this undiscovered country. Players may have travelled an area, but that doesn't mean they've discovered the entire area.

This system incorporates the adjustments to the jetstreams, and since it is just a algorithmic function f(x) to draw the jetstream on top of the exisiting map, but adding a new location (x,y) the function simply adjust the jetstream slightly.

The main problem with this would probably be system resources. Calculating jetstream patterns, rainfall patterns, temperatures, relative temperatures, cloud cover, wind speed, wind direction, ammount of sunshine, fogginess, etc, for EVERY room in the MU* simply can NOT be very resource-friendly, especially if you consider it also has to run the rest of the MU* with it. For a frame of reference, modern day weather-forecasting supercomputers have 320 GB of RAM.

[Ike]

It is very impressive that you have calculated such a complex system. However, I am a fan of just allowing each area to have it's own weather system.

- I do enjoy noticeable weather in games though. On most muds I play, when "lightning crashes in the sky" I could frankly care less. I prefer for "lightning to crash briefly illuminating the objects around me".

[Ashon]

It's no more complicated then most systems on a mud, and not as big of a resource hog as people would like to think.

Imagine the weather being as a group of mobile's. It moves from room to room. Either picking a flower or whatever, the mobile needs to know the room, what is around the room etc. The weather object needs to know the conditions of the room, and simply affect the room like a mob would. It then sends an update to the global system letting it know what happened. If two weather objects meet, then the weather could change drastically, which is where the memory footprint would come in, but it wouldn't be a lasting transition.

This of course is an overly-simplified run-down of how the system works. But it illustrates how non-intensive the system is.

[Kallian]

[Shao_Long]

well, if you'll have a mobile which is constantly moving in every room, it surely would ate a lot of resources, I think...

[Artovil]

Actually, it will not eat resources by just moving about. If that was the case a normal player would eat as much resources, since they are, at least in DIKU/CircleMUD's, the same object type. So just having it/or a whole system of them moving is not a problem at all. What would take time are all the calculations for the weather, which mob to move where, and what it should look like, and so forth and so on, which has already been covered, yadda yadda. My finger actually hovered over the flame button there for a while. You have to be trolling, Shao. Nobody can... *mutes himself*

[OnyxFlame]

[Ashon]

Not yet, but that is the plan. We just haven't figured a system to change the terrain type based on long-term weather affects, seeing as the weather is based on the terrain.

[John]

Wow, that would be complex. I think you'd find that the terrain wasn't changed too often except because of Sapient interaction. Although if you have magic, it would be amazing to play a mud where if fire spells keep getting cast then it has a chance to turn into a desert, which would then cause havoc on the other areas around it, and it would be fun if the entire ecology was nearly destroyed cause of it.

That would be a case of your system is TOO realistic, and some Imm intervention would have to take place in the form of the local temple/kingdom taking action.

Just a question, what's the URL to your mud? I'm intrigued by it now.

[Ashon]

The problem that I see with the changing of the terrain are the constraints that we've decided on to make the system easier to code. First off, the terrain, and organic density are the biggest parts of the equation. Here are my thoughts so far on a system to actually change the terrain: As the weather changes it affects the following components: Organic Density and Tempature.

Seeing as how we just have a skeleton system right now and Organic Density is just a number, I imagine that it would be modified by tempature, becoming more/less depending on the increase/decrease of temp. Which in turn would affect the tempature more...

I suppose that I need to put more thought into what Organic Density means, and should be affected by...

muh... we are still in development and no-where near completion... but if you are interested, you should check my profile for appropriate links and whatnot...