Missing Client Files for RoF2 with current server and peq database?

[Yummy]

What is the current state of missing files if any for the supported rof2 client and the current, 2/13/2015, peq database? I found a number of older posts but nothing recent or concise.

What prompted this post is in Nektulos I am experiencing very poor pathing; mobs walking through terrain, more hopping than I recall, and attacks from under the world. My assumption is I having missed something, possibly, client side.

client: supported rof2
private server: 6/7/2015
peqdb: 2/13/2015

Your time and help are very much appreciated.

[Yummy]

Hopefully, someone has something more recent, but I did find the following information.


Trevious stating the RoF2 client is complete except olde zones. Unfortunately, no idea what zone are older using the current PEQ database.
http://www.eqemulator.org/forums/showthread.php?t=39158

This post states 'some files may need to be copied' but nothing definitive and ultimately sends you to the UFMissing wiki entry.
http://wiki.eqemulator.org/p?Play_Gu...etting_Started

UFMissing wiki entry
http://wiki.eqemulator.org/p?UFMissi...etting_Started

Can anyone state definitive one way or another if there are missing files and which ones?

Thank you.

[Yummy]

In the absence of help, I started to dig into the pathing issues I observed in Nektulos.

I need to do further testing and I may have broken something(?), but the symptoms of mobs being under the world, pathing through terrain, and a ridiculous amount of hopping has been resolved.

Using KLS' zone utilities, I generate a new azone and awater files, uploaded to the Linux EQEmu host, then restarted daemons. Again, I need to test further but it looks much improved and the resulting files were not the same as found at http://eqemu-maps.googlecode.com/svn/trunk/.

Does anyone have any insight?

Thank you KLS for your awesome tools.

If I find my initial observations are erroneous, I will update, otherwise it is fixed.

[Coenxai]

The two main issues would be not having a properly generated map file or loading database information from a previous version of Nektulos forest.

[dagulus2]

Originally Posted by Yummy

Hopefully, someone has something more recent, but I did find the following information.


Trevious stating the RoF2 client is complete except olde zones. Unfortunately, no idea what zone are older using the current PEQ database.
http://www.eqemulator.org/forums/showthread.php?t=39158

This post states 'some files may need to be copied' but nothing definitive and ultimately sends you to the UFMissing wiki entry.
http://wiki.eqemulator.org/p?Play_Gu...etting_Started

UFMissing wiki entry
http://wiki.eqemulator.org/p?UFMissi...etting_Started

Can anyone state definitive one way or another if there are missing files and which ones?

Thank you.

There are actually hardly any files missing as far as I can tell in the RoF2 version on steam. The ones that have cropped up are the LDoN resources for Oasis, Nro and Sro.

There are however a few zones that RoF2 simly does not recognize as existing even if you have the right files, such as ecommons, highpass, misty and tox. There is also the fact that Arena, Bazaar, Nektulos and Lavastorm have been replaced with new versions, but that is common to all usable clients.

Everything else should be accessible with an unmodified RoF2 client.

[Coenxai]

Originally Posted by dagulus2

There are actually hardly any files missing as far as I can tell in the RoF2 version on steam. The ones that have cropped up are the LDoN resources for Oasis, Nro and Sro.

There are however a few zones that RoF2 simly does not recognize as existing even if you have the right files, such as ecommons, highpass, misty and tox. There is also the fact that Arena, Bazaar, Nektulos and Lavastorm have been replaced with new versions, but that is common to all usable clients.

Everything else should be accessible with an unmodified RoF2 client.

That's actually not true. The only issue the client has a problem with is Highpass iirc.

[Yummy]

Originally Posted by Coenxai

The two main issues would be not having a properly generated map file or loading database information from a previous version of Nektulos forest.

Originally Posted by Yummy

client: supported rof2
private server: 6/7/2015
peqdb: 2/13/2015

Coenxai, I totally agree with your statement. What is puzzling is that I had checked with the wiki, Debian build, to verify I was using the current sources, given below, for both peqdb and maps. I have checked a third time and I am/was using those sources.

Did I use the wrong sources?

peqdb (http://peqtgc.com/releases)
https://drive.google.com/folderview?...p=sharing#list

maps
http://eqemu-maps.googlecode.com/svn/trunk/

My build documentation is found here--nothing regarding the use of azone/awater, yet:
http://blog-harmonson.rhcloud.com/20...erver-minimal/

The map file I processed with azone/awater to generate the working files was from the RoF2 Build Date of May 10 2013 23:30:08. It is cited as the most current supported client. So I am bloody confused. Am I using the wrong map file or wrong client or something else? Is it possible maps files change without build dates changing? Hmm.. I obtained the client after May 10, 2013 from Steam at or before March 2014.

Testing my generate map files: I hunted mobs for five hours without pathing issues for Unholy armor quests. God, I forgot all about the mobs pathing through the halfling camp and died a few time trying to mend between fights. I am rusty

I appreciate your time and guidance.

[Coenxai]

Testing my generate map files: I hunted mobs for five hours without pathing issues for Unholy armor quests. God, I forgot all about the mobs pathing through the halfling camp and died a few time trying to mend between fights. I am rusty

So the issue is fixed or what?

The map file I processed with azone/awater to generate the working files was from the RoF2 Build Date of May 10 2013 23:30:08. It is cited as the most current supported client. So I am bloody confused. Am I using the wrong map file or wrong client or something else? Is it possible maps files change without build dates changing? Hmm.. I obtained the client after May 10, 2013 from Steam at or before March 2014.

Azone will build the map file for you containing the listed objects in the .ini file. I've never used the maps repository as I simply build them myself (less bandwidth for me, plus I like to stick every object in them and sort it out later). By default, they will build to your current directory, so you'll need to stick them in the server/maps folder.

[Yummy]

Originally Posted by Coenxai

So the issue is fixed or what?

Azone will build the map file for you containing the listed objects in the .ini file. I've never used the maps repository as I simply build them myself (less bandwidth for me, plus I like to stick every object in them and sort it out later). By default, they will build to your current directory, so you'll need to stick them in the server/maps folder.

Yes the new/generated map is working as expected. I apologize for being unclear.

Can you clarify what you do exactly with the .ini file? I just ran the command without any modifications. I would like to duplicate your process since it works.

After this experience with the Nektulos map from the repo, I will follow your process and build my own then scp to the eqemu host. Thank you.

[Coenxai]

There's another application called something similar to GLModelViewer? It's been a long time since I've used it. You'll figure out what I'm referring to relatively quick though if that's not the name. You browse the zone file you wish for objects to map. When you find the object you stick it in the .ini for when you build the map with azone.

Here's an example entry:

airplane.s3d,0,1,2,3,4,5,6,7,8,9,10,11,12,13,14
akanon.s3d,0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,1 6,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32, 33,34,35,36,37,38,39,40

[Yummy]

OK. I will take a look.

I assume cavedude uses ini files to generate his maps. Maybe he will see this post and dump them on googledrive.

Either way, I will manage.

Thank you, Coenxai.