Leads, leashed mobs and leash knots on fences #3798

spekdrum · 2017-06-21T18:57:51Z

Adds leads handling, leashed mobs and leash knots on fences.
Drops appropriate pickup on unleash.
Save and load knots from map and re-leash mobs that were leashed before server close.
Knots sound.
Support from 1.8 to 1.12 protocol versions.

It's been a lot of work and testing but that was very enjoyable :P

Fixes #2915 and #2729

Tests done:

Create some leads ( /i lead 24 ). They are stack-able now, as in vanilla.
Go for passive mobs (pigs, cows, horses...) and right click them with a lead on main hand. They will be leashed to you.
Try on others than passive mobs (wont work).
Take more than one mob at a time. You are now Santa Claus.
Look them following you.
Try to go far from the mob (> 10 blocks). Leads should break with no drop.
Unleash a leashed mob right clicking on it, then used lead will become a pickup.
Kill the mob while it's leashed to you, leash link (the drawn rope between you and the mob) will go out and there will be no drop.
Catch a mob with a lead and then right click on a fence, a leash knot will show up. The leash sound should be heard. The mob will unleash from your player and get leashed to the knot.
Try to leash more mobs to the same fence block. No more knots will be created, the existing will be reused. No sound will be reproduced.
Try to leash more mobs to the knot (it's different to the server right clicking on a knot than right click on the fence sustaining the knot). It will work.
Try to break a knot, all mobs leashed will be released.
Try to break a fence where there is a knot. As in vanilla, the knot will break passed about a second, and mobs will be released.
Try to leash a mob that's currently leashed to a fence leash knot. No effect and no rope line drawing. That last has been tricky to fix, because client anticipates to server and draws the line of the leash between player and the mob without regard from the current state of the mob.
Try to put several leash knots on adjacent fence blocks, logout, close server, open server again, login. Every mob will be leashed to it's knot again.

Not implemented:

Leashed mobs in vanilla can go around up to 5 blocks distance from the knot. Know mobs just go to the target pos like in other situations.
Surely I forgot some LUA and doc stuff

madmaxoft

I think all mobs should be capable of being leashed, and each cMonster instance should have a flag saying whether that particular mob can be leashed - so that plugins may override it. Imagine a plugin for a tame creeper-on-a-leash :)

Also note that the PassiveMonster tick code has changed the assumptions somewhat - now the m_LoveTimer etc. can reach negative values, unlike in previous versions. This will most likely not matter if you move the logic out to cMonster, though.

Upon inspecting the ticking code, I think it will be prone to failures across chunk borders - when the entity is loaded and the knot is in a neighboring unloaded chunk. That would mean lost leashings (I have a feeling this happened in Vanilla, too), possibly even crashes.

Why is there even a timeout between destroying a fence and destroying the knot? Why not break the knot immediately? Makes much more sense.

Style issues:

multi-line if statements should have each condition on a separate line (including the first one) and the boolean operator at the end of the line:

if (
  (a == b) &&   // Possible comment on the reasons for this check
  !IsTicking()  // Why this condition?
)
{
  // ...
}

Member variables that store bools should be named with a yes/no verb in front: m_IsLeashed..., m_ShouldCheck... etc. (cLeashKnot::m_SelfDestroy)

spekdrum · 2017-06-23T18:27:07Z

Agree with upgrading to cMonster, this will also make cleaner code.
I will think on a solution for the chunks problem, first I will try to reproduce it.

The delay for the knot is as in vanilla. I thought they did it this way to point out to the player he ruined a knot breaking the fence or whatever. But maybe vanilla behaves this way for some limitation that cuberite dont suffer :p

Im on holidays now, will put hands on this in a week or so. Happy coding ;)

spekdrum · 2017-06-28T17:51:04Z

I'm working on the possibility to leash any monster and I found a problem. With any aggressive monster (tried creeper and skeleton) the client sends the right click event twice, when you just right click once on it. The result is that the monster gets leashed but immediately unleashed.
Should I have to use a variable to store last leash action tick count in order to avoid this? So ugly...

Seadragon91 · 2017-06-28T18:07:08Z

Ah that problem. Had also been reported in this issue with sitting a wolf: #3186

Not sure whats going on there...

spekdrum · 2017-06-28T18:16:33Z

Looking at the call stack, having put a breakpoint in cClientHandle::HandleUseEntity it seems that is the client that sends the packet twice...

spekdrum · 2017-06-28T19:06:39Z

I found an interesting point with the double right click problem.
This is the code that gets executed twice:

void cProtocol_1_9_0::HandlePacketUseEntity(cByteBuffer & a_ByteBuffer)
{
	HANDLE_READ(a_ByteBuffer, ReadVarInt, UInt32, EntityID);
	HANDLE_READ(a_ByteBuffer, ReadVarInt, UInt32, Type);

	switch (Type)
	{
		case 0:
		{
			HANDLE_READ(a_ByteBuffer, ReadVarInt, UInt32, Hand)
			m_Client->HandleUseEntity(EntityID, false);
			break;
		}

The "Hand" variable first time is 0 and second time is 1. According to the protocol doc (http://wiki.vg/Protocol#Use_Entity) that means main hand (0) or off-hand (1). Maybe we should check which hand holds the item we want to use with the entity, but we need to change the code a bit in order to let this parameter arrive to every place. I suggest to initially ignore calls for the off-hand and implement off-hand actions later. It's indeed a very easy fix. This way we can get rid of those double action related issues till a complete solution is done.

Edit: I've just make a PR for a fix.

spekdrum · 2017-06-28T22:59:55Z

@madmaxoft As suggested I moved the logic to cMonster with a flag.
I've been doing some tests regarding the chunk borders potencial problem. I reproduced the problem, no crash happened, just mobs became unleashed and knot was still there (with no mob leashed). To fix that, I removed the line that sets m_LeashToPos to nullptr. This way the mob keeps trying till the knot is found. I introduced a stepped Tick there to avoid unnecessary calcs.

The delay for the knot destroy upon fence wipe is still there, because vanilla does this way. I like to remark the player the knot is gone. If you insist I have no problem to remove it, but please consider my argument :)

spekdrum · 2017-06-29T09:53:49Z

I added an overload for cBoundingBox in order to get horizontal and vertical radius

Seadragon91 · 2017-07-01T11:36:23Z

Does this work with monsters like creeper now?

spekdrum · 2017-07-01T12:28:20Z

Only if you override m_CanBeLeashed flag. By default only passive monsters have this flag on.
You can see it in cMonster constructor.

…l it finds knot on chunk load.

spekdrum · 2017-07-02T10:52:29Z

I fixed a possible leash lose when a mob is looking for it's knot and server gets closed. Also stopped mobs when they are leashed to a knot that has not been found yet.

spekdrum · 2017-07-02T11:13:41Z

Added speeding up mobs getting far from player when leashed to a player as Vanilla does.

Code was rewritten

madmaxoft · 2017-07-03T09:05:40Z

src/BoundingBox.h

@@ -27,6 +27,7 @@ class cBoundingBox
 	cBoundingBox(double a_MinX, double a_MaxX, double a_MinY, double a_MaxY, double a_MinZ, double a_MaxZ);
 	cBoundingBox(const Vector3d & a_Min, const Vector3d & a_Max);
 	cBoundingBox(const Vector3d & a_Pos, double a_Radius, double a_Height);
+	cBoundingBox(const Vector3d & a_Pos, double a_Radius, double a_Height, double a_VerticalOffset);


This deserves a doxy-comment.

madmaxoft · 2017-07-03T09:06:50Z

src/ClientHandle.cpp

@@ -1704,6 +1704,7 @@ void cClientHandle::HandleUpdateSign(
 void cClientHandle::HandleUseEntity(UInt32 a_TargetEntityID, bool a_IsLeftClick)
 {
 	// TODO: Let plugins interfere via a hook
+	LOGD("Use entity %d", a_TargetEntityID);


This should probably be deleted.

madmaxoft · 2017-07-03T09:08:24Z

src/Entities/LeashKnot.cpp

+	else
+	{
+		// Detect if fence is destroyed. Get block at knot position and check if its solid
+		BLOCKTYPE BlockID = m_World->GetBlock(static_cast<int>(GetPosX()), static_cast<int>(GetPosY()), static_cast<int>(GetPosZ()));


Use FloorC instead of the casts.

madmaxoft · 2017-07-03T09:10:58Z

src/Mobs/Horse.cpp

@@ -131,24 +131,28 @@ void cHorse::OnRightClicked(cPlayer & a_Player)
 	}
 	else if (a_Player.GetEquippedItem().IsEmpty())
 	{
-		if (m_Attachee != nullptr)
+		// Check if leashed / unleashed to player before try to ride
+		if (!m_IsLeadActionJustDone)


Lead or Leash?

madmaxoft · 2017-07-03T09:11:16Z

src/Mobs/Monster.cpp

@@ -582,6 +685,27 @@ void cMonster::OnRightClicked(cPlayer & a_Player)
 			a_Player.GetInventory().RemoveOneEquippedItem();
 		}
 	}
+
+	// Using leads
+	m_IsLeadActionJustDone = false;


madmaxoft · 2017-07-03T09:13:19Z

src/Protocol/Protocol_1_12.cpp

+void cProtocol_1_12::SendLeashEntity(const cEntity & a_Entity, const cEntity & a_EntityLeashedTo)
+{
+	ASSERT(m_State == 3);  // In game mode?
+	cPacketizer Pkt(*this, 0x3C);  // Set Attach Entity packet


Prefer lowercase hex digits

madmaxoft · 2017-07-03T09:13:59Z

src/Protocol/Protocol_1_8.h

@@ -90,6 +90,7 @@ class cProtocol_1_8_0 :
 	virtual void SendHideTitle                  (void) override;
 	virtual void SendInventorySlot              (char a_WindowID, short a_SlotNum, const cItem & a_Item) override;
 	virtual void SendKeepAlive                  (UInt32 a_PingID) override;
+	virtual void SendLeashEntity               (const cEntity & a_Entity, const cEntity & a_EntityLeashedTo) override;


Wrong alignment, one more space

madmaxoft · 2017-07-03T09:14:10Z

src/Protocol/Protocol_1_9.cpp

+void cProtocol_1_9_0::SendLeashEntity(const cEntity & a_Entity, const cEntity & a_EntityLeashedTo)
+{
+	ASSERT(m_State == 3);  // In game mode?
+	cPacketizer Pkt(*this, 0x3A);  // Set Attach Entity packet


lowercase hex

madmaxoft · 2017-07-03T09:14:17Z

src/Protocol/Protocol_1_9.cpp

+void cProtocol_1_9_0::SendUnleashEntity(const cEntity & a_Entity)
+{
+	ASSERT(m_State == 3);  // In game mode?
+	cPacketizer Pkt(*this, 0x3A);  // Set Attach Entity packet


lowercase hex

madmaxoft · 2017-07-03T09:15:11Z

src/WorldStorage/NBTChunkSerializer.cpp

+			{
+				LeashedToPos = a_Monster->GetLeashToPos();
+			}
+			else if (a_Monster->GetLeashedTo()->IsLeashKnot())


Could both LeashedToPos and LeashedTo be nullptr?

No, because the outer if ensures that one of them (at least) is not null.
a_Monster->IsLeashed() it's the same as a_Monster->GetLeashedTo() != nullptr

madmaxoft · 2017-07-03T09:17:13Z

This is definitely on the right way, just a few cosmetics now :)

spekdrum · 2017-07-04T17:12:19Z

Should I mark dirty a chunk when a player places a leash knot on a fence?

Seadragon91 · 2017-07-05T08:21:57Z

Is a new entity created? If yes then it should be marked dirty

spekdrum · 2017-07-05T15:21:44Z

Ok, do not merge please, I'm going to mark them all dirty :P

spekdrum · 2017-07-05T16:46:39Z

I checked the code and there is no further change needed. MarkDirty() is already called later, once the entity is initialized and added to vector m_EntitiesToAdd from World. Same happens when destroyed. Everything happens in cWorld::Tick.

So, for me this is done!

madmaxoft · 2017-07-06T22:28:04Z

src/Blocks/BlockFence.h

+	virtual bool OnUse(cChunkInterface & a_ChunkInterface, cWorldInterface & a_WorldInterface, cPlayer * a_Player, int a_BlockX, int a_BlockY, int a_BlockZ, eBlockFace a_BlockFace, int a_CursorX, int a_CursorY, int a_CursorZ) override
+	{
+		// this vector allows to store the reference to an existing knot, if found inside the callback function
+		std::vector<cLeashKnot *> LeashKnotList;


Why a vector? A simple pointer should suffice for this.

madmaxoft · 2017-07-06T22:32:40Z

src/Entities/LeashKnot.cpp

+{
+	super::OnRightClicked(a_Player);
+
+	// Check leashed nearby mobs to tight them to this knot


tight -> tie

madmaxoft · 2017-07-06T22:35:04Z

src/Entities/LeashKnot.cpp

+			return false;
+		}
+	} Callback(this, &a_Player);
+	a_Player.GetWorld()->ForEachEntityInBox(cBoundingBox(GetPosition(), 8, 8, -4), Callback);


This big callback code seems repeated in cBlockFenceHandler::OnUse. Could it be moved into a method of its own (TieHandLeashedMobs (?)) and shared?

madmaxoft · 2017-07-06T22:38:04Z

src/Entities/LeashKnot.cpp

+		if (!cBlockInfo::IsSolid(BlockID))
+		{
+			m_ShouldSelfDestroy = true;
+		}


Does this need to happen here? Couldn't the fence being broken signalize that the knot should be destroyed?

madmaxoft · 2017-07-06T22:40:28Z

src/Mobs/Monster.cpp

+		// TODO: leashed mobs in vanilla can move around up to 5 blocks distance from leash origin
+		MoveToPosition(m_LeashedTo->GetPosition());
+
+		// If distance to target > 10 break lead


lead -> leash

madmaxoft · 2017-07-06T22:40:44Z

src/Mobs/Monster.cpp

@@ -582,6 +685,27 @@ void cMonster::OnRightClicked(cPlayer & a_Player)
 			a_Player.GetInventory().RemoveOneEquippedItem();
 		}
 	}
+
+	// Using leads


madmaxoft · 2017-07-06T22:43:02Z

src/Entities/Entity.cpp

+
+
+
+void cEntity::RemoveLeashedMob(cMonster * a_Monster, bool a_DropPickup, bool broadcast)


Style: a_ShouldBroadcast

madmaxoft · 2017-07-06T22:43:57Z

src/Entities/Entity.cpp

@@ -2247,3 +2264,38 @@ void cEntity::SetPosition(const Vector3d & a_Position)



+
+void cEntity::AddLeashedMob(cMonster * a_Monster, bool broadcast)


Style: a_ShouldBroadcast

madmaxoft · 2017-07-06T22:46:32Z

src/WorldStorage/WSSAnvil.cpp

+	// Leashed to a knot
+	bool Leashed;
+	int LeashedIdx = a_NBT.FindChildByName(a_TagIdx, "Leashed");
+	if (LeashedIdx >= 0)


Use an early bailout (negate the condition, return) to avoid unnecessary indent levels.

Perhaps even move this into a separate function, since LoadMonsterBase is already pretty long by itself.

spekdrum · 2017-08-05T21:43:17Z

Done

madmaxoft · 2017-08-07T08:24:00Z

src/Entities/Entity.cpp

+	{
+		LeashedMob->Unleash(true, true, false);
+	}
+	m_LeashedMobs.clear();


Can you try if this works? Removing the need for Unleash's last parameter.

while (!m_LeashedMobs.empty()) { m_LeashedMobs.front()->Unleash(true, true); }

Like, much better

madmaxoft · 2017-08-07T08:33:36Z

src/Entities/LeashKnot.cpp

+
+cLeashKnot * cLeashKnot::FindKnotAtPos(cWorldInterface & a_WorldInterface, Vector3i a_BlockPos)
+{
+	cLeashKnot * LeashKnot = nullptr;


Remove this variable, make LookForKnot::m_LeashKnot a simple pointer and do return CallbackFindKnot.m_LeashKnot in the end.

madmaxoft · 2017-08-07T08:36:55Z

src/Mobs/Monster.cpp

+void cMonster::CalcLeashActions()
+{
+	// This mob just spotted in the world and [m_LeashToPos not null] shows that should be leashed to a leash knot at m_LeashToPos.
+	// This keeps trying until knot is found


Add a note that the leash knot may be in a different chunk that needn't be loaded, to make it clear why this can happen.

madmaxoft · 2017-08-07T08:39:31Z

src/Mobs/Monster.cpp

+		// Mob is already leashed but client anticipates the server action and draws a leash link, so we need to send current leash to cancel it
+		m_World->BroadcastLeashEntity(*this, *this->GetLeashedTo());
+	}
+	else if (CanBeLeashed() && (EquippedItem.m_ItemType == E_ITEM_LEAD))


How about adding E_ITEM_LEASH equivalent to the lead, but better named, and using that everywhere in code instead?

madmaxoft · 2017-08-07T08:41:00Z

src/Mobs/Monster.cpp

+
+void cMonster::LeashTo(cEntity * a_Entity, bool a_ShouldBroadcast)
+{
+	m_LeashedTo = a_Entity;


You should probably add ASSERT(m_LeashedTo == nullptr), so that when broken code in the future tries to call this while already leashed, the error is detected early and precisely.

Oh wait, is this the directly exported Lua API? Plugins are bound to call this while already leashed, because we plugin authors are stupid and too lazy to read docs. So make the function behave well in such a case - ideally re-leash the mob to the new entity, or if not practically possible, don't change the leash-ness.

Similar with Unleash being called while not leashed.

You mean check if already leashed and if so then do nothing, (and viceversa) right?

spekdrum · 2017-08-07T12:32:21Z

That's kinda poetic man, you are leashing me to this xD

Bond-009 · 2017-08-08T17:25:53Z

src/BlockID.h

@@ -459,6 +459,7 @@ enum ENUM_ITEM_ID : short
 	E_ITEM_GOLD_HORSE_ARMOR = 418,
 	E_ITEM_DIAMOND_HORSE_ARMOR = 419,
 	E_ITEM_LEAD = 420,
+	E_ITEM_LEASH = E_ITEM_LEAD,


But, ... Why?

'cause I said so. Leash is a much better name than lead, because it's unambiguous. Lead can be also a metal, or a verb.

Then why not only use Leash?

Because the vanilla item is named minecraft:lead?

Cause he/she said so 😄
Not a very important thing to argue about, others did it before 😛
https://english.stackexchange.com/questions/273617/difference-between-lead-and-leash

spekdrum · 2017-08-08T17:34:22Z

Done.
For LeashTo / Unleash I've just add code to check if already / not leashed and do nothing if so.

madmaxoft · 2017-08-09T06:41:58Z

Yayyy, approved :)

spekdrum · 2017-08-09T07:29:38Z

madmaxoft · 2017-08-09T12:40:08Z

spekdrum · 2017-08-09T13:17:39Z

LOL a leashed cat!

madmaxoft · 2017-08-17T13:49:40Z

I'm afraid the recent merge of int-to-vector change in cBoundingBox has produced some merge conflicts (sorry). Can you fix those please?

spekdrum · 2017-08-17T14:22:20Z

Sure

# Conflicts: # src/BoundingBox.cpp # src/BoundingBox.h

spekdrum · 2017-08-20T17:27:20Z

I hope I did it well. I also had to change a bit of code affected by the entity ownership changes.

madmaxoft · 2017-08-21T08:47:16Z

🎉

madmaxoft previously requested changes Jun 23, 2017

View reviewed changes

Reworked leashes and moved to cMonster

62bfbfb

spekdrum force-pushed the leads-wip branch from 7d6f70a to 62bfbfb Compare June 28, 2017 22:47

spekdrum added 2 commits June 29, 2017 01:01

LeashPos reset and style fix

3a4b545

Fix leashing mobs to fences when they are above the mob

da87f05

spekdrum mentioned this pull request Jul 1, 2017

You can't use beds when there are hostile mobs nearby #3828

Merged

Improved leashed monsters serialization and stop leashed monster unti…

e47b5a1

…l it finds knot on chunk load.

Speed up leashed mobs getting far from player (as in vanilla)

647bfd7

Merge branch 'master' into leads-wip

ee4e691

madmaxoft requested changes Jul 3, 2017

View reviewed changes

spekdrum added 2 commits July 4, 2017 18:18

Style fixes

806c604

Tab removed

085361d

madmaxoft requested changes Jul 6, 2017

View reviewed changes

spekdrum added 5 commits August 5, 2017 21:24

Merge and refactor

e3dfc77

Merge and refactor

2ddcb48

Function override fix

920e410

Remove unneeded code

7b58921

Merge remote-tracking branch 'upstream/master' into leads-wip

be465c8

Change definitions order

79af20c

madmaxoft requested changes Aug 7, 2017

View reviewed changes

spekdrum added 3 commits August 8, 2017 19:15

Code improvements

d5c7196

Add myself to CONTRIBUTORS

ea88e17

Merge remote-tracking branch 'upstream/master' into leads-wip

909d4f5

Bond-009 reviewed Aug 8, 2017

View reviewed changes

Desc for ITEM_LEASH in APIDesc.lua

ed3e2a0

madmaxoft approved these changes Aug 9, 2017

View reviewed changes

Merge remote-tracking branch 'upstream/master' into leads-wip

48041ee

# Conflicts: # src/BoundingBox.cpp # src/BoundingBox.h

madmaxoft merged commit b18f663 into master Aug 21, 2017

This was referenced Aug 21, 2017

Animals don't follow you using leads #2729

Closed

Fixed build for older clang versions #3935

Merged

bearbin deleted the leads-wip branch August 21, 2017 09:47

Seadragon91 mentioned this pull request Sep 29, 2019

Added another check if the item is place able #4404

Merged




		void cEntity::RemoveLeashedMob(cMonster * a_Monster, bool a_DropPickup, bool broadcast)

		@@ -2247,3 +2264,38 @@ void cEntity::SetPosition(const Vector3d & a_Position)




		void cEntity::AddLeashedMob(cMonster * a_Monster, bool broadcast)

Leads, leashed mobs and leash knots on fences #3798

Leads, leashed mobs and leash knots on fences #3798

Conversation

spekdrum commented Jun 21, 2017 • edited

madmaxoft left a comment

Choose a reason for hiding this comment

spekdrum commented Jun 23, 2017

spekdrum commented Jun 28, 2017

Seadragon91 commented Jun 28, 2017 • edited

spekdrum commented Jun 28, 2017

spekdrum commented Jun 28, 2017 • edited

spekdrum commented Jun 28, 2017

spekdrum commented Jun 29, 2017

Seadragon91 commented Jul 1, 2017 • edited

spekdrum commented Jul 1, 2017

spekdrum commented Jul 2, 2017

spekdrum commented Jul 2, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

spekdrum Jul 4, 2017 • edited

Choose a reason for hiding this comment

madmaxoft commented Jul 3, 2017

spekdrum commented Jul 4, 2017

Seadragon91 commented Jul 5, 2017 • edited

spekdrum commented Jul 5, 2017

spekdrum commented Jul 5, 2017 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

spekdrum commented Aug 5, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

spekdrum commented Aug 7, 2017

Bond-009 Aug 8, 2017 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

spekdrum Aug 9, 2017 • edited

Choose a reason for hiding this comment

spekdrum commented Aug 8, 2017

madmaxoft commented Aug 9, 2017

spekdrum commented Aug 9, 2017

madmaxoft commented Aug 9, 2017

spekdrum commented Aug 9, 2017

madmaxoft commented Aug 17, 2017 • edited

spekdrum commented Aug 17, 2017

spekdrum commented Aug 20, 2017

madmaxoft commented Aug 21, 2017

spekdrum commented Jun 21, 2017 •

edited

Seadragon91 commented Jun 28, 2017 •

edited

spekdrum commented Jun 28, 2017 •

edited

Seadragon91 commented Jul 1, 2017 •

edited

spekdrum Jul 4, 2017 •

edited

Seadragon91 commented Jul 5, 2017 •

edited

spekdrum commented Jul 5, 2017 •

edited

Bond-009 Aug 8, 2017 •

edited

spekdrum Aug 9, 2017 •

edited

madmaxoft commented Aug 17, 2017 •

edited