The DLL Project

[pd]

As well as checking DLL versions, would it be possible for the RP to force all players in multiplay to use RP? I.e. if Player 1 uses RP and player 2 doesn't, then RP will refuse to start a network/internet game? That way, Player 2 can be sure that their opponent has no possibility of using RP to enable cheating in a vanilla online game.

Of course I might do this in RP, but other DLLs do not *have* to do it.
IE, only RP users would be protected, if somebody runs his own project the check is not necessarily done.
I don't think we should put too much attention to cheating.
It has always been possible to use trainers online (Droke confirmed this to me a few days ago), so what would the difference be?
Those who blatantly cheat can usually get identified quickly.

---

I will use this small section to ask DCoder or Ren to add support for the <hr> tag here, cause horizontal rules look alot better than "---" ...

EDIT: Maybe I should just find a BBCode reference >.<

---

Progress Report:
I "took a few days off", another few days I worked almost half-time.

Funny things have been implemented and can be done in the game:
The CaptureManagerClass is responsible for units capturing other units (mind control). This feature is (apparently) fully implemented.
My test was selecting an enemy unit and make one of mine mind control it. It worked!
Mind overload and freeing a unit from mind control seems to work fine just as well.

The DiskLaserClass draws a radial laser around a unit which eventually fires at an enemy unit. This is used by the floating disk in YR, now it's available using C++.
A minor addition, but a good step in the "done"-direction.

Untested, but already implemented is the AirstrikeClass, which is used for Boris' airstrikes. Bad news is, it really wants to be fired by an InfantryType.
I might have to code a new class that works independently from infantry.

Yeah, there's more stuff, but the list would blow this forum.
It will be a damn pain to write a documentation over this, it might turn out to be just a little description on each class, ie what it can be used for.
The rest can be explored in the declarations, which I'm trying to comment understandably.