No need to disable or revoke admin on a script during a sit. No - If you have an admin script and someone sits your account, it will behave just like a regular non-admin script when they run it. Q: I've got an Admin script and someone is sitting my account, should I delete my script/disable Admin? (So vault "admins" are really just "group admins".) Whenever an admin makes a new script, it's automatically placed into their group. No - every time you make a new script through the Register page it's placed in a new "group" - any script can only see data from others in the same group. Q: Can others using the Vault on the same world see my info? (ie, a council member sending troop spreadsheets to enemy tribes.) This gives the Vault a bad name and gives me a headache – I don’t want to deal with it.
Scripts may be revoked, and players may be banned from the Vault for inappropriate behavior – this includes hacking attempts, and general douchery. I will never forcibly revoke scripts for the benefit of any person. Data is provided to Vault Admins in an aggregated form to promote accountability without leaking damaging information such as specific troop locations.
Features provide just enough information to be useful, without providing so much information that a single spy could compromise all of a tribe's data. Privacy and security were major parts of the script's design.
It is not perfect (no system is) but is more than sufficient to deter even experienced developers.Īll features in the script were designed to provide features without leaking information. The script was designed with various layers of protection to prevent spoofing/hacking. I will not share this data with anyone other than player(s) that own the data. As the developer, I may pull any data from the Vault database at my own discretion only for debugging, development, or analytics. Advanced data exports: I am able to directly connect to the Vault database and retrieve more detailed information than users have access to (necessary for cross-referencing incorrect data when troubleshooting an issue, usually only used for problems with incoming tagging or incorrect troop estimates)ģ.
#Tribal wars 2 beta key manual
Manual privilege overrides: I am able to reassign any Vault user to a Standard, Admin, or System Admin token (necessary for permissions testing)
#Tribal wars 2 beta key code
Script impersonation: I am able to use any player's Vault script and spoof the code to run as though I were the intended user (necessary to view problematic behavior without needing to record a user, connect to their machine, or sit their account usually only used for problems with high scores or Admin spreadsheets) As the developer, I have the following tools at my disposal but will not use them for the gain of myself or others, which are limited to debugging or development purposes: (This would quickly lead to banning of the vault script.)Ģ. I am able to but will never deliberately modify or expose data for the benefit of myself or my tribe. I disclose these methods here for transparency and clarification.ġ. All requests through the script are logged with your IP, user ID, tribe ID, and various request information such as the endpoint.Īs the developer, I have access to various features and information not accessible to other players. Information collected by this script will never be shared with any third parties or any unauthorized tribes/players. Data that you upload is visible to vault admins in your group (aka tribe) and nobody else. Action notifications, ie notification when an ally uploads an incoming train to the Vault, showing target village and landing timeĪll requests to the script are IP-logged for security. Tribe council easily sees troops and participation from all tribe members if you upload a report, scripts for other tribemates will take your report into account automatically.) There are 5 big features in this script (and many, many smaller ones): (See screenshot below.) Tribemates that upload will add to the pool of data that the vault has to use, and benefits everyone using the script in your tribe. This script takes your reports, commands, incomings, and troops, and uses this to provide useful information. Each user must get their own script for each world - instructions below. This previously private script is now open for general use. This thread will soon be closed.įull source code (with some config files) is now at: Someone else will need to host the Vault. Scripts can no longer be generated from the Public Vault. New: The Vault has been shut down early, as of Oct. The script was approved for a few months, but was banned near the end of 2020.
0 kommentar(er)
