Fishing (Game Mechanics)
This article or section needs proper wiki formatting. |
Game Mechanics - Mechanics Category
SWGANH Wiki is a repository of Star Wars Galaxies Developer information. This site is only meant to be used by SWGANH Developer team.
|
Game MechanicsFishing is type of mini game that serves as both a resource and item collection event. Resources are collected from fish that are caught and filleted. Fish resources work similarly to other resource mechanics in that each planet has its own variation of fish resources and follow resource shifting behaviors. Items are looted in the forms of "catches" like fish and the player has to go through the same process to get them as catching the actual fish. Items such as chum baits, come as byproducts of the filleting process. It is unknown as to exactly what all items were available for fishing but it is generally accepted that the majority of items were not very useful or in essence "junk" although there are reports of items such as skill attachments, weapons and holocrons coming as loot so it would appear that fishing loot tables are perhaps linked to the general loot tables from npcs.
Operating The Fishing PoleThe fishing pole is at the heart of fishing since it is a required tool in order to be able to fish in star wars galaxies. Fishing poles act as containers (for bait only) as well as having a quality rating on them. Pole quality can range from 0 to 100%. According to some sources, fishing pole quality lowers the chances that bait will be lost during the fishing process, although by how much, is unknown. In order to fish, a player must first have a baited pole. To bait a pole, the player must drag and drop a bait item over on top of the fishing pole or manually open the fishing pole through the radial menu and drag and drop the bait into the pole container. This will bait the pole and all bait uses will be automatically deducted from the stack size of the bait in the fishing pole. In order to start fishing, the player needs to then equip the pole. Once the pole is equipped the player can then utilize the Start Fishing radial option on the pole or issue the /fish command to begin fishing.
Fishing EventsMaybe we shuold have it so that the tug options are linked to the chance that the fishing engine will swing the Caught Somthing event around to the player. FOr example we could set certain combinations to increase significantly, the chance that the Caught something event will occur with the next fishing update if the player executes the appropriate combo. For example, a combo could be two left tugs in a row or two right tugs or a combination of tug right, tug left etc. The player could have a base chance of the Caught something event occuring if they just use any tug option but of course, executing a combo would dramaticaly improve their chance and thus save them some time (which would be the incentive for executing combos).
Start Fishing Process:Fishing can be initiated through two means: 1. /fish command To start fishing, a Player has to be 2 meters from the water source and physically facing the water to where a direct line can be drawn between the player and the bobber when the /fish command is sent. The player must also have a fishing pole and there must also be bait inside the fishing pole. If they meet these requirements then they can successfully execute the fish commands. Once the fishing commands are executed, the player throws out their line and an Fishing Events sui prompt is presented.
Stop Fishing ProcessThings that stop the fishing process:
Event Window StatusThe event window is broken up into several sections:
Whenever a player casts their line, a 7 second timer is begun that creates and updates an SUI window that rotates between 6 status events; Waiting, Nibble, Bite and Caught Something, Line Snagged, Reel-In. The first 4 events are tiered from lowest to highest with waiting being lowest and Caught Something being the highest. The first two events (waiting and nibble) are automatically generated by the fishing engine, while the other two are based on actions taken by the player. Every 7 seconds A random roll is made to check if an event will raise to the next level or fail completely. If the event check fails, then it is sent back to the lowest event (waiting) to begin again. In each of the 4 primary events (waiting - caught something) there is a chance to encounter sub events such as losing bait, which immediately causes the fishing process to stop. Some types of bait loss events that occur, are unique to certain events.
Fishing Window User Input Options:There are 5 fishing window user input options that allow the player to manipulate certain aspects of the fishing process. To use them, the player selects an option, and then clicks the OK button. After this is done, the window updates and lists the queued action in the Next Action listing of the window. This action will be executed at the start of the new event cycle (an event cycle occurs every 7 seconds during the fishing process). When one of these options are used, the player initiates a unique animation at the next window refresh cycle. It is believed that when some of these options are used (tug inputs in particular) they will affect the chance for a new event (nibble, bite, caught something) to occur. It is believed that the server selects some button or a combination of buttons to be used for each 7 second interval that the windows refresh. If the player hits the right button or sequence of buttons in a row, their chances to initiate the next higher event will dramatically improve. No known formula or values for how this process works exist so we will need to make something up.
1. Tug Right: Shortens distance between player and line bobber, indicates player wants to move to the Bite and Caught Something events, and also affects the chance to achieve a new event. Any time an action is initiated, the window will update to display what the action will be at the next 7 second update. As the window updates, an animation for the action is initiated.
Shortens distance between player and line bobber, indicates player wants to move to the Bite and Caught Something events, and also affects the chance to achieve a new event.Any time an action is initiated, the window will update to display what the action will be at the next 7 second update. As the window updates, an animation for the action is initiated. 3. Tug Up: Shortens distance between player and line bobber, indicates player wants to move to the Bite and Caught Something events, and also affects the chance to achieve a new event.Any time an action is initiated, the window will update to display what the action will be at the next 7 second update. As the window updates, an animation for the action is initiated. 4. Reel In: Shortens the distance between the player and line bobber. Has no effect on events.Any time an action is initiated, the window will update to display what the action will be at the next 7 second update. As the window updates, an animation for the action is initiated. 5. Stop Fishing: Stops the fishing process, regardless of what stage the player is on.
Events1. Waiting Event
Bait stealing - whenever an update occurs, fish have a chance to steal bait and thus stopping the fishing process.
Other Events:
Nibble Events - Randomly chosen messages when the player gets a Nibble event.
When a bite event occurs, the player can use the Tug options. Each of these options can affect the random roll event to progress from nibble to caught something event. I believe that the engine selects a correct choice to make at each event stage starting with "waiting" and that when a player selects the correct choice (tug up, left or right) that they increase their odds of reaching the next stage. The player isnt given any indication of which may be the right choice however. Players do not need to use a tug option to advance to the Caught Something stage. The random roll engine automatically determines every 7 seconds if the event will pass to the next stage (Caught Something).
Other Events:
4. Caught Something Event When the highest level of event is reached (caught something) the fishing engine moves to a new set of random events that involve reeling the catch in which ultimately determine if the player will obtain the fish or not.
5. Line Snagged?
Events:
6. Reel-In Event
Note; These are estimates based on my own anecdotal observations from observing the various events unfold. A More scientific data collecting methodology would be preferred such as long duration packet captures and parsing the data. These values should just be used as a starting point. During the reel-in event, various actions can occur such as:
Bait StatusValues:
Random roll is made at each update to determine which state the bait is in. Each roll determines if the bait will decrease in status where fresh is the highest and mush is the worst. Bait status presumably affects the chance that the bait will be taken at each update. Upon starting the fishing process, Bait can be at any status from starting out even as mush. Bait can be lost at the start of any event except the reel-in event. The reel-in event has a unique handling of bait loss in that bait loss for it only occurs if the player has lost the catch. When the catch is lost, a random roll is made at that point to determine if the bait will be lost as well. There is no known formula for calculating how bait status affects the Bait loss rate so we will need to come up with something. It is presumed that fishing pole quality and bait status combine to affect the chance of the player losing their bait on any given event that allows bait to be lost. Line Range - (aka Fishing Bobber)Fishing process can start with the bobber being cast anywhere within the 2-10 meter range from the player. Once the fishing process has started, a bobber object is placed in the water in a direct line in front of the player and its position is updated as the player performs actions or when certain events occur. It is the player's responsibility to control the line range either with small reel in option on the event window or to physically move closer to the bobber position in the water. Line range is displayed as a float value up to two decimal places. If the player's line is at or beyond 45 meters of their current position by the time the window updates, the fishing event will be canceled. If the player's line is at or below 2 meters of their current position by the time the window updates, the fishing event will be canceled as well. The only exception to this is when the player is in the Reel-in event process. When this event begins, the objective is to get within 2 meters of the bobber in order to catch the fish or object, therefore the minimum distance rules are not enforced however the maximum length rules are still in effect. The fishing bobber can change positions under the following circumstances
Line Range Calculations Note; These are estimates based on my own anecdotal observations from using the various options. A More scientific data collecting methodology would be preferred such as long duration packet captures and parsing the data. These values should just be used as a starting point. Using the following status window options will affect the distance of the bobber
Source References
|