Yep, but second time around I would not care.

IDevAffiliate, how I understand it works as follows for recurring payments:

1. User pays the amount. vbulletin IPN script with curl sends amount, transactionId, IP address, affiliateId to idevaffiliate. Idev affiliate records IP address and affiliateId to record commissions.

2. On next recurring payment, IPN script with curl sends amount, transactionId, IP address retrieved from db to match last one, affiliateId to idevaffiliate. Idev affiliate again records commission for same affiliate.

So I suppose the IP address is used by idev affiliate to hack the subscription recurring commission.

I hope that explains it.

So. The plugin you mention would work as follows:

Use some field which is common between recurring payments ( i dont know if this is transactionId or something else ).

Query database to see whether transaction already exists (with IP address). if exists, pull out IP address. If does not exists, store IP address in vbulletin database against transactionId.

John