Special thanks to United for stealing my job and answering questions about PMC. :p (I'm serious, thanks. :) )

If this is the case, there is basically no other possibility than a problem with the setup of the core module United mentioned. Even if the toolswitcher was broken, the core module would prevent the message from sending.

Is there anything that was previously bound to the onSendChatMessage event? If there is, try placing the PMC core binding to the first position (e.g. $$<PMC_Core.txt>|$$<OtherMacro.txt> ), but that can prevent the second macro from executing.

 

I don't understand how a balance show macro would work... are you typing something to update your balance display? Normally a balance macro should be placed in onChat to update, I have no idea why yours should belong to onSendChatMessage.

I am asking because I have yet to find a way that would not break everything. .-.

 

Alright, the problem has been cleared up ingame. I modified the wiki instructions by adding the last sentence.


A major shoutout for PMC's new top supporter, @alpert3925, with the astonishing amount of 10,000 ECD - major thanks! :happy:


Also, I am still searching for good feature requests that could be added into PMC. If you have an idea for something, use the format from the main post. ;)

 

~Status: Updated.



If you wish to use this new functionality, please download the new version from https://github.com/ECC314/PMC/archive/master.zip.
This module is already available without the need to bind any scrpits to events except for the core macro.

If you notice a very long silence between different pieces of music, please tell me which one you were listening to. I used the time stated on the Minecraft wiki, but there might be a mistake that wasn't found during my testing period.

 

Please refer to the optional instruction located on the join module wiki page. The textarea shows all players that join, but highlights special groups with colours.

I might add the option to log it into chat as well, but I don't really like that idea because it becomes very spammy very fast.

 

Put on hold until 1.9 macros (hopefully) appear. .-.

 

This version isn't even working for me. .-.
I will require more testing; most of it will probably happen in 10 days.

 

I actually created this update after the 1.9 server update and mainly tested it for the short time between 1.9 macros and 1.9.4 ECC. If anything is broken, please tell me.

Why is this mainly a performance update?
I decided to rewrite some parts of code that were rather inefficient. The ToolSwitch module, for example, defined variables many times per second. The main performance problem, however, was located within the Statistics module.

Those who were curious and used .help stats in a few specific versions noticed that .stats chat existed; I actually added the command itself a little earlier. It was originally supposed to be a test, but I have decided to remove it. Why?

PMC itself includes around 1000 lines of macro code. I removed roughly 200 lines of code by erasing this command that was never of any real use. Those 200 lines weren't even the largest problem - an estimated 100 lines of code were executed whenever you picked up an item or when a new line of chat appeared. Every. Single. Time. I have tested it during 1.9 when ECC's chat was rather active; it appears to cause a perceivable difference.

For those who normally modify PMC code to suit their needs: I have improved the code readability by creating more local &prefix variables instead of using annoyingly long strings of letters, brackets and colour codes.

Important:
If you wish to use the new version of PMC - or any future versions - you will need to take a look at https://github.com/ECC314/PMC/wiki/Setup because I have added a new file, PMC_Init.txt, to solve the ToolSwitcher problem I mentioned above (and a few other problems that are based on the very same principle).​

TL;DR: Bind $$<PMC_Init.txt> to onJoinGame and everything should work again.