*Daniel wrote:Now is 3.1 going to be so big that no mod will work with it? Or is it depending on what changes there are?
In some ways correct. Work has been done so MODs already installed on your board will continue to work (however there will probably be quite a few merge conflicts) however most MODs being released will need significant changes to:
1) Turn into an extension (If they choose to (highly recommended))
2) Use events (hooks)
3) Adjust to new 3.1 coding guidelines, new MOD DB Policies
4) Adjusting to use new things like request class intead of request_var
5) Simply fixing conflicts due to the high amount of 3.1 changes
In 3.1 something new is being added called extensions. Extensions are self-contained MODs. They literally drop into a directory, then you have an ACP UI to view the meta-data, enable/disable them and you can even disable them but keep the data in the database. Then you have a purge function which deletes the database data too.
From 3.1's release MODs will still be accepted (I think) but they will be less popular for a number of reasons.
1) Extensions are easy for mod authors to write as its all in one extension, no more having to work out what edits you've made
2) Extensions are easy for admins to enable/disable at the drop of a hat
3) Extensions can be completely managed from the ACP including uploading, deleting, enabling, disabling, purging, viewing information etc. MODs however will require the board admin to add autoMOD.
4) Extensions must be completely edit less (like plugins).
That's just how extensions work in a few sentences, there will be a lot more information given out by the MOD Team once 3.1 has been released.