Random Chitchat 2012-2016

[xoft]

I never wanna leave XP

---

XP is still the second most present OS today, according to wikipedia:
http://en.wikipedia.org/wiki/Usage_share...ng_systems

---

We have just "gained" a few percent points of source code comments on OhLoh. I had forgotten to exclude the Bindings.cpp file from analysis; and since it's machine-generated, there aren't many comments in there.

[xoft]

I'm currently "fighting" with both Lua and SQLite, I decided to finish the ProtectionAreas plugin, together with its tutorial.

[tonibm19]

I'm currently "fighting" with both Lua and SQLite, I decided to finish the ProtectionAreas plugin, together with its tutorial.

Good, when it's finished I'll try to make a server with plots.

[xoft]

Finally some nice weather. I finally got around to swapping the tires on my car from winter ones to summer ones

[tonibm19]

Mobs don't move FS#381
I mised set it to high, it is in low. I think you should set it to high, it's a big problem.

[NiLSPACE]

Mobs don't move FS#381
I mised set it to high, it is in low. I think you should set it to high, it's a big problem.

Well Keyboard is still working on the mobs, so it is expected that they are not doing what they should do.

Finally some nice weather. I finally got around to swapping the tires on my car from winter ones to summer ones Smile

Yea we also finaly have some nice warm weather.

[tonibm19]

In Spain you can't stay out because it's very hot, and the swimming pool is not opened

[NiLSPACE]

I exported a function and I created a function. One is the clienthandle SendBlockChange function. With that you can send "fake" blocks. and the other is cWorld::GetWeatherInterval/SetWeatherInterval that returns/sets the amount of ticks before the weather changes. Should i commit the changes?
EDIT:
Also I worked on the level.dat. I added: raining, thundering, DayTime, GameType, rainTime, LastPlayed, and LevelName.

[xoft]

Those two functions, GetWeatherInterval() and SetWeatherInterval(), do they work on a single interval, or do they set the interval permanently? That is, once the interval is up and the weather changes, will the new interval be the old value or the newly set value? Is it possible to rename the functions to make this more apparent? Or add the counterparts?
I'd go with:
GetTicksUntilWeatherChange() - returns the number of game ticks until the current weather changes
SetTicksUntilWeatherChange(a_Ticks) - sets the number of game ticks until the current weather changes
GetWeatherInterval(a_Weather) - returns the number of ticks for which the specified weather stays (is a per-weather value)
SetWeatherInterval(a_Weather, a_Interval) - sets the number of ticks for which the specified weather stays (per-weather; regardless of what weather is now)

I don't think the level.dat change is necessary, that file is only written so that external tools, such as map viewers, work with the level. MCServer doesn't use it at all - it has its own world.ini that should store all the info.

[NiLSPACE]

Those two functions, GetWeatherInterval() and SetWeatherInterval(), do they work on a single interval, or do they set the interval permanently? That is, once the interval is up and the weather changes, will the new interval be the old value or the newly set value? Is it possible to rename the functions to make this more apparent? Or add the counterparts?
I'd go with:
GetTicksUntilWeatherChange() - returns the number of game ticks until the current weather changes
SetTicksUntilWeatherChange(a_Ticks) - sets the number of game ticks until the current weather changes
GetWeatherInterval(a_Weather) - returns the number of ticks for which the specified weather stays (is a per-weather value)
SetWeatherInterval(a_Weather, a_Interval) - sets the number of ticks for which the specified weather stays (per-weather; regardless of what weather is now)

I gues GetTicksUntilWeatherChange() and SetTicksUntilWeatherChange() is a better name. They are just like the SetTimeOfDay in the World.h.

Int64 GetWeatherInterval(void) const { return m_WeatherInterval; }
///////////////////////////////////////////////////////////////
void SetWeatherInterval(long a_WeatherInterval)
{
	m_WeatherInterval = a_WeatherInterval;
}

I don't think the level.dat change is necessary, that file is only written so that external tools, such as map viewers, work with the level. MCServer doesn't use it at all - it has its own world.ini that should store all the info.

Yea but if you want your world to run on Minecraft you need everything, so i started working to get everything