• If you have a mod, tool or prefab, please use the Resources section. Click Mods at the top of the forums.

[MOD] Coppis Additions (NEW)

Yeps. And you only had to answer my question (twice in thread post and once by PM) about changing the one (!) conflicting command i used and i would have changed it within the blink of an eye. But there was only silence even after you posted about the "blinking mess" when you use one of coppis commands in a way its not supposed to be used after that post. I have never had any problems receiving or sending PMs on this forum so forgive me if i find it hard to believe you actually replied. I never got a response so dont blame me for thinking i was being ignored while willing to help resolving any conflicts.

Anyways. This is turning into a he said <-> he said convo and all my chatcommands have been ported over. So i will ask you one last time, if you want me to change the /who chatocmmand to someting else i will. I have no intention of taking over anyone else's functionality. Do you want me to change it? Just say yes and i will have it released in next version.

Cheers

 
Yes please change it. If you don't I will have to add Coppi's mod to the list of mods that I work around due to a command clash. That would negatively affect around 200 servers. I have been using /who and /protect for 3 years and those commands are used a lot, especially /protect.

I also have /who visited

 
Last edited by a moderator:
Yes please change it. If you don't I will have to add Coppi's mod to the list of mods that I work around due to a command clash. That would negatively affect around 200 servers. I have been using /who and /protect for 3 years and those commands are used a lot, especially /protect.
Considder it done.

Cheers

 
its done. I made /who a reserved command for servermanagers so it cant be set as command in Coppis.

Code:
private void SetCommand (List<string> _params)
       {
           string command = string.Empty;

           if (string.IsNullOrEmpty(_params[1].ToLower().Trim()))
               SdtdConsole.Instance.Output(string.Format("The parameter for command is not valid.", _params[1]));
           else
           {
               if (_params[1].ToLower().Trim().Equals("/who"))
               {
                   SdtdConsole.Instance.Output("Sorry, but /who is reserved for servermanager usage, defaulting to /loctrack");
                   command = "/loctrack";
               }
               else
                   command = _params[1].ToLower().Trim();

               PersistentContainer.Instance.LocationTracking.Command = command;
               PersistentContainer.Instance.Save();
               SdtdConsole.Instance.Output(string.Format("Command has been set to {0}", command));
           }
       }
will release tomorrow, since mh alcohol level does say "dont do it now man!" :p

Cheers

 
Another Idea I had, if possible, was a way to make a custom message with a countdown timer that would come across as the server. Like say for events on servers that offers them.. maybe something like: countdowntimer {message} in {time} {interval of notification}

 
Prisma, any chance to get an editable xml for all the messages like bloodmoon announcement, /who response's...?

It is really great but i hate the color ^^

or merge that project with ServerTools *.*!

 
Last edited by a moderator:
Another Idea I had, if possible, was a way to make a custom message with a countdown timer that would come across as the server. Like say for events on servers that offers them.. maybe something like: countdowntimer {message} in {time} {interval of notification}
Sure, will put that on my list. I ll even add in a parameter for manipulating the name which says it :D

Cheers

 
I noticed this, and coppi's before it, has a weird... issue with pblock. It always adds 1. Try pblock steelblock 10 0 10 0 for example, it creates an 11x11 platform. It also happens with the more advanced x1 x2, y1 y2, z1 z2, r command. pblock steelblock 1000 1010 50 50 1000 1010 0 also creates an 11x11 platform. Facing north by default, it only happens to the east and north sides. pblock steelblock 1000 1009 50 50 1000 1009 0 results in a 10x10, as does pblock steelblock 9 0 9 0.

 
Prisma, any chance to get an editable xml for all the messages like bloodmoon announcement, /who response's...?It is really great but i hate the color ^^

or merge that project with ServerTools *.*!
Lol, i was just saying the other day in modders discord that i want to keep Coppis xml free as long as i can hold it up :D . There are not many responses that would need manipulating so ill make them settings in the corresponding commands. That way you will have control on color used.

Cheers

- - - Updated - - -

I noticed this, and coppi's before it, has a weird... issue with pblock. It always adds 1. Try pblock steelblock 10 0 10 0 for example, it creates an 11x11 platform. It also happens with the more advanced x1 x2, y1 y2, z1 z2, r command. pblock steelblock 1000 1010 50 50 1000 1010 0 also creates an 11x11 platform. Facing north by default, it only happens to the east and north sides. pblock steelblock 1000 1009 50 50 1000 1009 0 results in a 10x10, as does pblock steelblock 9 0 9 0.
Will check that and see if i can fix! Thanks for reporting mate.

Cheers

 
Last edited by a moderator:
Update 4.3!

Update time!

Version 4.3 (2018.02.26)

Fixed:

- bug in pblock: creating platforms/structures with specific coords or quantities making x and z length 1 to long

Changed:

- default chatcommand for location tracker to /loctrack (was /who). It can still be set to anything you like.

Added:

- configurable response color for location tracker chatcommand ("loctrack responsecolor <hexString>")

- configurable text (with (nested) colorcode support) for NightTime Announcer

  • an announcer <name>
  • an nighttimetext <string>
  • an blooddaytext <string>
  • an blooddaytomorrowtext <string>
  • an counterdaytext <string>

- configurable warning hours for NightTime Announcer ("an warnhours <hours>")

New adjustable settings in bold:

Code:
an
AnnounceNightTime Enabled: True
Bloodmoon cycle: 7 days
[b]Warn 2 hours before 22:00
Announcer name: [b43104]{Server-Auto}[-]
NightTime text: [00ff00]Nighttime in {hours} hours !!![-]
BloodDay text: [00ff00]Better hurry! Its bloodmoon [FF0000]TONIGHT[-] !!![-]
BloodDay Tomorrow text: [00ff00]Remember: Bloodmoon is tomorrow !!![-]
CounterDay text: [00ff00]Remember: Bloodmoon is in {daysleft} days !!![-][/b]
Code:
loctrack
Active location tracker settings:
Enabled: True
Command: /loctrack
CommandEnabled: True
Interval: 15 seconds
MaxAgeData: 72 hours
NearDistance: 200 meters
[b]ResponseColor: 4DA6FF[/b]
For convenience: this is the site i always use for picking my color codes https://html-color-codes.info/

Code:
Usage:
 1. an true/false
 2. an hordecycle <days>
 3. an warnhours <hours>
 4. an announcer <name>
 5. an nighttimetext <string>
 6. an blooddaytext <string>
 7. an blooddaytomorrowtext <string>
 8. an counterdaytext <string>
 9. an
1. Turn AnnounceNightTime ON (true)/OFF(false)
2. Configure the bloodmoon cycle in <days>
3. Set the number of <hours> before 22:00 warning
4. Set the name of the announcer
5. Set the text for nighttime warning. {hours} will be replaced by the warnhours setting
6. Set the text for announcing bloodmoon is tonight
7. Set the text for announcing bloodmoon is tomorrow
8. Set the text for normal bloodmoon counter text. {daysleft} will be replaced by remaining days
9. List active AnnounceNightTime settings
All text and announcer name support (nested) color coding. The value of <string> has to be wrapped in "double quotes".
Put text between [colorCode]text here[-] for giving it a color.
Code:
Usage:
 1. loctrack search <steam id/player name/entity id> <radius> <numberOfHours>
 2. loctrack search <x> <y> <z> <radius> <numberOfHours>
 3. loctrack showtrack <steam id> <maxrecords> <timespan> <timeBetweenRecords>
 4. loctrack enabled <true/false>
 5. loctrack command <newChatCommand>
 6. loctrack commandenabled <true/false>
 7. loctrack interval <seconds>
 8. loctrack maxagedata <hours>
 9. loctrack neardistance <meters>
10. loctrack responsecolor <hexstring>
11. loctrack
1. list players within <radius> of <steam id/player name/entity id> last <numberOfHours>
2. list players within <radius> of <x> <y> <z> last <numberOfHours> (use y=-1 to ommit y search)
3. show location tracks of <steam id>. Maximum records <maxrecords>.
  Minimum time between records <timeBetweenRecords> (seconds). Within <timespan> (MMddHHmm-MMddHHmm).
4. Enable / Disable location recording
5. Define the ingame chatcommand (include the prefix)
6. Enable/Disable ingame chatcommand for querying databases
7. Set the interval of recording locations (seconds)
8. Set the maximum time the data stays in databases (hours)(0=forever)
9. Set the distance for use with chatcommand for reporting near live players
10. Set the responsecolor for use with chatcommand. Has to be 6 long hexadecimal number
11. Show all active location tracking settings
Enjoy!

Cheers

 
Last edited by a moderator:
I think waypoint commands might be messed up.
Thats a lot of info to go on. ;)

What seems to be the problem?

Cheers

-edit- i had existing waypoints and they got automigrated to the new persistent bin structure. They do still work fine. They do not list? You cant fly to them or move players to them?

 
Last edited by a moderator:
Lol sorry, I updated to scripts and now I cant /ft player, /ftw wp, or /setwp name
The /ft is a simple teleport netpackage which is not related to waypoints at all. It doesnt even use any persistent data except allocs for quering partial playernames. You are sure you did update correctly? Do you get an error in chat? Any other chatcommands not working. Like /hostiles or /bubble?

-edit- when you do "loctrack" in console, do you see a value behind ResponseColor: ?

Cheers

 
Last edited by a moderator:
The /ft is a simple teleport netpackage which is not related to waypoints at all. It doesnt even use any persistent data except allocs for quering partial playernames. You are sure you did update correctly? Do you get an error in chat? Any other chatcommands not working. Like /hostiles or /bubble?
-edit- when you do "loctrack" in console, do you see a value behind ResponseColor: ?

Cheers
Yes, /hostiles works, /bubble works and I do see the response color 4DA6FF

- - - Updated - - -

Version is showing 4.3

 
no response, just shows text publicly
aight then i think it fails to get the chatcommand for location tracker. And get exception internally. /hostiles and /bubble are prior to the loctrack chatcommand. The rest is after.

Few things to check if im right:

Does /acf behave the same?

Could you post the output of consolecommand "loctrack"?

Cheers

 
/acf has no response either

> loctrack

Active location tracker settings:

Enabled: False

Command:

CommandEnabled: False

Interval: 0 seconds

MaxeAgeData: 0 hours

NearDistance: 0 meters

ResponseColor: 4DA6FF

 
Back
Top