[ARCHIVED] Latest Version of UOX3 (Updated March 8th 2006)

[giwo]

Code: Select all

[color=yellow]3/05/3006 - giwo (0.98-3.4v [3.5 BETA])[/color]
	Added the Script # to the JS Error Reporter to make debugging easier.
	Fixed an issue causing JS scripts to give useless error messages on server startup.
	Modified the region debug code to not default to on in debug mode.

I have some other JS changes to make before we release 3.5, which I will be committing in the next day or two. Currently the only thing holding up the next release is the problem with UOXCFile in JS. It seems that the properties work fine, but the methods will not work unless I disable the properties. As a workaround I may make the class work entirely with methods for now, but eventually we will need to track down this issue.

Aside from that, I have also been doing alot of work on walking and map handling. Currently I have implemented a rough version of A* pathfinding, which will need some speed improvements yet, but I'm hoping we will see in 3.6, and I have also found several bugs in maphandling which I will be submitting as fixes in the 3.6 beta cycle.

Anyhow, for other developers/contributors, try to tie up any loose ends leading toward a release of 3.5, as I will be trying to finish up the JS changes and hopefully we can see a release within a week.

[Maarc]

Code: Select all

[color=yellow]5th March, 2006 - Maarc[/color]
Updated file loading code to be more accurate in %ages.  Will now be much more accurate, with no large jumps.

[Grimson]

Ok, I got finally through on CVS. Is it possible that you (giwo) forgot to actually update the version number in the code, or is the CVS damaged due the problems SF has today?

[giwo]

Code: Select all

[color=yellow]3/05/2006 - giwo (0.98-3.4w [3.5 RC])[/color]
	Minor changes to the JS Handling.
	Modified UOXCFile handling to remove all props and added .EOF(), .Pos(), and Length() methods.
	Fixed an issue causing items not to dissapear when 'removed
	Fixed an issue causing characters to randomly dissapear around NPC's
	Fixed an issue causing items and characters to be updated when out of range.
	Fixed a VC2005 Compile issue.
	Included a default VC 2005 Project/Solution file.

Either is possible...

More likely is that I forgot.

[Grimson]

Code: Select all

[color=yellow]3/07/2006 - grimson[/color]
	Fixed LineOfSight() not working when you stand directly next to the target.
	Changed checkItemLineOfSight() so that it checks whether you can see the base or
	the top of the target item.

[Xuri]

Code: Select all

[color=yellow]3/05/2006 - giwo (0.98-3.4w [3.5 RC])[/color]
	Modified UOXCFile handling to remove all props and added .EOF(), .Pos(), and Length() methods.

Could you give an example of how to use these?

[giwo]

.EOF() is a boolean value, basically are we at the end of the file.

.Length() returns an integer that represents the length of the file (in increments of bytes).

.Pos() sets and returns the current read/write position in the file. (If you don't pass a val, it returns but does not set).

[Grimson]

Code: Select all

[color=yellow]3/08/2006 - grimson[/color]
	Fixed CPIAllNames3D::Handle() so that SHIFT+CTRL actually shows the names of NPCs.

[giwo]

Code: Select all

[color=yellow]3/08/2006 - giwo (0.98-3.5)[/color]
	Fixed a possible issue caused by passing float values to JS func RandomNumber()

[Xuri]

UOX3 0.98-3.5 is up on the downloads page (and in the first post of this thread).

[giwo]

Downloads at OpenUO@SF.net updated as well.

Xuri: so what were your thoughts on "archiving" this thread with every version release?

[Xuri]

New category (archived discussions) and subforum (changelog archive)created. Names can be changed if anyone has better suggestions

So how do we do this? Just move this entire thread there, then pop up a new similar one, or what?

[giwo]

Yeah, in the future we can do it with every new release, but since this is the first, just lock and move this thread, and create a new thread (probably copy/paste from the old one) in its place.

That way we have an archive of all of our old conversations/web changelogs, which could be removed later, if need be.

[giwo]

While you are about creating forums... perhaps a "Tools" forum, where we can handle new Tool announcements, support questions, and so on.

Going further on that thought, maybe Tool Designers can request their initial announcement be made "sticky" and then they can update it as new versions arrive....