EOSERV Forum > EOSERV > Bank Locker Upgrade Limit Bypass
Page: << 1 >>
Bank Locker Upgrade Limit Bypass
Author Message
Post #202675 Bank Locker Upgrade Limit Bypass

Here is a quick and hacky way to make the EO client think it hasn't met the upgrade limit unless the server says so. I did notice the build I have uses npc->Data().type rather than npc->ENF().type. You should ignore that change depending on which revision you are working in. The rest is pretty straight forward. I did plug it in to diff-online for a bit more clarity in what to add to fudge the client:

http://pastebin.com/GH7D7neM

Warning: This is an extremely lazy way to do this.

1 year, 32 weeks ago
Post #202693 Re: Bank Locker Upgrade Limit Bypass

Thank you so much!

This works great. I don't know why I couldn't think of such a brilliant solution.

I changed around your logic slightly, I'll share here just as an alternative:

static int locker_bankmax(Character *character) {
    return character->bankmax < static_cast<int>(character->world->config["MaxBankUpgrades"]) ? character->bankmax < 7 ? character->bankmax : 6 : 7;
}
---
Just your friendly neighborhood Programmer-Man!
1 year, 32 weeks ago
Page: << 1 >>

EOSERV Forum > EOSERV > Bank Locker Upgrade Limit Bypass