I have searched the threads and google and I cannot find anyone talking about this but this needs to be addressed.. The "Collect Wage" feature for guild missions was a good idea to get members to participate more in guild missions however the fact that members can use this feature as a savings tool can severely crash a guilds bank! Let me explain. The total amount of funds per mission (guilds half of silver + members half of silver) gets deposited fully into the GUILDS FUNDS TOTAL. It does NOT get divided with half the silver being directed towards the participating guild members in a separate function. This causes a false balance of guild funds as the actual amount is incorrect and only reflects a guesstimate of actual guild funds. Guild members believe its their own personal guild bank and let the collect wage funds pile up using it as a savings tool. This reflects billions of incorrect funds. (yes I mean billions, my guild has tested it) There is no proper way to do the banking and no real guilds fund TOTAL with the current coding for the mission funds. Imagine doing a massive guild payout of billions and then directly after the majority of members are then cashing out on billions more of uncollected mission wages. It can potentially leave the guild bank with a zero balance! There are a few options that can be created. It will require more coding but it really is needed. 1, actually divide the mission earnings to deposit member wages into a separate banking system that does not get totaled with guild funds. (It can then be used as a savings and never effect the guilds actual total what so ever). or 2, (I like this one best) put an expiration date on the collect wage feature. Members have until say... "the weekly update" to collect their mission wages or forfeit them entirely to the guild funds. Collect it or lose it but this will protect the guilds bank and allow proper banking for guild activity.