Mmf_eqmax_items=100,000?

**GeorgeS** · #1 07-09-2007, 10:52 PM

I'm slowly rewriting the item editor code to use a smarter way of finding the next available item_id, instead of using SELECT MAX(id) FROM ITEMS...
In this way it will not go over 100K limit.

GeorgeS

image · #2 07-09-2007, 11:17 PM

When you insert into a table using MySQL you are able to pass in a integer to retrieve the unique insert id, this would probably be the best way by just letting mysql decide the newest ID.

John Adams · #3 07-10-2007, 03:07 PM

Right, Image. So long as someone knows that time is coming. I think that item ID was the latest from 13th Floor, as of May.

Will the shared memory just not load those 100k+ items? Or will it crap something out? I think the former is true. I can't remember. i guess I could just go create item id's 100,000 through 100,100 and see if they show up.

image · #4 07-10-2007, 04:47 PM

Well you are confusing me, you are talking about an item editor and then you are bringing up code for the emulator. If you have item ID's that exceed that define, the items simply will not load into EQEMu's memshare because it needs more memory space. There is no other way around it other than increasing the define to exceed the highest item id number.

John Adams · #5 07-10-2007, 04:57 PM

No, I was talking about Emu only... not the item editor. Sorry for not being clear. I actually created my item by inserting a new SQL row manually.

I'm a barbarian at heart.

But thanks for clearing it up.

gernblan · #6 08-08-2007, 09:41 PM

100k should be enough for anybody.

Or was that 640k?

gernblan · #7 08-15-2007, 04:50 AM

Quote:

Originally Posted by GeorgeS

I'm slowly rewriting the item editor code to use a smarter way of finding the next available item_id, instead of using SELECT MAX(id) FROM ITEMS...
In this way it will not go over 100K limit.

GeorgeS

Thank you, GeorgeS. That is badly needed for sure. It will be helpful also to fill in gaps in the items table this way.