azb
Level: Disabled
Rank Points: 502
Registered: 03-08-2014
IP: Logged

File: Bug Test.hold (1.1 KB)
Downloaded 58 times.
License: Public Domain

Hello, in the hold I was working on, "The Final Reckoning", I made a Guard with the name "Pirate Captain". When the player plays as him, his temporal clones inexplicably lose their sword, even though I explicitly stated to "set player weapon Sword". Even without the command and just leaving it as "set player role Pirate Captain", his clones are still unarmed.

The version I used to upload the example is version 5.1.0.6501.

Insoluble
Level: Smitemaster

Rank Points: 1639
Registered: 09-04-2014
IP: Logged

I encountered this bug too and posted about it a while back:

Insoluble wrote:
I have no real opinion on the above mentioned bug, but wanted to mention a possibly related bug that I've encountered. This occurs if you create a custom player role that is based on an element that has a weapon (I did this with a custom character based on Beethro at first, but tested it with guards and slayers as well. Same bug). When you set the player role to your custom character then record a temporal projection, the projection will play back disarmed for no apparent reason. This occurs even if you swap weapons using a token or set the payer's weapon using set player weapon. See the attached hold for an example.

I wish I could offer some sort of help but I was never able to find a workaround and ended up just having to revert to a standard player role for the one room with a time token in it.

____________________________
Links to neat forum tools that I always have trouble finding:

mrimer
Level: Legendary Smitemaster

Rank Points: 5199
Registered: 02-04-2003
IP: Logged

hyperme has fixed this issue cleanly for 5.1.1.

____________________________
Gandalf? Yes... That's what they used to call me.
Gandalf the Grey. That was my name.
I am Gandalf the White.
And I come back to you now at the turn of the tide.

NiroZ
Level: Smitemaster
Rank Points: 1302
Registered: 02-12-2006
IP: Logged

I've checked and this is fixed in 5.1.1.alpha.2020-09-24 build in windows 10.