Rec/Req levels
 

Is there a way to remove the req and rec level from items, i have tried creating, modifing items through phpeditor and the EOC and even though the editor shows it removed, it still has it listed in game... have also done direct sql queries, no dice.. any help would be appreciated

Did you restart your server after making the changes?

yes, i did, even went as far as restarting entire OS. no dice.

So, pretending you're attempting to make Item 50153 available at full stats to characters of any level, you changed both reclevel and reqlevel to 0, and restarted the server, but they're still showing as required and recommended levels for that item in-game?

Relevant SQL code would be:

right, i was trying to do query for entire server thus i did

UPDATE `items` SET `reclevel`=0, `reqlevel`=0 WHERE `id`=%;


i am newb to this, but learning fast, this is tripping me up though

Ahh, gotcha. Just drop the WHERE `id`=% bit.

I can see what you were attempting, but it wasn't quite right. % is used for text fields, and is accompanied by the LIKE keyword.

You could use it for things like matching on item name.

But when it comes to numbers, there's no such matching. You can use "WHERE `id` IN (1, 2, 3, 4, 5, 6)" or "WHERE `id` BETWEEN 1001 AND 1009" or "WHERE `id`>0", but the percent sign isn't used for number field matching.

ok thanks, im going to give it a try right now, ill update once tested

I ran that query without the WHERE portion, i also ran it directly on the item i created. no errors, EOC shows the item without the level restrictions, but once i load into game and #si the item it has the level restrictions...im truly not getting it.

The statement to run is:

If you:

1. Run it on the correct database in Navicat/HeidiSQL
2. Restart the server (including shared_memory)
3. Log into the game and summon the item

Then I don't think there is any way to not see the updated results.

It has to be the same database in #1 that your server is using in eqconfig.xml. And you have to do #2 after verifying #1.

Thank you much, apparently i did all the DB stuff correct, but shared_memory was a step i was forgetting! i literally just set this linux server up, and have been typing the commands in manually. havent set up a script to start the server. ill have to learn a bit more linux before i get into BASH :P

Thanks again!

Glad you found the problem!

Yeah, shared_memory is a necessary step whenever the database is changed, so it's generally at the top of the list in load scripts.

It loads the server-wide data from the DB and makes it available to each zone instance so they don't have to load their own separate copies to work from.