You're welcome to DM me the replayfile on Discord or in a private message here in the forums.
It sounds like you and an enemy sub ran into each other underwater, which is so incredibly rare as to suggest that you should go buy a lottery ticket right now.
The replay doesn't seem to work with 0.11.7. You may have chosen something from a prior version.
It might be because of a Hotfix which was released earlier today to fix the Railgun Bug. You might want to record the replay while your client hasn't updated yet.
If I recall correctly, Ramming code is tough to figure out. In general, as long as you are moving faster than a very slow speed, contacting another ship will deal an amount of damage equal to your full ship HP. There is a flag that can increase that while reducing the amount of damage you take in return.
If the ram happens at a very slow speed then some weird interactions can result. This used to be an issue when spectators for competitive matches had to ram each other and sometimes "failed the ram" or something.
I do provide additional clarity in areas. In general I believe having more information allows better decision-making and happier players, so it's something I do aim for in general. However, there are limits to what is reasonable to share or not.
From what I understand, Ramming code is fairly complex/awkward and wouldn't be easy to learn or convey.
-
While it would be interesting to have it fully laid out, these are the roadblocks:
A full and complete explaination to me before I could relay it.
The problem with this is that Ramming is niche enough that I don't require this information. In effect, it's wasted time from an employee standpoint in both my time and the time of the others that would have to dig it up and train me on it.
A detailed breakdown of Ramming is not required for the game to be understandable.
Rams are rare enough and mostly function via "ships collide and deal their max ship HP damage to enemy they collided with". Dialing down to the minutiae would be fun, but it really isn't necessary outside of answering curiousity.
There are limits to the information we share as our game is our intellectual property.
If information is not required to allow the game to function, there is a very real reason to keep it internal-only. We make and offer a product just like Coca-Cola or other companies. Guarding our recipe/secret sauce is sane from a business perspective.
Those are going to be qualifiers on any information request/ask.
Is it time prohibitive to learn and relay?
Is it needed for gameplay to be understandable?
Is it oversharing?
I've lived across a few MMOs and LARPs over my decades of gamer'ing. Literally part of the content of each game was the process of breaking down how things worked and determining optimal uses.
In World of Warcraft, determining background mechanics for spell interactions, threat, resistances, stats, and a variety of bossfights. The information was figured out and guarded by some while being shared by others.
In my first LARP there were players that figured out the math/roll mechanics that GMs used to determine ritual success/failure. Players also determined the mathematical concepts that the magic system was based on and used it to force the devs of the LARP to allow them to create spells with should have been possible according to such a full understanding of the system. While the spells were not intended to be part of the game, the game runners decided they couldn't say no.
In EVE Online there is extreme attention paid to building and sourcing mechanics so that players can play the markets/speculate the markets prior to each new release of content. There is a wealth of information provided on certain topics in game but little understanding of how they work until players grind it out and turns in-game knowledge into content and/or power.
For myself, I made this: https://forum.worldofwarships.com/topic/239175-ahskances-lesson-compendium-the-overly-large-videobook-of-cv-everything/
That post contains some 160+ videos that were made through active interaction with WoWs and its systems. I'm interested in systems and learning how they function, so I quite literally stayed engaged with this game for years while learning and teaching what I learned.
I started in this game around 3.5 years ago, so I started after much of what you listed above was already listed in the port interface. I appreciate having had access to the information, but I can honestly say that it was an overwhelming amount of information that took me years to take in. Part of our concern in putting out as much information as possible is that it is overwhelming when new players have their first interactions with our game. While giving you a detailed description of Ramming Code isn't likely to run off a new player, there is still the situation of "Does this need to be done?". If it doesn't, and I don't believe it does in this case, then leaving it unanswered does provide something for people to test and theorize about which isn't a bad thing.
devtrackers.gg