Hello Guest

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - MegaStar

Pages: [1] 2 3 4 5 6 7 8 9 10 11 ... 28
1
the cute lil workshop / [DISCORD] AoS Presence
« on: April 06, 2019, 01:32:05 PM HST »
I just updated this, I made a small program with which you can modify things more easily so you avoid doing everything through the config.ini

Advantage:
- Everything will be more orderly.
- Unlike the old version, now you can modify the data and update them instantly without having to reopen the program.
- The data will remain even if you close the program, this will make you avoid putting everything again the next time you open it.

The only thing you should do is fill in the boxes with the corresponding data, the list of servers is sorted by the number of players (from highest to lowest) to select a server just point and click it once (you can do more than 1)

Demonstration:


PD:
- It is advisable not to modify anything in the config.ini, do it through the program, thanks.
- To exit the program use the Exit button (important)

Download link:
http://www.mediafire.com/file/vgx5ukgxch6o56o/discord_presence.rar/file


Old version
Spoiler for unknown:
This time I come to share a Rich Presence that I did today in relation to ace of spades for Discord, you can customize it to your liking.

What you should do is download the openspades_presence.rar file that will be on the bottom, this contains an .exe file so your browser will probably send a message saying it is a dangerous file (actually it is not)
Once downloaded the file, watch this video, here I show all the necessary steps.


PD:
In the video is not shown but I add a new option in the config.ini, this option is called player_text_count, here you must put the message that will appear next to the player count (by default it will be in players)

Example:
player_text_count = nubs

Result:


Download: http://www.mediafire.com/file/5k5ebr049ck36u2/openspades_presence.rar/file


Thanks

2
the cute lil workshop / [SCRIPT] detect_bans.py
« on: March 20, 2019, 06:47:18 PM HST »
This script allows you to detect possible evading players, this is verified through the player's IP ranges, this also verify through the country, city, ISP and region.
This detection starting from 3 ranges of pairs of numbers (x.x.x.o) (obviously).


For example:
Player IP = 193.33.144.96
IP ban = 193.33.144.34

In this case there are 3 ranges of similarity, which would be:  193.33.144, the same happens if this find 2 ranges of similarity.
In 3 ranges or 2, the matches of Country, city, ISP and region may vary.

Messages:
"Ban evader detected" => If it detects 4 matches (country, isp, city, region)
"Possible ban evader detected" => If it detect 2-3 matches (this may vary)
"Unlikely ban evader detected" => If it detects 1 match (country)
"No matches detected" => If there is no match (this is only shown in the /compare command)
"1 range ip detected but 0 matches found" => in case there is 1 range of similarity between both IPs but they are from different countries (such as 181.1.75.205 (ARG) 181.141.75.205 (CO))

The detection by one only range (1 range ip detected but 0 matches found / Unlikely ban evader detected) by default is disabled, this is to avoid that warnings are shown frequently, but if you want to activate it you can use the command /toggleunlikely

Optional command:

/compare <ip1> <ip2>
This command is used to see the data of both IP, the range of matches will also be shown.

Example:
/compare 25.9.98.125 25.9.98.123
IP 25.9.98.125: Country: United Kingdom, City: Woodstock, ISP: UK Ministry of Defence, Region: England
IP 25.9.98.123: Country: United Kingdom, City: Woodstock, ISP: UK Ministry of Defence, Region: England
Matches: country/city/isp/region, type: Ban evader detected


PD:
When an evader or possible evader is detected, the script will send a warning to the administrators, moderators and guards that are available on the server, as well as on the IRC, something like this:



This would be better if a bot did it in the IRC, so we can verify more easily if a player is evader through the country/isp/city/region,  this will give us more precision even if both IPs do not match.
I will do it when I have time, thanks.

3
the cute lil workshop / [SCRIPT] checkban,py
« on: March 20, 2019, 06:39:09 PM HST »
The servers for default will always save the data of the bans in the file bans.txt, it does not matter if the IP of the player is banned again, the new ban will be saved causing the accumulation of bans with repeated IPs, I don't like this.

Seeing this, I decided to modify the code a little so that you can choose whether to let the new ban accumulateor that the old bans of that IP are eliminated leaving only the current ban (only if that IP has been previously banned).

If the option to accumulate the bans is enabled, this script will automatically get only the bans that did not expire leaving aside those that have already expired and still remain in the bans.txt, this will also get the ban with the longest if a IP was banned more than 1 time.

If the option of not accumulating the bans is enabled, the IP ban/nick will be obtained directly and it will be verified that the ban has not expired (in case it is still in the bans.txt)

To activate the option not to accumulate bans you must use the command /togglebans, otherwise use the command again in case you want to disable it, by default this will be disabled (the bans will accumulate)

That said, the purpose of the script is to obtain the data of a specific ban, you can search it through an IP or nick.

Example:
/check MegaStar
/checkban 127.0.0.1



Commands:
/check <ip/nick>
/togglebans => enabled/disabled

4
the cute lil workshop / [SCRIPT] build.py (updated)
« on: December 08, 2018, 04:48:49 PM HST »
This is my new build script, it's improved and now it can work without problem with any other script such as box, paint, floor, db, dw, wall, etc.
This new version contains registration and login to protect and save the sectors of each user, with this we avoid the grief and trolls users who want to cover or destroy the sectors with box, floor, db, etc.

The format of the database is in JSON and its structure is this:

{
   "<account username>": {
      "shared": [],
      "password": <password>,
      "coordx": <claim_pos_x>,
      "coordy": <claim_pos_y>,
      "ip": <user_ip>
      }
   }


<username>
Here is the account name of the user, it will never be repeated or there will be another like it.

"shared": []
Here will be stored users who can destroy and build in a player's sector.

"password": <password>
Here is the account password of the user.

"coordx": <claim_pos_x>
This is the position of the first block on the x axis (with this we avoid putting all the coordinates)

"coordy": <claim_pos_y>
This is the position of the final block on the y axis (with this we avoid putting all the coordinates)

"ip": <user_ip>
Here the IP of the user is saved, with this we avoid that more than one account is created.


Size of the sector per user:
The default size of the sector per user is 30x30 blocks, you can modify this in line # 13 of the build.py script

RANGE_CLAIM = 15
Keep in mind that the value you put there will be multiplied by 2, therefore 15 would be 30 blocks (default)


Commands:

/buildregister <username> <password>
/buildlogin <username> <password>
/share <account username>
/unshare <account username>
/removeclaim <account username>
/buildlogout
/claim
/tpsector

buildregister:
This command allows you to register on the server, you need to put the name of your account and password.


buildlogin:
This command allows you to enter your account, you need to enter the username of your account and your password.

share:
This command allows you to share your sector with another user, you need to place the account name of that user, keep in mind that he will be able to destroy and build in your sector.

unshare:
This command allows you to remove a user from your list of users who can build and destroy in your sector, you need to place the account name of that user.

tpsector:
This command will teleport you to your sector.

claim:
This command allows you to claim a sector, you can only claim 1.

buildlogout:
This command allows you to exit your account.

removeclaim:
This command can only be used by administrators, you need to place account name of that user to whom you want to remove their sector.

Users will not be able to build or destroy anywhere until they register, login and claim a sector.


IMPORTANT:

- Only administrators can build and destroy on the entire map without having to register, be careful with this.
- It does not matter if a user has /god, he can only build and destroy in his sector (also in the sectors where he was given the permission to destroy and build).
- Use a auto savemap script like savemap.py, with this we avoid that some constructions are lost in case your server closes.
- Put a message in your config.txt saying that to build you need to register, login and claim a sector.
- Download the build.py file and put it inside your scripts folder.
- Download the users.json file and put it inside your dist folder.
- If you change the size of the claim (RANGE_CLAIM) avoid that it is not so big.
- You can only register once, as a consequence the users can only claim a single sector

A small example of the script working:



In the video I registered with two accounts to show how the script works but this only be done once.

Thanks.

5
the cute lil workshop / [SCRIPT] helpban.py
« on: July 26, 2018, 05:58:42 PM HST »
This script may be helpful, the purpose of this command is to make it easier to ban a player during a certain time, usually the "/ban" command takes the "time" through the minutes, so 1 day will be " 1440 ", 2 months would be" 87600 ", 1 week" 10080 "etc.

Commands:
- /mban [#player ID or nick] [format time] [reason]
- /checkban [ip]


- The /mban command has special characters:

p = permanent ban
m = ban for months
w = ban for weeks
d = ban per days
h = ban by hours
t = ban per minutes (I do not think this is necessary but I also put it in case someone needs it)

Permanent ban
- In case you want to ban a player permanently you will only have to use the following format:

/mban [player] [p] [reason]

For example:

/mban #2 p esp/ab

Ban per months
- If you want to ban a player either for 1 month or more you should use the following format:
/mban [player] [number of months / m] [reason]
For example (ban for 2 months):
/mban MegaStar 2m for being cool

Ban per weeks:
- If you want to ban a player either for 1 week or more you should use the following format:
/mban [player] [number of weeks / w] [reason]
For example (ban for 1 week):
/mban #2 1w superjump

Ban per days:
- If you want to ban a player either for 1 day or more you should use the following format:
/mban [player] [number of days / d] [reason]
For example (ban for 3 days):
/mban #2 3d evasion/esp

Ban per hours:
- if you want to ban a player either for 1 hour or more you should use the following format:
/mban [player] [number of hours / h] [reason]
For example (ban for 5 hours):
/mban #3 5h griefer


Ban per minutes
- If you want to ban a player either for 1 minute or more you should use the following format:
/mban [player] [number of minutes / t] [reason]
For example (ban for 30 minutes):
/mban #3 30t votekick abuse

- When a player is banned, the script will send a message to all administrators saying that the "player" has just been banned by "name of the admin/guard/etc" for "duration of the ban" with the reason of "reason of the ban"
Example:
"MegaStar was banned by MoDeR for 2 months with the reason of: for being cool"

Checkban
- Each ban that is done with the command /mban, in a file called "banformat.json" will be saved the following data of the banned player:

- Nick of the banned player.
- IP of the banned player.
- Reason why he was banned.
- The day and time he was banned.
- Nick of the admin/mod/guard/etc that gave ban him.
- For how long was he banned.


To use the command you should only use command /checkban [ip], for example:

/checkban 233.233.122.23

IGN: MegaStar
Ban duration: 2 months
Reason: for being cool
Ban date: 2018/07/26 [20:35]
Banned by: MoDeR

Optional

- Usually when someone bans a player with the command "/ban", in the global chat everyone can see the data of the ban, for example:

PabloEscobar was permabanned: esp/aimbot
MegaStar was banned for 999999 days, 19 hours, 59 minutes

- In this script that can be configured, when you use the command "/mban" and you want that in the global chat nobody can see the data of the ban does and only show the message "was banned." for example: "MegaStar was banned", you must open the script and in line #19 "TOGGLE_GLOBAL_MESSAGE = True" you must change the True and set it False => TOGGLE_GLOBAL_MESSAGE = False

- For default I have put it in False.
- The /mban command can only be used within the game.
- The command /checkban can be used within the game and through the console (run)
- Make sure you download the file "banformat.json" and put it inside your dist folder (dist/banformat.json)

Any questions you have, just put your question on this topic, thank you.

6
the cute lil workshop / [GAME MODE] versus
« on: June 10, 2018, 06:54:09 PM HST »
Game mode: Versus

Commands:
- /versus <player> <number of kills (default is 20)>
- /accept <player>

- To challenge a player you should use the command /versus <name or #ID> <number of kills> (example: /versus #2 30)
- Once you challenge a player, that player will receive a message saying that you are challenging them.

- When you want to accept a versus, you must put /accept <player> (example: /accept #1), when you accept the challenge, all the players that are in the server will automatically join the spectator team at the exception of you and the challenger.
- Those who are in the spectator team will not be able to join any team and will not be able to use the /versus or /accept commands until the versus is over.

- When you accept the versus, you and the challenger will join a random team, either blue or green (this is to avoid if both the challenger and you are on the same team)
- There will be a count remain of 5 seconds, when reaching 0 a message will be sent saying the following:


"The versus (your nick) and (nick of the challenger) have started!"
"The player who reaches (maximum kills to win the versus) kills is the winner!"

- The script every 30 seconds will show the current kills of both players:

"(Player (nick of the challenger): kills: (kills of challenger)) --- (Player (your nick): kills: (your kills))
"Goal of versus: (maximum kills to win the versus) kills!"


- When a player is the winner, the script will send a message saying:

"(nick of the winner) is the winner!"
"#########"
"######"
"###"

- When finishing the versus again the team's will be unblocked and it will be possible to start again a new versus.
- When a player, whether you or the challenger, leaves while the versus has not ended, a message will be sent saying that the Versus has not ended for the reason that the (player) retired while the Versus had not yet finished and everything will be unblocked again so the players can choose a new versus again.

- The players will not be able to kill, destroy and build, all this will be enabled only when a versus has started therefore only the players of that current "versus" will be able to build, destroy and kill, everything will be disabled when the versus has finished.

Demonstration:



Perfect maps for this game mode, they would be assault and pinpoint, you can also use small maps.

7
the cute lil workshop / [SCRIPT] Build
« on: June 08, 2018, 04:10:38 PM HST »
Game mode: Build
There are no killings, only construction (the name says it :P)
There is a glitch in which is that you can destroy unbreakable blocks (I will not say how it is done) but in this script that glitch/bug does not work.

Commands:
/claim: Claim a sector (you can only claim 1)
/sector: If you are far from your sector and want to teleport to your sector, just use this command.
/removeclaim <player>: (only for administrators)
/ask <player> <question (optional)>: Ask the player if you can destroy their blocks.
/allow <player>: Allow a player to destroy your blocks.
/remove <player>: Revoke the player's permission so that he can no longer destroy your blocks.


/claim:
How to use it: You must put the command /claim and choose the place where you want to have your sector, if you want to choose the color of your sector you should only change the color of the block you have, once you have chosen the place and the color only you should hit the block that is at your feet.
-The claim will not work if you choose a sector that is in the range of another sector, you must ecoger a good sector.
-The default of the size of a sector is 20x20 cubes, no one can place or destroy any block that is within your sector (claim) either up or down (it could be said that your sector has the shape of a perfect quadrangular prism)
-If any player has permission to destroy your blocks (/allow), anyway he will not be able to place or destroy any block in your sector since the sector is only for you but  he can break your blocks that are outside your sector.

-If you want to change the size of the sector per player (I do not recommend it) you must open the script and in line #15 (RANGE_CLAIM = 10) you must keep in mind that the number you put in RANGE_CLAIM will be multiplied by 2, suppose that you put 15:
RANGE_CLAIM = 15
therefore the sector size per player will be 30x30 blocks (cimetric base).

/sector:
How to use it: You must put the command /sector and you will automatically teleport to your sector, this can be useful if you are in another place and want to return quickly to your sector.

/removeclaim:
How to use it: You must put the command /removeclaim <player name or #ID> (example. /removeclaim MegaStar)
-This command will allow you to remove the sector of a player, keep in mind that when removing the sector of a player, that player can choose a sector again.
-If the <player> does not have any sector, the command will not run and the script will send you a message saying "the player (player name) does not currently have a sector."
-This command can only be used by administrators.
-If the sector of the <player> is removed successfully, that sector will count as null, therefore they will be able to build and destroy since the sector will not exist.

/ask:
How to use it: You must put the command /ask <player name or #ID> <question (optional)> (example: /ask # 2 can I help you?)
-If nothing is passed in <question> the default question will be "can I destroy your blocks?".
-When the command is used, the <player> will receive that message and decide if he will let you destroy his blocks.

/allow:
How to use it: You must put the command /allow <player or #ID> (example: /allow MegaStar)
-If the <player> currently already has permission to destroy your blocks, the script will send you a message saying "The player currently has the permission to destroy your blocks."
-When a player asks you something with /ask, to accept it you only have to put /allow <player name or #ID> and automatically the player can destroy your blocks.

/remove:
How to use it: You must put the command /remove <player or #ID> (example: /remove # 2)
-This command will allow you to remove the privilege to a player who previously you gave him the permission (/allow) to destroy your blocks.
-If the <player> currently does not have permission to destroy your blocks, the script will send you a message saying "The player (player name) can not currently destroy your blocks."

/fly:
-To activate/deactivate the flight

Demonstration:


Consider the following:
-You can only destroy your blocks and the blocks of the player who gave you permission (/allow)
-You can not destroy blocks that are in other sectors (only administrators can do it)
-You can not claim more than 1 sector.
-When you choosing a sector, the area of ​​the sector will be painted with color of the block you are using.
-You have infinite cubes
-The weapons, grenades and spade do not cause damage.
-You can not kill.
-Grenades can not destroy blocks.

I modify some scripts a bit, so they can work with this script.
-The paint.py script was modify it so that you can only paint your blocks, you can not paint the blocks of other players or the blocks of the map. (use it plz)
-The sculpt.py script will only allow you to destroy the blocks of the map, yours and those of your sector, if a player gave you permission to destroy their blocks (/allow), you can also destroy their blocks with the sculpt.

Caution:
-I recommend that the commands: /box, /db, /df, /dw and /wall should only be used by the players that are trustworthy to you, this will avoid the misuse of commands.
-I will put the map I am using in the video (the map is great for a build server) along with the scripts + a config.txt that you can use it on your build server, you just have to change the passwords.

The commands /paint, /rapid /gr(gradient commands) and /sculpt can be used by any player.
 
Thanks.

8
the cute lil workshop / [SCRIPT] changevalue
« on: May 13, 2018, 10:34:57 AM HST »
This script will allow you to modify the damage of the weapons, both the damage it causes to the head, body and arms/legs.

Default damage of weapons:

1) rifle: head: 100 body: 49 arms/legs: 33
2) smg: head: 75 body: 29 arms/legs: 18
3) shotgun: head: 37 body: 27 arms/legs: 16

Commands:

/riflevalue <value head> <value body> <value arms/legs>
/smgvalue <value head> <value body> <value arms/legs>
/shotgunvalue <value head> <value body> <value arms/legs>
/debug

The commands /riflevalue, /smgvalue and /shotgunvalue will have 3 parameters, in <value head> you must put the damage you want the weapon to do in the head, in <value body> you must put the damage you  want the weapon to do in the body and in <value arms/legs> you must put the damage you want the weapon to do on arms/legs.

When you put the command without passing any parameters you will receive 2 messages saying that you must pass the values in the 3 parameters and the current damage that the weapon has,  for example in the rifle:

/riflevalue
You need to type /riflevalue <value head> <value body> <value arms/legs>
Current RIFLE damage: HEAD: 100 BODY: 49 ARMS/LEGS: 33



If you only want to change the damage of the head, you must only pass the damage in <value head>, the other parameters will automatically take the value that the weapon currently has.

/riflevalue 50
You changed the RIFLE damage by: HEAD: 50 BODY: 49 ARMS/LEGS: 33

in case you want to change only the damage of the body, in <value head> you should pass the value 0 and then put in <value body> the value you want, it will no longer be necessary to pass the value of <value arms/legs> since it will automatically take the value it currently has in arms/legs.

/riflevalue 0 20
You changed the RIFLE damage by: HEAD: 50 BODY: 20 ARMS/LEGS: 33

In case you want to just change the damage of <value arms/legs> you must pass both in <value head> and <value body> the value 0, and in <value arms/legs> you must pass the value you want to put.

/riflevalue 0 0 5
You changed the RIFLE damage by: HEAD: 50 BODY: 20 ARMS/LEGS: 5

(The 0 is used to tell the script "I'm not going to pass any value on you, so you'll take the damage that the weapon currently has.")

To change all the values ​​just put the damage in <value head> <value body> <value arms/legs>

/riflevalue 90 50 10
You changed the RIFLE damage by: HEAD: 90 BODY: 50 ARMS/LEGS: 10

The same is for /smgvalue and /shotgunvalue
If you want to reset the damage of the weapons to the default value, you should only put /debug command.

In this video you can see a small demonstration:



In the case of the shotgun, each shot have 8 bullets, therefore each of those 8 bullets will take the value you put, in the video in /shotgunvalue I put 1 in <head value> therefore 8 bullets in the head is equal to -8HP.


thanks.

9
the cute lil workshop / [SCRIPTl market
« on: May 06, 2018, 04:20:45 PM HST »
This script allows players to buy things for their own benefit.

Market contains:

1) medkit (1 medkit costs 3 dollars)
2) helmet (1 helmet costs 4 dollars)
3) shield (costs 12 dollars)
4) refill (costs 7 dollars)

To buy something from the market, you just have to put the command /get [object]. Example: /get medkit

Helmet: the helmet will protect you from a headshot and it will break, at the moment of breaking it will send you a message saying "Your helmet has been broken!, now you have (amount) helmet's." (you can buy more than 1)

Medkit: Restores your life to 100%, to use it you must type /m (you can buy more than 1)

Refill: Restores your hp, grenades, blocks and ammo at 100%.

Shield: Counts like a bulletproof vest, the damage of weapons will makes you less damage, when you buy 1 shield the durability of your bulletproof vest goes up to 200%, the bulletproof vest does not last forever, every shot you get in the body will lower the durability of your bulletproof vest, if the durability reaches 0% it will send you a message saying "Your shield has been broken!" and the damage of the weapons return to normal.

The maximum durability is 400%, be careful because this only protects your body, if someone shot you in the head the damage of the weapon returns to normal.
Your shield will continue to work until the durability reaches 0%.

Commands:
*/get [object]
*/mystuff
*/m

/m = if you have medkit's you can use this command.

/get [object] = if no object is passed, the script sends you a message saying the things available to buy.
If the object does't exist, the script send you a message saying "the [object]  was not found on the maket." + the things available to buy.
 
/mystuff = to see everything you have bought and currently have: amount of dollars, helmet's, medkit's and The durability of your bulletproof vest (shield).

To get dollars, you must kill 1 player, since 1 kill += 1 dollar.

Shield + helmet = OP
Thanks.

10
the cute lil workshop / [SCRIPT] detectip
« on: May 06, 2018, 01:16:32 PM HST »
I come to share another script that may be of help, the purpose of this script is to help detect evaders.
The script works with the "bans.txt" file that is inside the dist folder.

#Detects when an ip contains 3 octets equal to the banned ip (message = Ban Evader Detected)
#Detects when an ip contains 2 octets equal to the banned ip (message = Possible Ban Evader Detected)

IP's contain 4 pairs of numbers (octets) = a.b.c.d
example: 104.166.78.57 (104 is a, 166 is b, 78 is c, 57 is d).

suppose that a banned IP is 192.168.120.89 and the IP of the player who has just entered your server is 192.168.120.50 (here would be "Ban Evader Detected" since both IP's contain 3 equal octets 192.168.120).


Now let's suppose that another banned IP is 120.233.45.100 and the IP of the player that has just entered your server is 120.233.80.20 (here would be "Possible Ban Evader Detected" since both IP's contain 2 equal octets 120.233).

The script will alert you with a message in the IRC when it detects an evader, as well as sending a message to the administrators who are inside the server.

Example of a "Ban Evader Detected":



Example of a "Possible Ban Evader Detected":




Thanks.

Pages: [1] 2 3 4 5 6 7 8 9 10 11 ... 28