New WOE bet npc

[starlight]

Woe Bet npc

bet who wins the upcoming woe

To prevent exploits there shouldn't be any money injected into the server through the system.
winners share the sum of all losers' money according to the ratio of money they put in.

( A bet 5, B bet 20 on winning side. if sum of loser money is 100, then A get 20 and B get 80)



This is how the template might look:

How can I help you?
-bet
-menu for 3 woe times.
-deposit
guild menu
insert the amount of zeny [input]
-withdraw (to prevent exploit, might be good idea to disable it 3 days before woe)
guild menu
insert the amount of zeny [input]
-claim reward => you have gained [#] amount of zeny
-Current bet
-menu for 3 woe times.
-display guilds/amount bet on
-Your bet
-display your bet/s


At specific time (after woe, sunday midnight etc)
server distribute money to winners.


What do you think?

[Kiana]

This is a plausible idea, Koma will look into scripting this. Though if its not used often enough it would end up being removed from the server.
So we need to see some support for this before we go into it full force as there is a considerable amount of research into go into this before hand.

[Muffin]

I am against this. It's too easily abusable.

[Tri Edge]

I would definitely use this xD. It would make me try harder when it comes to woe, lol that way i can get some money back for the materials i use durring woe. I think its a pretty interesting a idea.

[starlight]

I am against this. It's too easily abusable.

Some possible abuse:
-A major guild suddenly skipped woe or pretend to lose woe for bet profit
skipping woe also means no treasure profit,
I am not sure how much money people are willing to put into these if little it probably wouldnt happen.

Since bet money doesn't come out of no where there are always losing people that will help keep track of abusers
Problem with this is it might cause headache for gm trying to proof someone guilty...

But on good side, beside the fun of betting, it gives some random people/smaller guilds an incentive to attend woe (to win bet) making woe more interesting.

I hope no one abuse it. I don't think it is worth sacrificing guild reputation for only a tiny bit of money.

[Koma]

Yes, as previously mentioned, this is plausible, but full details on how the system interacts with players is a high concern. I'm probably going to have to full research "game betting" gambling unless someone comes up with a detailed description of how this should work.

The incentive to keep a castle should be worth it though in regards to abuse. This is similar to a team winning a sports game, but you never know.

[Dowe]

Hrm...As for the returns of the bet... Maybe IF you are correct in your bet you get your money back and the money from people who were wrong is divided proportionally between the people who guessed correctly.

At this point in time, the system could be customized to suit the desires of the admin. Note: these would be configured to suit the desired system so not all of these would be implemented exactly how it is listed (obviously). Not all of the suggestions work with each other, they are just different aspects that could be implemented to the system.

_____________________________________________________________
1) People can place bets on their OWN guild only.
This way, a guild or members cannot effectively "rig" a game one week to make a small fortune that MIGHT outweigh treasure. (Remember some leaders don't share treasure, so some members might purposely not WoE so they can get some cash).

Pros:
Would limit abuse of the system.

Cons:
Would limit the system to WoE participating people only.
Would basically make the strong guild richer if they continually win WoE. This would no doubt end in the non-use of the system.

_____________________________________________________________
2) A Bet Cap
A simple limit to the maximum bet possible could prevent some forms of abuse, such as very large bets by one person.

For example:

Total amount of zeny to be split between the winners is 1m.

5 people have bet between 0z - 100,000z.
1 Person has bet 100m zeny.

To be an effective (scaled/proportionate) betting system, the winnings must be split between the winners based upon how much they bet. The 100m bet would obviously get the majority of the winnings (they WOULD be risking a lot more though).

_____________________________________________________________
3) Maximum 1 Bet: Per WoE-Per Account. Lvl 85 Minimum character level
Basically the same as above. This could be avoided quite easily, but at least it would be in place to stop large bets to some extent (when used with a bet cap).

_____________________________________________________________
4) Fixed Bet Size
For example: The only bet size a person can bet is 500,000z. This would also mean everyone gets the same portion of the winnings.

_____________________________________________________________
5) Total Prize Pool Information

A) Hidden or Non-Specific Information
What I mean by this is that the NPC would give little or no information regarding how much money has been bet so far and how much they stand to win if they do in fact win.

Let us assume that a person has bet that "Guild X" would win (and won). While they were placing their bet for "Guild X", if the total pooled zeny was hidden, they would not know if the total amount bet on "Guild Y" was 10,000z or 10,000,000z.

B) Limited Information
Average bet size is shown to the user (as a general range or possibly specific amount), but information regarding which guild the money was bet on (by everyone else) is unknown. For example: The NPC would say if the average bet was "1z to 499,999z", "500,000z to 999,999z" or ">1,000,000z".

C) Specific information shown
Total of All Bets could be shown. Example:
"54 people have bet a combined of 535,342,003z. The average bet size is 9,913,740z"

D) All Information available
Example:
"A total of 500,662,442z has been bet on Guild X"
"A total of 350,342,012z has been bet on Guild Y"
"A total of 50,972,052z has been bet on Guild Z"
"Average Bet Size is 1,565,232z"

_____________________________________________________________
6) Tweaking the Economy
The total prize pool could be increased or decreased depending on what the admins want. If you feel there is too much zeny then the NPC could be used to reduce the overall amount of zeny in circulation. If you feel there isnt enough though, then zeny could be added to the prize pool.

For example, the NPC could take a 10% commission, so the total prize pool is only 90%.
Alternitively, the NPC could ADD 10% zeny to the prize pool (or possibly add the amount of zeny based upon how many people bet on this result). This would also serve to boost the systems popularity and have more people use it.
_____________________________________________________________


I personally would like the NPC have:
2) A Bet Cap
3) Maximum 1 Bet: Per WoE-Per Account. Lvl 85 Minimum character level (But can alter their bet before the start of WoE)
5)B)Limited Information OR 5)C) Specific Information
6) +/-10% To Total Winnings (+10% is what id like to see rather then -10%)



Anyway, Im a little pressed for time so i might fix this post up later and add some ideas

[starlight]

see below for new rewritten code

[starlight]

1) People can place bets on their OWN guild only.
No No, No fun
This npc is also suppose to make outsiders attend woe to turn tide and make woe more fun

2) A Bet Cap
This seems to be a misnomer? but according to the explanation..
Yea this is what I mentioned in previous posts about splitting losers money according to ratio of winners bet money. So... agreed.

3) Maximum 1 Bet: Per WoE-Per Account. Lvl 85 Minimum character level
More unnecessary work for coders? I don't think this is any use unless you are trying to cap betting amount per person

4) Fixed Bet Size
Limiting bet kinds of make it less fun in my opinion but might solve problems with big guilds manipulating win lose since there won't be enough incentive to do so with less money in.
Way to get around, multichar/ids.... Ways to prevent it, min lvl added.(Although i know some people with 10+ 90+ high class ids)
In my opinion, there is no need for this.

5) Total Prize Pool Information
A) Hidden or Non-Specific Information
Good for preventing exploits that can be done by core guilds.
But takes some fun out of it. Nothing more to look at after putting in money. Less bet on losing side.

For this, I think we can mix as will be explained below i think.


6) Tweaking the Economy
negative= tweak-less people participating.
positive= inflation

**************************
Conclusion: (what I think would be best)

Ratio System:
See first post.

Min CAP:
Minimum per bet (may be 50k?). (better than inserting transfer fees in my opinion)

INFO:
if lower than 2m combined bet on that woe, no info available.
else show all
This way people will not hesitate to be the first to put money in against 0 or very little bet
******************

[starlight]

Koma help please T-T

wrote everything up again->
This time start on Core Calculations parts.
Since I don't know a way to write a code to go through all account-variables on

its own, I tried to write something that will make the calculations for rewards

specific to person when they talk to npc.
This means deadline for retrieving reward is the next calculation time(OnMon0000)

or else all will be erased to prevent exploit.
Not sure if 2D array work or not so i just use 1D for now.


OnInit:



OnMon0000:

//get total reward each woe from last week's total bet
set $FE1Reward,$FE1TotBet;
set $FE2Reward,$FE2TotBet;
set $FE3Reward,$FE3TotBet;
set $SEReward,$SETotBet;

//renew total bet
set $FE1TotBet,0;
set $FE2TotBet,0;
set $FE3TotBet,0;
set $SETotBet,0;

//Get winners for each woe
set $FE1Winner$,;
set $FE2Winner$,;
set $FE3Winner$,;
set $SEWinner$,;


//set winner total bet (for reward calculation)
for( set .@i, 0; .@i < $AllG ; set .@i, .@i+1 ){
if($FE1Winner$==$GName$[.@i]){
set $FE1WinnerTotBet,$FE1GTotBet[.@i];
}
}


for( set .@i, 0; .@i < $AllG ; set .@i, .@i+1 ){
if($FE2Winner$==$GName$[.@i]){
set $FE2WinnerTotBet,$FE2GTotBet[.@i];
}
}


for( set .@i, 0; .@i < $AllG ; set .@i, .@i+1 ){
if($FE3Winner$==$GName$[.@i]){
set $FE3WinnerTotBet,$FE3GTotBet[.@i];
}
}


for( set .@i, 0; .@i < $AllG ; set .@i, .@i+1 ){
if($FE1Winner$==$G01N$){
set $FE1WinnerTotBet,$FE1GTotBet[.@i];
}
}

//Renew all bets.

for( set .@i, 0; .@i < $AllG ; set .@i, .@i+1 ){
set $FE1GTotBet[.@i],0;
}
for( set .@i, 0; .@i < $AllG ; set .@i, .@i+1 ){
set $FE2GTotBet[.@i],0;
}
for( set .@i, 0; .@i < $AllG ; set .@i, .@i+1 ){
set $FE3GTotBet[.@i],0;
}
for( set .@i, 0; .@i < $AllG ; set .@i, .@i+1 ){
set $SEGTotBet[.@i],0;
}


set $CurrentWeek,$CurrentWeek+1;


prontera,<x>,<y>,<facedir> script WoeBet <sprite id>,{

if($CurrentWeek == #BetWeek+1){
//if this is new week, Give last week's bet reward.

if($FE1Winner$ == #FE1BetName$){
set Zeny,Zeny+$FE1TotBet*#FE1Bet/$FE1WinnerBet;
mes "Last week Morning FE bet reward:"
mes $FE1TotBet*#FE1Bet/$FE1WinnerBet+" Zeny";
next;
}
if($FE2Winner$ == #FE2BetName$){
set Zeny,Zeny+$FE2TotBet*#FE2Bet/$FE2WinnerBet;
mes "Last week Afternoon FE bet reward:"
mes $FE2TotBet*#FE2Bet/$FE2WinnerBet+" Zeny";
next;
}
if($FE3Winner$ == #FE3BetName$){
set Zeny,Zeny+$FE3TotBet*#FE3Bet/$FE3WinnerBet;
mes "Last week Night FE bet reward:"
mes $FE3TotBet*#FE3Bet/$FE3WinnerBet+" Zeny";
next;
}
if($SEWinner$ == #SEBetName$){
set Zeny,Zeny+$SETotBet*#SEBet/$SEWinnerBet;
mes "Last week SE bet reward:"
mes $SETotBet*#SEBet/$SEWinnerBet+" Zeny";
next;
}

}
set #BetWeek,$CurrentWeek;




LbetmorningFE:
mes "[Woe Bet NPC]"
mes "Available guilds to bet on?"
for( set .@i, 0; .@i < $AllG ; set .@i, .@i+1 ){
mes $GName$[.@i];
}



}

Note:
<...> are to be replaced with something
<<<<<<<<< means need to add stuff