03-31-2010, 04:08 PM
I want a better banking system and this is what I purpose.
/bank
1. /setclientcode <CharName><Code> (4 number code) (This is the code that the bank receives from client not the bank setting the code for the client.)
2. /loan <Char Name><client code><Amount><interest> (Interest is 4 settings which is: 0% - 10% - 15% - 20%)
3. /checkpay <CharName><Code> (Checks the amount left that your client needs to pay.)
4. /lean <CharName><Clientcode><On/Off> (Will forcefully place a garnish amount every time the player makes over 1 million credits which would be 350,000 credits. This lean is placed till it matches the loaned amount plus interest. This is accessed through the giving client code, that overrides the cashcode, if they had set one up.
At this point I think this is enough and more can be suggested. But I will provide a sample of how this would be used.
Gary asked for a loan of 10million
Bank agrees.
Gary:/setclientcode Gary 1234
OK
Gary gives the code to the bank.
Bank:/loan gary 1234 10,000,000 10 (11,000,000)
OK money transferred
It has been a 2 weeks the bank wishes to know how far Gary is to playing the loan off.
Bank:/Checkpay Gary 1234
ok
11000000/0 (Amount owe/Amount paid)
The bank tries to contact Gary to pay but he has been less then willing to talk. In a final effort the bank needs the loan to be leaned.
Bank: /lean Gary 1234 on
ok
payment received 11000000/350,000 (will continue till it reaches 11million if the auto pay exceeds 11million the left over will not be carried over to the bank)
Bank happy.
For every new loan the client must change his client code. Then after a month of not having the previous client code accessed it will auto delete from records. This really gives a more ability to protect your business since from my understanding that admins will not lean fines for not playing the loans. Which I've argued is under the fraud stipulations. But this is what I find as a acceptable alternative to this issue. Otherwise feel free to comment and offer suggestions.
Thank you,
Zigeris.
/bank
1. /setclientcode <CharName><Code> (4 number code) (This is the code that the bank receives from client not the bank setting the code for the client.)
2. /loan <Char Name><client code><Amount><interest> (Interest is 4 settings which is: 0% - 10% - 15% - 20%)
3. /checkpay <CharName><Code> (Checks the amount left that your client needs to pay.)
4. /lean <CharName><Clientcode><On/Off> (Will forcefully place a garnish amount every time the player makes over 1 million credits which would be 350,000 credits. This lean is placed till it matches the loaned amount plus interest. This is accessed through the giving client code, that overrides the cashcode, if they had set one up.
At this point I think this is enough and more can be suggested. But I will provide a sample of how this would be used.
Gary asked for a loan of 10million
Bank agrees.
Gary:/setclientcode Gary 1234
OK
Gary gives the code to the bank.
Bank:/loan gary 1234 10,000,000 10 (11,000,000)
OK money transferred
It has been a 2 weeks the bank wishes to know how far Gary is to playing the loan off.
Bank:/Checkpay Gary 1234
ok
11000000/0 (Amount owe/Amount paid)
The bank tries to contact Gary to pay but he has been less then willing to talk. In a final effort the bank needs the loan to be leaned.
Bank: /lean Gary 1234 on
ok
payment received 11000000/350,000 (will continue till it reaches 11million if the auto pay exceeds 11million the left over will not be carried over to the bank)
Bank happy.
For every new loan the client must change his client code. Then after a month of not having the previous client code accessed it will auto delete from records. This really gives a more ability to protect your business since from my understanding that admins will not lean fines for not playing the loans. Which I've argued is under the fraud stipulations. But this is what I find as a acceptable alternative to this issue. Otherwise feel free to comment and offer suggestions.
Thank you,
Zigeris.