Warning and looking for input

[purple]

Ok, I've been at this long enough that I feel comfortable actually making some changes in release numbering and cvs. So I'm looking for some input as to what actually needs to be done before 5.1 is released. If you'd like to see something extra that isn't being done, bring it up.

Things I think that need to be done:
- Branch 4.x off the trunk in cvs
- Merge 5.x beta branch back to the trunk in cvs
- Update INSTALL.newbies (recommend Fedora Core 3? This seems weird with 4 out, but 4 is pretty crazy. Also, I don't know anything about Fedora Core at all!)

Once 5.1 is released, new changes will be on the trunk in CVS. New releases will have version numbers x.y[.z][.q] from there on out:

X will be major feature-based. I can't forsee what will bring this beyond 5 at this point, as for the most part seq has been maintaining itself instead of progressing for over a year now.

Y will be minor feature- and bugfix-based. The normal releases you have been seeing will equate to increases in Y because mostly they have a feature or two and a handful of bugfixes.

Z will be struct/opcode updates. If there's a patch and the only changes to seq are to update opcodes and structs, then only Z will be updated. Note that is is pretty rare and usually there will be some bugfixes and minor features mixed in. Z is optional. If it isn't specified, Q isn't specified either, and both are for all intents and purposes 0.

Q will be purely release problems being fixed. If I release a crap tarball that won't build and I need to quickfix it, then I'll use the Q part of the version to reflect this. Q is optional. If it isn't specified, it is 0.

[BlueAdept]

Sounds good to me. That is the way it should have been done for version updates.

I'll help with what I can. I'm not very good at writing but I will see what I can do. It won't be until next week because I am a bit tied up this week. Lot of stuff I need to do.

[purple]

The first two bullets on my list are complete in CVS now if anyone cares and will show up on anoncvs by tomorrow I'd imagine, depending on the whims of sourceforge. Next release will be 5.1 whenever support for live is reestablished.

The 4.x branch is now v4. The 5.x branch is merged down to the trunk and all new development will occur there (and not pre_5_0_beta). I'll more than likely only branch for major version releases since we don't maintain old version since they are useless anyways for using against live (though I'll continue to tag releases with vX_Y_Z_Q as above).

[bonkersbobcat]

Sounds good to me.

BB

[Cryonic]

I would shift the bug fix parts of Y into Z. So X is major feature changes/additions. Y is minor changes to current feature set. Z would be bug fixes to features of X/Y. Q would be opcode/struct changes to track EQ live.

So you would release SEQ 5.1.0.0 for live today. 5.1.1.0 to deal with a code bug (not likely) as well as struct changes. 5.1.0.1 if no code fixes, but some struct changes/opcode fixes, etc...

[Spaz]

As far as the FC3 suggestion - It can work with both RH9 and FC4, but both now require some tinkering.

If a newb wants to grab Linux, SEQ, get rolling then FC3 is pretty painless. From what I recall of the installs, the defaults would work for most everything (I use my linux box for other crap, so I added a bunch).

Succinctly, I think FC3 should be the suggested OS for quickly installing, but I'm interested in hearing how easy the other distros are to get running.

[DiAvOlO]

I have a quick question how would this update work, with a unit that is running Redhat 7.2 ,

Say for excample I have Showeq 5.xxxx up and runing right now on Redhat 7.2

Could you do a regular update on cvs when the new version of Showeq comes out?

[purple]

cvs is for developers and people who don't need to ask questions like that. Tarballs are for everyone else.

[Could_Be_Anyone]

I've been using it under Gentoo Linux thru v. 2005 with no issues. I'm happy with Gentoo Linux, so I have no plans on switching, but I got bored last week and blew in FC4 on an old machine just for the sake of looking at it and and the current SEQ tarball (.25) installed and ran with no tinkering.

I didn't spend alot of effort installing FC4, just ran the installer, selected a 10G partition and blew everything in.


As far as the FC3 suggestion - It can work with both RH9 and FC4, but both now require some tinkering.

If a newb wants to grab Linux, SEQ, get rolling then FC3 is pretty painless. From what I recall of the installs, the defaults would work for most everything (I use my linux box for other crap, so I added a bunch).

Succinctly, I think FC3 should be the suggested OS for quickly installing, but I'm interested in hearing how easy the other distros are to get running.

[purple]

I use Gentoo and keep everything very up to date with stable, so you're pretty much guaranteed to work on Gentoo.

I tried to get seq to work with FC4 "out of the box" so that people wouldn't feel behind on FC3, but I've never used it, so I got no clue how to update INSTALL.newbies.

[Cryonic]

only reason to not recommend Gentoo is if the user (of which most SEQ users qualify) are linux neophytes. I've done gentoo installs (stage1 and stage3) and they aren't for the faint of heart or the unknowlegable.

[Elyon]

So I'm looking for some input as to what actually needs to be done before 5.1 is released. If you'd like to see something extra that isn't being done, bring it up.


Is it possible to get the X Y Z coordinates in the maps working again?

[SeqTester]

I've done gentoo installs (stage1 and stage3) and they aren't for the faint of heart or the unknowlegable.

But it forces you to learn more, I really enjoyed the Gentoo install on my 2 ShowEQ boxes and also on my VDR (TV) Box. I know for sure I learned a few things about lunux I did not know before these installs.

[Could_Be_Anyone]

Yes, a stage 1 install can be a bit time consuming. ;)

Regarding the learning involved. If you want to play with toys like SEQ, what's wrong with spending some time learning how? Nothing, in my book.

That's one reason I won't be keeping Fedora, and I've never really liked any flavor of Red Hat.. it just wants to be Windows. :P


only reason to not recommend Gentoo is if the user (of which most SEQ users qualify) are linux neophytes. I've done gentoo installs (stage1 and stage3) and they aren't for the faint of heart or the unknowlegable.

[Red]

As an added suggestion, can the Zone Modifier be displayed on the GUI front end (or did I just miss it)? I am currently watching the terminal window when I zone to see it scroll by and have had to zone a couple of times to catch it.

[purple]

By zone modifier do you mean ZEM? ZEM isn't passed to the client I believe, so whatever you're seeing isn't valid.

[Cryonic]

ZEM is dead. All the zones are listed as a ZEM of either 1 or 100 and SEQ does display it down on the lower bar of the main window (status bar?).

[rolled]

I think it'd be sweet if the skittles could be color coded for Zek, even con within 4 levels, green below that, and red above it.

Love this proggy guys, thanks! yall are l33t!

[r]

[purple]

Players are already color coded based on normal consider ranges inside the magenta box....

[fransick]

During the server side/client side changes of the past few years, did SEQ lose the ability to dump bank inventory to console or file?

It sure was nice getting a file dump from all those mules. I am guessing that was a victim of changes much like ZEM.

~

[rolled]

sorry if im being retarded, but color coded for pvp? i used to have the pvp diety checked on Sullen Zek, i was suggesting a pvp option under the options menu that works for the new rule set.

[r]

[purple]

What does "color coded for pvp" mean? How's that different than just color codes by con color? I got absolutely no idea what "the new rule set" is.

[purple]

The contents of your bank is sent every time you zone.

[rolled]

The new pvp rule set is within 4 levels you can attack someone. So within 4 levels, toons would con white, and more than 4 levels red, less than 4 levels green. This rule set hit when the 3 pvp servers merged into one, so the pvp diety and pvp team servers are no more. I used to use the PvP Diety option that made evils red, neutrals orange, and goods blue. A pvp option would be sweet for those of us playing on Zek, however.


[r]

[fransick]

The contents of your bank is sent every time you zone.At the risk of appearing braindead, is the only way to view this data to log packets and sift through it that way? I've messed around with the debug menu and network/log in the past and haven't found an easy way to list bank inventory. It used to be a menu option back in the days of v4 if I recall.

~

[purple]

Does /outputfile inventory from your EQ client do what you want?

[fransick]

Does /outputfile inventory from your EQ client do what you want?I'll claim ignorance here... didn't seem to do anything but then again I could be invoking the command improperly.

I have a feeling I am missing the obvious here and making it more complicated than it is. At this late hour, public embarassment comes easily : )

~

[purple]

Go look for the text file it made for you containing all your inventory and bank...

[purple]

Ok, so for PVP, would this be ok:
1) New context menu option on the map for Show->PVP
2) If someone is within +/- 4 of you their icon will switch from a box to a triangle
3) If someone is within +/- 4 of you they will have a flashing circle based on colors:
a) If they are -4 through -1, the flashing circle will be blue
b) If they are the same level, the flashing circle will be white
c) If they are +1 through +4, the flashing circle will be yellow
4) If they are outside the range, there will be no flashing circle and normal box icon for players

No promises since I've never touched the map, but would that be what you are looking for?

[rolled]

That would be sweet, purple.


[r]

[purple]

pvp thing was pretty easy. The map stuff is well written. That'll be in next release.