Troubleshooting Modules - Revision history

Cheese: /* My module crashes whenever I try to use an interface! */ fix'd

2011-01-23T08:09:34Z

‎My module crashes whenever I try to use an interface!: fix'd

Cheese: Undo revision 6185 by Hakaku (Talk) yet in english

2011-01-22T23:23:04Z

Undo revision 6185 by Hakaku (Talk) yet in english

Hakaku: /* My module crashes whenever I try to use an interface! */ redundant

2011-01-22T22:12:00Z

‎My module crashes whenever I try to use an interface!: redundant

Cheese: /* My module crashes whenever I try to use an interface! */

2011-01-21T00:08:40Z

‎My module crashes whenever I try to use an interface!

Hakaku: /* My module crashes whenever I try to use an interface! */ Expanding

2011-01-20T14:29:50Z

‎My module crashes whenever I try to use an interface!: Expanding

Cheese at 23:37, 6 January 2011

2011-01-06T23:37:27Z

Cheese: added knowledge

2010-12-30T08:41:21Z

added knowledge

New page

Here are some general solutions to help you solve a problem with a module that you just wrote.
Keep in mind that these are suggestions, and may not always be correct.

== My module works when I put it in modules.conf, but the zone crashes when I use ?insmod, why? ==

Chances are, you are doing something in the CB_ARENAACTION callback, and are doing something in the AA_PRECREATE or AA_CREATE states.
Simply do this when the module loads:

<pre>
Arena *a;
Link *link;
aman->Lock();
FOR_EACH_ARENA(a)
{
ArenaAction(a,AA_PRECREATE);
ArenaAction(a,AA_CREATE);
}
aman->Unlock();
</pre>

== When my module is in modules.conf, players can not enter the zone, or when I use ?insmod, players can not switch arenas and I get errors about player states! ==

You may be using arena data improperly.
Be sure you have gotten the I_ARENAMAN interface and have used AllocateArenaData() properly.

== My module keeps failing to load! ==

Be sure you have all the necessary modules needed for your module to run.
Make sure your module loads after the modules it is dependant on are already loaded.

== My module crashes whenever I try to use an interface! ==

Make sure you have gotten the interface by using GetInterface().
You may have forgotten to check if your interface is valid. (''like if(!iface) return MM_FAIL;'')

== My module will not compile! Why can't my compiler find certain things? ==

Sometimes, #include asss.h is not enough.
Only the core header files are in asss.h, and you will need to manually include any others.
This may also be true if you are using a custom interface.

[[Category:Module]]
[[Category:Guides]]

@@ Line 37: / Line 37: @@
 Make sure you have gotten the interface by using <tt>GetInterface()</tt> properly, that the assigned interface variable is unique, and that you verify whether or not the interface is valid by checking to see if it is not defined.  The latter is typically done in the entry point, as shown [[Writing Modules In C#Using Interfaces|here]], by adding an if-statement and returning <tt>MM_FAIL</tt> on failure.  If the interface is being called at some other point in the code, make sure to verify if it is defined and to handle cases throughout your code where it may not be valid.
-Note that also that if a parent interface does not check to see if it is still being used by other modules before unloading, it may cause instability in your zone and eventually result in a crash when a module calls that interface again.
+Also note that if a parent interface does not check to see if it is still being used by other modules before unloading, it may cause instability in your zone and eventually result in a crash when a module calls that interface again.
 == My module will not compile! Why can't my compiler find certain things? ==

@@ Line 37: / Line 37: @@
 Make sure you have gotten the interface by using <tt>GetInterface()</tt> properly, that the assigned interface variable is unique, and that you verify whether or not the interface is valid by checking to see if it is not defined.  The latter is typically done in the entry point, as shown [[Writing Modules In C#Using Interfaces|here]], by adding an if-statement and returning <tt>MM_FAIL</tt> on failure.  If the interface is being called at some other point in the code, make sure to verify if it is defined and to handle cases throughout your code where it may not be valid.
-Note also that if a parent interface does not check to see if it is still being used by other modules before unloading, it may cause instability in your zone and eventually result in a crash when a module calls that interface again.
+Note that also that if a parent interface does not check to see if it is still being used by other modules before unloading, it may cause instability in your zone and eventually result in a crash when a module calls that interface again.
 == My module will not compile! Why can't my compiler find certain things? ==

@@ Line 37: / Line 37: @@
 Make sure you have gotten the interface by using <tt>GetInterface()</tt> properly, that the assigned interface variable is unique, and that you verify whether or not the interface is valid by checking to see if it is not defined.  The latter is typically done in the entry point, as shown [[Writing Modules In C#Using Interfaces|here]], by adding an if-statement and returning <tt>MM_FAIL</tt> on failure.  If the interface is being called at some other point in the code, make sure to verify if it is defined and to handle cases throughout your code where it may not be valid.
-Note that also that if a parent interface does not check to see if it is still being used by other modules before unloading, it may cause instability in your zone and eventually result in a crash when a module calls that interface again.
+Note also that if a parent interface does not check to see if it is still being used by other modules before unloading, it may cause instability in your zone and eventually result in a crash when a module calls that interface again.
 == My module will not compile! Why can't my compiler find certain things? ==

@@ Line 37: / Line 37: @@
 Make sure you have gotten the interface by using <tt>GetInterface()</tt> properly, that the assigned interface variable is unique, and that you verify whether or not the interface is valid by checking to see if it is not defined.  The latter is typically done in the entry point, as shown [[Writing Modules In C#Using Interfaces|here]], by adding an if-statement and returning <tt>MM_FAIL</tt> on failure.  If the interface is being called at some other point in the code, make sure to verify if it is defined and to handle cases throughout your code where it may not be valid.
-Note also that if a parent interface does not check to see if it is still being used by other modules before unloading, it may cause instability in your zone and eventually result in a crash when such modules call the interface again.
+Note that also that if a parent interface does not check to see if it is still being used by other modules before unloading, it may cause instability in your zone and eventually result in a crash when a module calls that interface again.
 == My module will not compile! Why can't my compiler find certain things? ==

@@ Line 35: / Line 35: @@
 == My module crashes whenever I try to use an interface! ==
-Make sure you have gotten the interface by using GetInterface().
+Make sure you have gotten the interface by using <tt>GetInterface()</tt> properly, that the assigned interface variable is unique, and that you verify whether or not the interface is valid by checking to see if it is not defined.  The latter is typically done in the entry point, as shown [[Writing Modules In C#Using Interfaces|here]], by adding an if-statement and returning <tt>MM_FAIL</tt> on failure.  If the interface is being called at some other point in the code, make sure to verify if it is defined and to handle cases throughout your code where it may not be valid.
 == My module will not compile! Why can't my compiler find certain things? ==

@@ Line 44: / Line 44: @@
 Only the core header files are in asss.h, and you will need to manually include any others.
 This may also be true if you are using a custom interface.
 [[Category:Module]]
 [[Category:Guides]]