Save state of loaded EQ to save it through crashes/reboots

Please post your ideas to improve our mud.

Re: Save state of loaded EQ to save it through crashes/reboo

Postby *Splork* » Wed Jun 28, 2017 5:56 pm

The last code used value of item and other flags to exclude saved items.

Hundreds to thousands of items can be loaded at any given time. There is no sense in saving(and loading) small treasures and junk items....
User avatar
*Splork*
Site Admin
 
Posts: 1121
Joined: Tue Apr 29, 2003 8:50 pm
Status: Offline

Re: Save state of loaded EQ to save it through crashes/reboo

Postby Teron » Thu Jun 29, 2017 4:59 am

1. I'm not sure, if I was clear.

I meant held/worn items on mobs, larger than 1mil.

It shouldn't be a whole lot, and, like Gorka said, we are not killing the entire MUD. We are killing mostly same mobs - the issue is for items to stay long enough until we go back and kill them.

2. Some good items have low item value, and relative junk has high value, so it's better to go by item type.

3. I'd just start with some settings, go from there and see, if you can add/remove filters without eating tons of memory.

4. Both issues of not getting an item on repop and having tons of items loaded can be solved by loading items on death. What is your opinion on this?

The only exception I see is personal quest items, because we need to know, whether it loaded beforehand, so the looters are off/on - or there needs to be a separate load mechanism/message for personal items, so they are not looted immediately.
User avatar
Teron
Avatar Poster
 
Posts: 616
Joined: Wed Mar 03, 2004 1:59 pm
Status: Offline

Re: Save state of loaded EQ to save it through crashes/reboo

Postby Gorka » Thu Jun 29, 2017 9:28 am

It's difficult to determine an item's true value these days by defining conditions based on object attributes.

A lot of cp's have almost no object value, a lot of what is worn is junk. Even food items are used in some quests as well as spellbooks. It would be extremely difficult to set conditions on what reloads based on object attributes without applying rules unfairly.

You could avoid using object attributes and use a timestamp system like I suggested to stop scum settling in your reload file... or you could bite the bullet, and fix object values and types. You could kick the can down the road a bit and just watch for the scum in the bottom of the file while it's worked out.

Ideally object values need fixing, that's the purest solution... also the most work.

Regarding popping the items on death... solves a lot of problems I agree... but also I have some reservations... it's just so "sloth" that it works the way it does. It would be like a food company changing the recipe of an established product after 20 years... Even though it might be better... you just don't do that. Imagine Coca Cola dumping using sugar out of there regular product. They have been farting around with all these alternatives, but for all it's sugar, the original coke is something I doubt they can ever change or get rid of without massive upset... you don't change legends.
Gimme a G! Gimme a ORKA!
User avatar
Gorka
Double 40 Poster
 
Posts: 244
Joined: Tue Jul 12, 2016 5:50 am
Status: Offline

Re: Save state of loaded EQ to save it through crashes/reboo

Postby *Splork* » Thu Jun 29, 2017 2:41 pm

I'm not so sure I like the idea of changing how items are popped.

I think the new code will solve the majority of issues and concerns which have been raised.
User avatar
*Splork*
Site Admin
 
Posts: 1121
Joined: Tue Apr 29, 2003 8:50 pm
Status: Offline

Re: Save state of loaded EQ to save it through crashes/reboo

Postby *teker* » Thu Jun 29, 2017 3:55 pm

I'm hoping that once we get the code in place I can analyze a sample file and try to build rules based on the data. I'll know a lot more once I can look at a real sample. I've had an issue pointed out that I hadn't known about, so I'm still working on making the save function function work properly in all cases.

We can currently pop items on death using procs - the prisoner in Castle Zodiac is an example that pops some items normally and atleast one via proc. One disadvantage of doing this for all mobs is that Wealth and Glory would have to be rewritten as it doesn't know how to handle proc pops (like Maleficent). Currently all data for pops is stored on the room in which the pop happens - that would also have to change so that the mob can pop the appropriate items after roaming. It's a little tricky since we can pop multiple identical mobs in the same room but pop different items on them.
*teker*
Double 40 Poster
 
Posts: 194
Joined: Sun Apr 05, 2015 3:41 pm
Status: Offline

Re: Save state of loaded EQ to save it through crashes/reboo

Postby Teron » Fri Jun 30, 2017 1:09 am

The amount of totally useless worn items is minimal, afaik, since they don't all load at once.
There are several ways to filter, but I imagine all ways to filter have to be factored in, not just one or the other.

Items loading on mobs rather than on death is not Sloth, it's just all or most of the early MUDs, because that was the only way to do it, as far as I know.

The lazy, slothy way would've been to actually load items on death, so we kill mob once to have a chance to pop and get the item, and carry on.
User avatar
Teron
Avatar Poster
 
Posts: 616
Joined: Wed Mar 03, 2004 1:59 pm
Status: Offline

Re: Save state of loaded EQ to save it through crashes/reboo

Postby Teron » Thu Jul 20, 2017 11:51 am

07/20
Scheduled reboot

a swirling ball of fire
a heavy iron safe
a backgammon board
a book of conflagration
about 13 scimitars, 6 swords, 1 pair of ant mandibles, a few macus.
User avatar
Teron
Avatar Poster
 
Posts: 616
Joined: Wed Mar 03, 2004 1:59 pm
Status: Offline

Previous

Return to Mud Suggestions

Who is online

Users browsing this forum: No registered users and 1 guest

cron