Spells Level 255
 

What are all the spells that have required level of 255? I tried searching the forums for "spells level 255" but I only get results about "spells level". Is my spell file showing the client they are level 255? Are they not functioning, thus they are level 255?

-Djeryv

spells that are level 255 are everyspell pretty much and if ur level 255 you can mem them all thus a gm can use all spells in game at level 255 i believe

Well...I made some vendors and put those spells in their merchantlist. When I shop for them, they will say...for example...

BRD(255)

...these are the ones I am referring to. It is a Bard Song...but does the bard need to be level 255? If so...why is that...as characters cannot get that high.

-Djeryv

whats the spell name

In this example...

Song: Aelfric's Last Lullaby
Item ID: 78750

-Djeryv

now are u a bard when ur looking at the spell

scratch the last comment now the real question are you on sof client?

hmm i just went and change my server level to 85 since its a 71 spell and used sof client ur prolly better off making a spell scriber or maybe just going into the items database and seeing if u can edit the req level

I use SoF client only on my server. I don't want to make the spell usable if it is not functional yet.

Now...you said to scratch that comment...but I will say...I was logged in as a GM when I was looking at the vendors and their inventory.

-Djeryv

well i made a bard and all that the spell is functional
but the only problem is u cant scribe it from that scroll since level says 255
but u can have a spell scriber scribe all there spells saves u time making vendors you can even make people pay to get there spells from the scriber also depending on how u wanna do it

But how can they use it if they are not level 255?

-Djeryv

the scroll says level 255 but i did a scribespells on a bard and the spells showed up

But can they cast it?

aslong as its scribed yes but they cant use scroll to scribe it

I understand that you can just do a scribespell on it...but...

in the spells_new table, it shows that bards can use it at level 71. So why is the scroll saying BRD(255)? Why does it not say BRD(71)? No where in the spells_new (or in the spells_us.txt) does it show Bard 255. I even bumped up the server to MaxLevel of 85 and the spells still show (255) when you right click on them.

-Djeryv

Without knowing, since most spells in the database were based on max level being 70, and seeing that there's work being done on spells on the svn, I would guess that they are new spells being added for chars > lvl 70 that are being added to the database, but haven't been made available yet. One way to ensure no one can use them until they are ready to make them available is to set the level to 255 (if you check the database, all spells list the required level for each class, and all classes not getting a particular spell would be set at 255).

that was a problem in eq live as i play a cleric my cure spell was changed to 255 couldn't use it any more because of req lvl and was never fixed. as i do recall this happend around the time they changed the lvl of kei
to be casted on player and when the quild list lvls where messed up you would notice one or two peeps in guild
with wrong lvl. that spell was changed to 255 is still that away today in underfoot as the guild list was fixed later after a few updates patches. if i recall the lvl it was a lvl 55 spell and they have a 2 infront of that it was a data base error and hasn't been fixed yet under eq live so one spell from every class at lvl 55 was changed to 255.

i think its just the scroll is messed up ive tested spell it works and if u scribespells it it shows level 71 like its suppose to think its something to just do with the spell scroll

Although, now that I think about it, I played my mage last night on my private server, and noticed that two of my summon pet spells were listed as 255 when I was looking through my spells to memorize one. I think they were Minor and Major Conjuration, of which type I'm not sure. I'll see if I can check tonight and see which ones are doing that.

Lol to clear things up, they keep it at 255 so its hands off variable for future reasons and or for mob usage, mobs can still call the spell ID's without the appropriate level.

And as far as those spell scrolls, the default spell file is the Titanium spell set and until you mod them otherwise you're not going to be able to mem those spells appropriately (That is your talking about beyond Titanium spells).

I noticed that the scroll(ITEM) is not associated with the SPELL in the spells_new table. Not like the normal spells are. This may be the problem.

-Djeryv

Yeah they need to be linked up, there's a spell scroll effect ID that links up with the actual Spell ID, then there is a scroll type variable that depicts whether its a tome, spell etc.

If you edit your spells file/table from the default file and change spell IDs around, that is probably going to cause the problem you are seeing.

If making a custom spell file, you either want to make sure all scrolls related to the changes you made are corrected, or just use quest::scribespells($level) to scribe spells and avoid using the now broken scrolls.

Also for some scrolls, I am sure there is a chance that the scroll was changed on Live to prevent players from using it. By changing it to require level 255, they can be sure no one will be able to scribe it again. Since PEQ gets the items table from EQLive collects from the 13th floor database, the item data should match Live exactly from the time of the last update from that particular item. If you haven't edited your spells file at all, then chances are that SOE decided they didn't want players having that spell anymore.

The 255 level is just something set in the spells table to restrict classes from being able to scribe or use that spell. If all classes are set to 255 in the spells table, then that spell is an NPC spell or focus/worn/proc effect.

I just compiled a windows server running on XP with current PEQ code from SVN (downloaded day before yesterday). Had to do a lot of tinkering with the .sln file to get it going, but eventually got there.

I seem to have the same spell problem, but seems to be limited to spells above level 70, and all aura spells. Somehow my wife got her wizzy Rk. III spells up to level 75 using GeorgeS's item editor, but since then I haven't been able to do the same for shaman, cleric, chanter. The spells look like they go in the book from the editor, and show a spell icon, but then they aren't there on the toon after logging in.

#itemsearch Spell: <whatever>
gives me the correct scrolls
Then '#summonitem [ID]' to get them and they are all level 255.

I '#level 255' on whatever toon and they still can't mem them with an error of the spell already being in their book. Oh, and yes, this is all with SoF clients. haven't tested Titanium on it.

Just wondering if this is a 'windows' problem, or because of some changes to the spells, or maybe even because of the use of the item editor? - no items changed though. The 'spells_new' table of the database shows the correct level required for the correct classes (The correct class is NOT labeled 255 in the spells_new table) and I didn't edit the table ID's either..

If there's a developer wanting to test this, I think I have the server set for public access, just PM me for the site and account.

Actually thinking my problem has something to do with what's mentioned here.
http://www.eqemulator.org/forums/sho...97&postcount=6
I'm sure my setup isn't correct.

I think I found my problem. After importing the spells_us.txt with import_spells.pl, I ended up with duplicate spells in the database. Here's an example (deleted the SQL insert stuff for clarity..)

Second spell with the same name..
After deleting the second entry, I was able to place the spell in the toon's book with GeorgeS's item editor, but the spell scroll was still level 255, and maybe it is somehow linked to the second listed spell. Before importing, the only spell available was the second ID though. Very easy to tell them appart since they have no cast_on_you or cast_on_other field.
Maybe I missed a step somewhere, not sure. Trying to learn all this though.

I'm thinking maybe when the SoF disk was released, the first spell was to be used, but they changed when they went live (I know I still had to download crap even with the disk).

Hello. I am having a similar problem. I have a 9 shaman on Project 1999. I installed everything according to directions with nothing else. Anyways i turned 9. gated back to get my spells and i bought spirit of wolf. I open the description and it displays Shaman(255) Druid (255) Ranger (255). i go to put it in my spellbook and i get "your class can never use the spell:spirit of wolf"




...... Wondering if there were any fixes. Cause a shaman without SoW in the old world would be kind of lame. :confused:

Anyways Happy Hunting.

www.project1999.org, not here.

I had a number of issues with 255 level spells on my private server. One example was the level 59 shaman spell Incarnate Anew. It was listed as a level 255 spell and under another name. I used Georges Spell Importer on my SQL database found here:

http://www.georgestools.eqemulator.net/

...then I used the spells_us.txt from the SoD client and it resolved all of my spell issues.

I'm also playing on a private server and have run into this issue. The spell Spirit of Wolf shows as level 255 for all usable classes. I replaced my spells_us.txt files with one from the server, however it didn't fix the problem. Sow is still listed as 255 and unscribable, along with many others.

Any other help would be greatly appreciated!

First, get MQ2 when doing dev work. It gives you a TON more info to help you debug without needing to hunt through logs.

Second, make sure your client has the latest spell file. If you have made changes to your server, export the spells_new into a spells_us.txt file. If you have updated or added a new spell, but the client is using a default installed spellfile (or one that is MASSIVELY out of date) then it will default to 255 for everyone.

Third, you said in the spells_new table that the spell is level 71? Find the spell scroll item in your items table check the scrolltype field to ensure it has the same spell ID there. You may have placed an incorrect spell there (which may not be usable to bards, which explains the 255). Also, check the classes field (should be equal to 128 if bard only).


If you have done all of this, I'm positive it will be resolved.

-Hate